Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues editing unicode character docs #123

Open
dizzzz opened this issue Apr 4, 2016 · 3 comments
Open

Issues editing unicode character docs #123

dizzzz opened this issue Apr 4, 2016 · 3 comments

Comments

@dizzzz
Copy link
Member

dizzzz commented Apr 4, 2016

from https://stackoverflow.com/questions/36371056/unable-to-properly-edit-unicode-charachters-in-exide:

the backspace and delete buttons seem to delete characters that are not under the cursor.

  • chrome 50 / macsox
  • safari 9.1 / maxosx

attached is a file with special characters

test.xml.txt

@joewiz
Copy link
Member

joewiz commented Mar 12, 2017

I think this is an inherent problem with the ace editor - see https://github.com/ajaxorg/ace/search?q=unicode&type=Issues&utf8=%E2%9C%93 and https://www.google.com/webhp?hl=en&q=site:github.com/ajaxorg/ace/+unicode.

And according to ajaxorg/ace#3037 (comment):

This happens with many non-ascii characters (and the same error occurs in the github editor)
estimated chance of being fixed : 0.071%

So... close as "wontfix"?

@duncdrum
Copy link
Contributor

I d say this is core browser territory. @joewiz Let me have a look with some of my own files, where I managed to work around the problem with some editors. Chances are thus is beyond eXide s influence.

@duncdrum
Copy link
Contributor

yup font substitution in ace is playing tricks, even with files that the browser/ OS can actually handle. See also this PR with a potential fix for BIDI languages, in essence overriding ace's font-selection.

I vote not to close, so there is a place to track ace's development, and for users to see that its a known issues.

Maybe a similar overriding of ace font selection could be implemented in exide based on @xml:lang? People use eXide to work with xml in the browser. Both the browser and xml can handle Unicode, so eXide should to. This wouldn't solve the problem for .txt or .xq but could offer a workable compromise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants