Issue 92697 - Cannot open filenames with non-ASCII characters when system currency is Euro
Summary: Cannot open filenames with non-ASCII characters when system currency is Euro
Status: CLOSED DUPLICATE of issue 105047
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: DEV300m29
Hardware: Mac Mac OS X, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: thorsten.martens
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-12 10:33 UTC by vinc17
Modified: 2010-07-21 11:15 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description vinc17 2008-08-12 10:33:51 UTC
Build: OpenOffice 3.0.0 DEV300m29 (Build:9339), French version.

Under Mac OS X 10.4.11 (at least), when the system is configured with the Euro
currency in the System Preferences (International -> Format), OpenOffice cannot
open files with non-ASCII characters in their filename. I think that OpenOffice
incorrectly decodes the filename, thus cannot find the file (this is what
happened with OpenOffice 2.x X11 version). For instance, typing "open é.odt"
from a terminal leads to an error box saying "/Users/vinc17/é.odt n'existe pas"
though the file exists. Same problem when using the menu (Fichier -> Ouvrir...)
to open a file.

If the currency is set to British Pound Sterling (I have the system in English),
then there's no problem. One may wonder why currency settings has an effect on
filenames. With OpenOffice 2.x, this was related to the selection of the
locales, and OpenOffice messes up with that. You can see ktrace information on
<http://qa.openoffice.org/issues/show_bug.cgi?id=67438#desc23>.

Note: I cannot get ktrace information with OpenOffice 3 because when I run it
directly from the command line (in UTF-8 locales) with:

/Applications/OpenOffice.org.app/Contents/MacOS/soffice é.odt

then the file can be loaded. However, the filename that appears in the window
title is é.odt instead of é.odt (note that é is what one obtains when encoding
é in UTF-8/NFC and rereading it in ISO-8859-1).
Comment 1 vinc17 2008-08-12 10:35:11 UTC
I forgot to say that the file system on my machine is the standard HFS+.
Comment 2 thorsten.martens 2008-08-13 12:30:31 UTC
There have been some fixes about opening filenames with special characters
recently. In a m2 the problem is not reproducible anymore. Please check again. 
Comment 3 vinc17 2008-08-13 15:06:27 UTC
This is not a m2, but a m29, which is the latest build according to
<http://download.openoffice.org/680/?intcmp=1461>.

I've updated the version field (the bug tracker should list the versions in a
more logical way: the m2 is at the end and I hadn't seen m29).
Comment 4 tguido56 2008-10-29 21:47:22 UTC
Build: OpenOffice.org 3.0.0 OOO300m9 (Build:9358), English version

System: Mac OS X 10.4.11
Hardware: iMac7,1 (Intel Core 2 Duo)
Disk: single partition, partition type Apple_HFS
File system: Mac OS Extended (Journaled), aka HFS+ Journaled

System Preferences->International: Region=Custom, Currency=Euro, Measurement Units: Metric

Symptom is as already descibed: OpenOffice cannot open files with non-ASCII characters in their 
filename.
Attempted to open the files in thre different ways:
- drag&drop of file icon on OpenOffice
- from OpenOffice's Macintosh menubar (File->Open Document)
- fom file's contextual menu (ctrl + mouse click on file icon) Open withh...->OpenOffice.org

In all the three cases this error box pops-up:  "/Users/username/dir/fílènämê.rtf does not exist."
Comment 5 robinsmidsrod 2009-02-22 19:45:14 UTC
I also see this problem on Ooo 3.01rc2 (Aqua build) running on a PowerMac G4
when connection to CIFS shares.

Filenames with native characters are not possible to open.
Comment 6 kpalagin 2009-06-16 18:51:05 UTC
Seems to be duplicate of
http://www.openoffice.org/issues/show_bug.cgi?id=69973
Comment 7 vinc17 2009-06-16 19:02:56 UTC
No, the bug is quite different. Note that under Mac OS X (on HFS+), all files
are encoded in UTF-8.
Comment 8 Olaf Felka 2010-06-29 14:13:54 UTC
Even if this issue is I'll set it to duplicate to issue 105047. The newer issue
has at least more information and a target.
@ vinc17. If you would like to you cat add some information to issue 105047.

*** This issue has been marked as a duplicate of 105047 ***
Comment 9 Mechtilde 2010-07-21 11:15:26 UTC
duplicate -> closed