|
From: Arno P. <ar...@pu...> - 2013-03-03 21:11:24
|
The String encoding happens on the input side in
DEXmlvmOutputProcess.encodeString() (for both the C and the ObjC
backend). The C backend then generates the string constant pool via
COutputProcess.genConstantPool(). The actual code is emitted by the
xmlvm2c.xsl stylesheet.
Arno
On 2/28/13 6:10 PM, Panayotis Katsaloulis wrote:
> It seems that unicode Strings are still not quite supported by XMLVM.
>
> A simple command like this one:
> String a = "Δοκιμή";
> in the source (under constant pool) becomes something like
>
> // ID=1455: \1624\1677\1672\1671\1674\1656
> (JAVA_ARRAY_CHAR[]) {916, 959, 954, 953, 956, 942},
>
> which looks wrong, if indeed JAVA_ARRAY_CHAR is a char table.
>
>
> Similarly in the OBjC backend, the octal representation is shown.
>
> How can this issue be solved?
> For starters, is it possible instead of exporting the octal value, to
> present the actual unicode (UTF-8?) value?
>
> Thanks in advance
>
> --
> Panayotis Katsaloulis
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
>
>
>
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
|