+ update 2020: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means we will NOT develop new features and/or fix most of bugs. We left the tracker running in case somebody from community would like to work on it. Sorry for the inconvenience.
State: closed new: Initial state. As long as issue is in this state, the work on the issue has not yet begun. opened: Opened state means developer started working on the issue. Feature/Fix will probably be in the next release. postponed: This means developer is not working on it now, for some reason it cannot be implemented now. Issue may be opened again in the future. upgraded: Issue is in upgraded state when developer made changes to the program and new version was released. closed: This means the user is satisfied with issue results and no more changes are needed. invalid: These issues cannot be solved. ignored: Developer decided to take no action on this issue. returned: Program changes were made but user is not satisfied and returned the issue.
> What steps will reproduce the problem?
Left mouse click on a line with Japanese and English characters in it in an attempt to
place the text cursor.
> What is the expected output? What do you see instead?
Expected: The text cursor will appear in the correct spot on that line.
Actual: The text cursor appears a lot further ahead in that line then expected. Most
likely at the end if selected past the midpoint in the line.
> What version of the product are you using? On what operating system?
Version: 2.1.2 stable and 2.1.2 nightly 31c7cc0
OS: Windows 7
> Please provide any additional information below.
-Only happens on lines containing a mix of Japanese and English characters.
-Other lines in that file containing ONLY Japanese or ONLY English characters behave
-I would assume this also happens to Chinese and other foreign Unicode characters. (Have
-Example code for testing: trace("おはようございます。日本語です。");
Well, I just posted it to the JSyntaxPane page, but it doesn't look it's been updated
since 2009 (?). If there's nothing you can do about it, then I guess this can be ignored
then. Working around it isn't too troublesome.