Files with special characters in filename can't be opened

Bug #49008 reported by Kristian Rasmussen
22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenOffice
New
Undecided
Unassigned
openoffice.org (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: openoffice.org

I am unable to open files with special characters (æøå, specifically) in their filename through nautilus. I presume it is an encoding error in OpenOffice, since opening through OOo works, but when saving the opened document, the special charaters in the filename is encoded incorrectly.

Steps to reproduce:
1. Create an openoffice document and rename it to, for example, "abcæ.odt"
2. Open the document, and observe that OOo claims that "/path/to/abcæ.odt does not exist"
---
1. Create an openoffice document and rename it to, for example, "abcæ.odt"
2. Start OOo
3. Open the document through the "Open" button in OOo
4. Save the document and observe that it is saved as "abcæ.odt"

Revision history for this message
Will Hayworth (whayworth) wrote :

I cannot confirm this bug with my fully-patched Dapper install.

Revision history for this message
Markus Golser (golserma) wrote :

Can't reproduce this.

Revision history for this message
Micah Cowan (micahcowan) wrote :

Seems there's trouble reproducing this... what version of OOo do you have installed?

Changed in openoffice.org:
status: Unconfirmed → Needs Info
Revision history for this message
Kristian Rasmussen (krasmussen) wrote :

Version 2.0.2-2ubuntu12.1

Revision history for this message
Kristian Rasmussen (krasmussen) wrote :

Maybe it has something to do with my choice of the en_DK locale, since I couldn't reproduce this on my other box with the en_AU-locale?

Revision history for this message
Stéphane Marguet (stemp) wrote :

Are you still experiencing this issue ?

Revision history for this message
Kristian Rasmussen (krasmussen) wrote :

With en_DK-locale, yes. I guess that is sort of broken in general.

Revision history for this message
PasserRu (passer) wrote :

The same is with Russian (UTF8) in 2.0.4-ubuntu5. When saving file under Russian filename, it appears as ???? in Konqueror. When renaiming it there, OO failes to load file, indicating that it dosn't exist.

Revision history for this message
PasserRu (passer) wrote :
Revision history for this message
johndoe (hovnohovno) wrote :

I am experiencing exactly the same problem with OpenOffice 2.2 Slovak Version on Windows XP. If the path contains some special characters, it dosn't open with an error that the file doesn't exists. The error message contains different path - special characters changed to similiar standard characters.
Thanks for help.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for openoffice.org (Ubuntu) because there has been no activity for 60 days.]

Revision history for this message
Lars Ingvard Hoff (lars-hoff) wrote :

I have the same problem after upgrading from Ubuntu Studio Hardy to Lucid:

When opening an OpenOffice file with non ASCII chars like æøå in either the file name or in the path in Nautilus I get "File does not exist" pop-up message. If I create a new file in OpenOffice and try to save it with non-ASCII chars either in the file name or in the path I also get the file not found message.

If I run from command line I get the following error and the file is NOT opened:

lars@anteca:~/Dokumenter/leilighet/sameiet/nøkler$ ooffice "nøkler.odt"
I18N: X Window System doesn't support locale "nb_NO.utf8"
I18N: Operating system doesn't support locale "en_US"

If I open the file from within OpenOffice (Open file) then I also get the file not found error.

However, there is a workaround. This works:

lars@anteca:~/Dokumenter/leilighet/sameiet/nøkler$ sh -c "LANG=en_US.UTF-8 ooffice -writer brev\ aftenposten\ nøkler.odt "

OpenOffice is the only program that has this problem. I can open the same file in a text editor fine.

This worked fine in Hardy...

Locale gives the following:

lars@anteca:$ locale
LANG=nb_NO.utf8
LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
LC_CTYPE="nb_NO.utf8"
LC_NUMERIC="nb_NO.utf8"
LC_TIME="nb_NO.utf8"
LC_COLLATE="nb_NO.utf8"
LC_MONETARY="nb_NO.utf8"
LC_MESSAGES="nb_NO.utf8"
LC_PAPER="nb_NO.utf8"
LC_NAME="nb_NO.utf8"
LC_ADDRESS="nb_NO.utf8"
LC_TELEPHONE="nb_NO.utf8"
LC_MEASUREMENT="nb_NO.utf8"
LC_IDENTIFICATION="nb_NO.utf8"
LC_ALL=

Hope someone with better understanding for the locales and chars can help out. Must admit I think it is too bad we still have these kinds of basic problems in Ubuntu Linux.

Revision history for this message
Øyvind Jensen (jegerjensen) wrote :

I have exactly the same problem, and actually reported a duplicate bug. However, it turned out that the problem was not reproduced when I logged into a different user account on the same computer. Have you tried this?

For me at least the problem must be due to the configuration of my own user account. I suspect this is because of some old config files in my home directory. The Ubuntu installation started out as Hoary Hedgehog back in 2005 and I have upgraded it several times all the way to Lucid. The other user account, for which I cannot reproduce the problem was created around Hardy times I think. Do you all have installations that was first installed way back?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.