To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=95628


User sb changed the following:

                What    |Old value                 |New value
================================================================================
                      CC|'hdu,kpalagin'            |'kpalagin,sb'
--------------------------------------------------------------------------------
             Assigned to|sb                        |hdu
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Wed Apr 22 12:47:46 +0000 
2009 -------
@hdu:  OOo internally keeps file URLs in UTF-8 and, when interfacing with
external entities, converts relevant data between osl_getThreadTextEncoding and
UTF-8.  This is a very old design decision that directly impacts large bodies of
code.  Of course, if the relevant data contains characters that cannot be
represented in osl_getThreadTextEncoding, this causes problems.  This appears to
be a problem mainly on Windows (where the system uses UTF-16, i.e., full
Unicode, but osl_getThreadTextEncoding is always one of the legacy 8-bit
character encodings, each only covering a small subset of Unicode).  However,
for Windows, a solution could be as follows:

Use the ...W instead of the ...A variants of relevant system calls (so that,
e.g., Asian characters in a user name are transported correctly regardless of
locale).  Depending on surrounding code, either directly translate between the
Windows UTF-16 data and OOo's UTF-16--based rtl::OUString or, in a two-step
process, translate in one step between the Windows UTF-16 data and temporary
UTF-8 data and in another step between the temporary UTF-8 data and the OOo data
representation via a new osl_getThreadTextEncoding'.  That
osl_getThreadTextEncoding' would be like osl_getThreadTextEncoding, but for
Windows would always return UTF-8 (all places that currently call
osl_getThreadTextEncoding would have to be checked whether or not they have to
be switched to osl_getThreadTextEncoding').

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to