On 17.06.2014 21:10, Rony G. Flatscher (Apache) wrote:
According to some older infos about the encoding returned by "unoinfo[.exe]
java" the resulting
string starts with an indicator byte, where '0' indicates an ASCII encoding
(and the paths are
delimited with '\0'), whereas '1' indicates UTF-16LE (and the paths are delimited with
"\0\0").
On German Windows (AOO 4.1) I see the encoding '1' (UTF-16LE), but the
characters are not 16-bit
(UTF-16LE) encoded, but plain ASCII, however the paths get delimited with
"\0\0". OOo (e.g. 3.4.1)
would return encoding '1' (UTF-16LE) where each ASCII character is preceded by
'\0'.
Clearly, an installation routine dealing with the returned string value of AOO
gets confused, if it
was written with UTF-16LE in mind, working correctly on earlier OOo.
I had a quick look at the problem. This is indeed a behavior change.
There was a suspicious line in the responsible code. When I cleaned it
up (#i125115#) on trunk the output is fine again. Is this something for
our bugfix release? Please lobby for it if see it that way and when you
verified the fix.
Herbert
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
