ALT Linux Bugzilla – #17300
can't open a file if its name contains strange chars
Last modified: 2008-09-30 17:25:58
You need to
before you can comment on or make changes to this bug.
Created an attachment (id=2945) [details]
openoffice.org-18.104.22.168-alt4.M40.1 in Lite 4.0.3
I have a with a strange name (I got it via rsync from a system with another
locale). But whatever the name of a file is, a program must open it if it is
given as an argument. This is not the case with OOo:
$ echo *
$ ooffice óÐÉÓÏË.doc
An error message appears: "/home/imz/bugreports/encoding/??????.doc не
существует." (The question marks are not ordinary question marks, but question
marks in black diamonds.)
A proof that good programs can open this file:
$ file óÐÉÓÏË.doc
óÐÉÓÏË.doc: Microsoft Office Document
(How to reproduce: if you don't know how to create a file with such name, try
the attached .tar.)
Looks like sort-of output of 'echo *' is a feature of your terminal emulator
which can interpret invalid UTF-8 characters (you can check it by echo * |
iconv -f UTF-8 -t UTF-8).
Ability to use non-UTF-8 names in UTF-8 locale should be considered as a
feature, and refusal of opening such files should not be treated as a bug.
(In reply to comment #1)
> Looks like sort-of output of 'echo *' is a feature of your terminal emulator which can interpret invalid UTF-8 characters (you can check it
> by echo * | iconv -f UTF-8 -t UTF-8).
I don't care how it is displayed, but it's a real path, and it points to an
existing file. If it was invalid, the filesystem should have refused to create
"file" can open it, "abiword" can open it:
$ abiword * -t txt -o a.txt; cat a.txt
but OOo can't. Why? Because the file opening or option parsing code is broken