Issue 65752

Summary: OOo running in UTF-8 locales is not able to open filenames with latin2 characters
Product: General Reporter: pmladek <pmladek>
Component: codeAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: esigra, issues
Version: OOo 2.0.2   
Target Milestone: ---   
Hardware: PC   
OS: Linux, all   
Issue Type: ENHANCEMENT Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
A test file packaged in a tar archove, so we do not lost the latin2 chracters by an automatic recoding none

Description pmladek 2006-05-24 18:56:42 UTC
I heard from some users that they had had problems to open some old OOo
documents after they had updated to a newer SUSE Linux distribution and they had
started to use UTF-8 locales. The problem was caused by filenames including
non-ASCII characters that were stored in old coding, for example in latin2
(iso-8859-2).

Yes, we suggest our users to recode all filenaes to UTF-8. We provide an utility
for this purpose. Though, I think that OOo should be able to open such files.

I'll attach a file for testing. The filename includes some latin2 charaters.

I am sorry, I do not have a fix for this.
Comment 1 pmladek 2006-05-24 18:58:34 UTC
Created attachment 36706 [details]
A test file packaged in a tar archove, so we do not lost the latin2 chracters by an automatic recoding
Comment 2 thorsten.martens 2006-06-14 13:36:40 UTC
TM->requirements: please have a look, thanks !
Comment 3 goc 2007-07-17 16:33:55 UTC
I'd like to second that. Recently I've been given a CD from a customer who has
all sorts of weird Microsoft encodings on it, and I had to copy the CD to my
hard disk and rename a lot of files before I could open them. This sucks. OTOH,
I was unaware of the tool that renames files, although it would not help much on
a CD...
Comment 4 odalman 2008-05-06 14:31:59 UTC
This problem can be solved by executing something like "convmv -f iso-8859-2 -t 
utf-8 $HOME -r --notest". For the case with a CD, I suppose it needs some mount 
option that specifies the encoding of filenames on it. It may also require that 
a kernel module for that encoding is installed. Or it could be copied to the 
hard disk and fixed with convmv as above.
Comment 5 pmladek 2008-05-12 16:22:25 UTC
I agree that the best solution is to recode the filenames. Though, you might get
ugly file names also by attachments in mails or from a zip/tar archives. It is a
bit annoying to recode the file names just to see them.