To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=69973
------- Additional comments from [EMAIL PROTECTED] Fri Apr 27 12:08:21 +0000
2007 -------
I think the problem here is that OOo doesn't treat file names on Unix as opaque
byte strings, but interprets them according to the codeset/encoding (not really
sure about the correct terminology here) of the user's current locale? This is
problematic as file names on Unix *are* just byte strings.
Any interpretation of file name byte strings as UTF-8 or something else is up to
the user leve software. It's up to the user's carefulness and cluefulness, and
site policies whether the actual file names present on a Unix file system are in
some consistent codeset/encoding or not. I assume it is very common that Western
European Unix installation, for example, have file names both in ISO8859-1 and
UTF-8.
The file names (byte strings) in the three-names.zip file are, with Perl-style
hex escape syntax:
1) accentu\x{c3}\x{a9}.odt
2) accentu\x{e9}.odt
3) accentu\x[e2}\x{88}\x{9a}\x{c2}\x[a9}.odt
The zip format apparently stores file names just as byte streams. According to
http://www.pkware.com/documents/casestudies/APPNOTE.TXT there are mechanisms to
indicate the codeset and encoding of the file names, but I don't know how well
those are implemented and adhered to by the actual zip implementations.
I haven't checked the code, but apparently OOo trusts that the codeset/encoding
the user's locale setting indicates really is enforced, and that all file names
encountered are legal in that codeset/encoding. It probably converts the
filenames from this encoding to its internal UTF-16 string format. File names on
disk that aren't legal in the locale's encoding are just skipped.
In your SUSE case, apparently the encoding the locale indicates is in use is
UTF-8. Only the file names 1) and 3) above are legal UTF-8 strings. The file
name 2) presumably is in some single-byte codeset like CP1252. It is not legal
UTF-8, so OOo just skips it. How does the directory listing look in a shell
window, or a file browser window?
Fixing this problem might be quite hard. It might also be argued that this is a
case of garbage in, garbage out. If the user can't keep track of using a
consistent encoding for her file names, why should OOo care ;)
---------------------------------------------------------------------
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]
