I replied before but do not see my post. Hope this message makes it.
What you can do is apply encodeURI to the result of
editor.getSession().getValue().
Server side, you'll have to decode, of course.
It solves my problem.
What happened is that Ace (or Chrome) convert 'difficult' characters
to encoded strings. E.g.
é
will be encoded as:
%C3%A9
However, if the server does not understand this (and my eXist XML
database server did not when Chrome posts the data), it understands C3
as à and A9 as ©, so server side the text reads:
é
(the % signs are ignored).
By explicitly encoding the string in my own javascript code,
apparently the server leaves the string intact and my own code can
decode it correctly.
Joop
On Feb 28, 11:53 am, pravin nagare <
nagarepravi...@gmail.com> wrote:
> I am using Ace editor and using the command editor.getSession().getValue()
> to read from Ace.*
> *This works but while reading it contains the line numbers displayed on the