Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | OOo running in UTF-8 locales is not able to open filenames with latin2 characters | ||||||
---|---|---|---|---|---|---|---|
Product: | General | Reporter: | pmladek <pmladek> | ||||
Component: | code | Assignee: | 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
pmladek
2006-05-24 18:56:42 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
TM->requirements: please have a look, thanks ! 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... 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. 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. |