Apache OpenOffice (AOO) Bugzilla – Issue 28982
Improve file url conversion capabilities of sal
Last modified: 2009-10-19 12:37:13 UTC
OpenOffice.org file URLs are UTF8 encoded. Currently the OOo system abstraction layer (sal) uses the current thread text encoding (osl_getThreadTextEncoding) in order to convert file names received from the system interface to such URLs and vice versa. Under certain environments like Gnome for instance it is wrong to do this because these environments use a fixed encoding for path names, e.g. UTF8. A few new sal functions are necessary to respect this fact, e.g. osl_setFileURLEncoding, osl_getFileURLEncoding. During startup of OOo when the environment in which OOo runs is known the respective file URL encoding must be set.
@TRA: See also #i25416# and #i16281#
@TRA: Remember to improve the error handling of sal in case conversion errors happen.
@TRA: sal should maybe also handle broken Java file URLs (file:/...) containing only a single slash. Inform AS when starting this task.
To risky to be fixed in this late stage of the OOo2.0 time line. Will be fixed immediately with the start of the OOo3.0 development cycle.
Reassigned for change of responsibilities sake.
sb: Can you please have a look.
For the different encodings used within file URLs, see the com.sun.star.uri.ExternalUriReferenceTranslator UNO service. For the pathnames corresponding to file URLs, I am not aware of any problems in the OOo code that exchanges such pathnames with external code.
Please reopen if there *are* any specific problems.
.