From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131
Description of problem:
When writing a document in Swedish using the swedish char (ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½, described as
A with a ring, A with two dots, and O with two dots).
When exporting the document to Word 95 the swedish char is wrong, they are still
encoded as UTF-8, which Word does not understand. You will get the same error
when importing the file to OOo again.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Write ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ in an OOo doc.
2. Export it as Word 95
3. Open the Word95 file in either Word or OpenOffice.
Actual Results: You do not see the same characters.
Expected Results: To see the same characters.
Created attachment 91486 [details]
An OpenOffice doc with swedich char.
Open this doc in OpenOffice.
Save it as Word 95.
Open the Word95 file And you do not see the same file as you exported.
You can also try to open the Word file in Word95 and get the same error.
Please try current OOo 1.1.0, and reopen if problem still occurs
Still the same problem using 1.1.0
Usig FC1 RPM: openoffice.org-1.1.0-6
I mean latest OOo in rawhide, meaning openoffice.org-1.1.0-28
Still the same problem in openoffice.org-1.1.0-28
caolan, can you take a look?
as a temporary workaround
> export LANG=""
and then export to word95
clearly something is using the system encoding, and if you run
you've probably got a utf-8 encoding.
I'll investigate to see if this is a OOo error, or an unavoidable
artifact of the word95 format which is must use 8bit encodings unlike
the word97 one which is true unicode.
Firstly I've got the up and coming OpenOffice.org fixed
Secondly lets look at 1.1.X, I modified this stuff a lot for 2.0
because I was unhappy with the pre 2.0 code.
Created attachment 102837 [details]
this patch would do the trick for 1.1.2
Submitted patch for 1.1.X to upstream ooo-build
Will work in dans 1.1.2-5 testing rpm from
1.1.2-5 has hit rawhide, so this should be fixed. If its not, please
reopen the bug.