Issue 61732 - Problem handling filenames with international characters
Summary: Problem handling filenames with international characters
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 2.0.1
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: thorsten.martens
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-07 12:03 UTC by ismohaa
Modified: 2006-03-16 10:03 UTC (History)
2 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 ismohaa 2006-02-07 12:03:49 UTC
Behaviour: Opening a file containing international characters (åäö tested) in
the file name results in an error message being displayed, and the file not
opening. For example attempting to open the file "Test_åäö.txt" results in the
error message: "<path-to-file>/Test_%E5%E4%F6.txt does not exist" (This
statement is of course quite correct - such a file doesn't exist, but it wasn't
what I asked it to open either.)

Creating a file in OO.o and saving it as "Test_åäö.txt" will result in it being
named "Test_%E5%E4%F6.txt". I also tested converting the filename to UTF-8 using
the convmv tool. This resulted in a file named "Test_åÀö.txt". When I tried
to open it with OO.o I (ironically) got the error message
"<path-to-file>/Test_åäö.txt does not exist".

OO.o is the only program on my system displaying this kind of behaviour, causing
me to draw the conclusion that it's OO.o related rather than system
configuration related.

Reproducible: Always

Steps to reproduce:
1. Create a document that contains any of the following characters (å,ä,ö,Å,Ä,Ö)
in the filename. (I assume any international character would work, but have not
tried.)

2. Start OO.o

3. Click Archive --> Open and then choose the file created in step 1.

(Annoying) workarounds:
1. Clicking the file in Konqueror starts OO.o and opens the document correctly.
2. Using "oowriter2 <filename>" from a console window opens the document correctly.
3. Renaming the file so it doesn't contain international characters.

Additional information about my system:
-Gentoo Linux 2005.1 (ix86)
-KDE 3.5
-OO.o installed with "emerge openoffice" (i.e. compiled from source) with the
following USE-flags "-binfilter +curl +eds -gnome +gtk +java +kde -ldap -mozilla
+xml2"
-Java: Sun JDK 1.5.0.06
-.bashrc sets locale by:
export LC_ALL=sv_FI
- "locale -a" gives following output:
C
en_US
en_US.utf8
POSIX
sv_FI
sv_FI@euro
sv_FI.utf8
Comment 1 ismohaa 2006-02-07 17:49:22 UTC
Okay, I've found a solution. From Gentoo's bugzilla: "Hmmm, looks like a bug in
the gnome file selector, never experienced that myself, though. Just to make
sure, could you de-activate the GNOME file selector (in Tools > Options >
OpenOffice.org > General activate "Use OpenOffice.org dialogs" and try again?"

Now it works. It would appear that it's a Gnome/GTK-problem, and that would
explain why only some users have this problem. Compiling with USE="-gtk" might
also help, but I haven't tried it. (And I won't. OO.o is a great program, but a
beast to compile.) Oh, and FYI the reply quoted above wasn't a reply to me
directly, but to someone with the same problem - which means there is a problem,
be it OO.o's or Gnome's.
Comment 2 elmede 2006-02-13 04:25:35 UTC
Ok, just to add to the list.  I'm having the exact same problem with the only
difference that I'm using the qt-toolkit version of openoffice.org and the exact
same problem happens over here.

I'm also on gentoo, so that brings up the question to wether this is an oo.org
or a gentoo problem.  Anyways, it would be great if the situation could be
looked at.  

If needed, any log information could be pasted here, just that right now I don't
know how to do it.

By the way, I thought maybe it was a locales problem (LC_ALL, LANGUAGE, LANG,
etc) but that's been ruled out since i've ran oo from the shell exporting
different settings to no avail. The same problem stays there..

For now the problem is solved by using oo's dialogues, but that's just a workaround

Thanks a lot!
Comment 3 Olaf Felka 2006-03-16 10:01:42 UTC
It's not an OOo but a Gnome/gtk problem.
Comment 4 Olaf Felka 2006-03-16 10:03:04 UTC
closed