I am testing Fire.
It looks awesome!
But, I having hard time to input Korean character into Fire IDE Editor.
If i assign a character 테스트 into a variable. it should be like this.
a := ‘테스트’;
But, in fire app, on same key stroke it displayed like this.
a := ‘ㅌㅔㅅㅡㅌㅡ’;
the cursor pointer position is not correctly drawed also.
is this a bug?
thanks in advance.
This sounds like a bug, yes. Can you send me a screenshot, and steps to reproduce this? (eg. can i simply switch toKorean keyboard layout and type some random letters to reproduce this, or would i need to do something special)?
thanx,
marc
Thanks, logged as bugs://70259: Fire: problem with Korean characters in editor
here is screenshot and the screen shot contains instruction to reproduce.
and FYI most famous korean keyboard layout looks like this.
Sorry, this is on my list, but I haven’t gotten around to it yet. I know what the issue is (actually two, one for typing, and one for display of multiplex characters) but don’t have the perfect solution yet.
I am still waiting on this issue.
i know this is a low priority issue but i am just reminding this.
thank you
should be fixed for the next beta (next week, as we’re not shipping a beta this week due to some unforeseen issues). please let me know if it works for you.
What a great news. now i can use Fire.
Remobjects rocks.
thank you marc
bugs://70259 got closed with status fixed.
Is this all good foryou now with .2041?
nope. it is still happening on 2041
nothing changed.
Even cursor positions shows incorrectly.
ok, i’ll need more detailed steps how to reproduce this (with a US hardware keyboard), then. what settings to i change and what keys do i press to make this happen?
it still remains
choose korean layout in mac OS
open in fire ide
and set korean mode in OS
Type xptmxm in your keyboard if it is normal then character will look like this
테스트
Thank you,
I get tis when i type this:
ㅌㅔㅅㅡㅌㅡ
the UTF-8 for this is:
E3858C
E38594
E38585
E385A1
E3858C
E385A1
it seems that the problem is that the last two pairs of chars should be combined, but they aren’t, right? — but i gotta admit that i don’t understand enough about the language, and its parts of Unicode, to say why this doesn’t happen.
if i open the same file in textedit, it sows the same; so it looks like the display is correct (ie matches the data), but the inout is not.
The unicode generated by textEdit is:
ED858C
EC8AA4
ED8AB8
and when loaded back looks ok too.
i also notice that the string changes with literally every character i type, ie typing the 4th char still has affect on how the first one looks very interesting. i’ll need to dig much much deeper into the text input system to figure out how this works, i’m afraid, as the docs on this are sparse (even finding the info for the dead key support thats there enow took forever and was pure luck 
thanx!
Yes its a composite language.
Many open source language supports language analysis server
so someone might able to make a plugins for VS code or etc
Template parts are supported by CLI
More open policy maybe helpful to grow a ecosystem.
One suggestion.
It seems supporting Korean in editor is a hard problem.
But i do know there is no problem to input korean to
Fire’s preference text fields
So i wonder that would it be great that i press some keyboard shortcut and it shows a hovering text field.
the hovering small text fields that only covers the cursor line.
and after it is done and the native text fields gone!
How about that?
