View previous topic :: View next topic |
Author |
Message |
nggalai Blue Pill

Joined: Jul 26, 2009 Posts: 1
|
Posted: Sun Jul 26, 2009 5:48 am Post subject: |
|
Hi there,
I might be late to the game, but this issue is prevalent still in OOorg 3.1 (and the current NeoOffice release). Unfortunately, the OOorg people don’t seem to be too interested in Mac encoding. The most recent bug report has been open for months, now, no word from the OOorg devs.
This might sound like a luxury problem, but when receiving RTFs, say from Mellel users, special chars like Umlauts, typographical quotes etc. are garbled up.
As the OOorg dudes don’t seem to care, I was wondering whether you guys have a more direct route / more leverage? The current bug report has the issue number 98663.
Cheers, and thanks for the great work,
-Sascha _________________ Sascha “nggalai†Erni, .rb |
|
Back to top |
|
 |
pluby The Architect


Joined: Jun 16, 2003 Posts: 11949
|
Posted: Sun Jul 26, 2009 10:56 am Post subject: |
|
nggalai wrote: | As the OOorg dudes don’t seem to care, I was wondering whether you guys have a more direct route / more leverage? The current bug report has the issue number 98663. |
Unfortunately, we have zero leverage with Sun Microsystems' OpenOffice.org engineers. If it is going to be fixed, I would need to debug and fix their code myself.
Since the OpenOffice.org bug indicates that NeoOffice 2.2.5 handled this encoding correctly, I will take a look at the OpenOffice.org code and see if there is any obvious place where they broke their code.
I will post again when I have some news to report.
Patrick |
|
Back to top |
|
 |
pluby The Architect


Joined: Jun 16, 2003 Posts: 11949
|
Posted: Sun Jul 26, 2009 12:48 pm Post subject: |
|
FYI. After comparing the OpenOffice.org 3.0.1 code to the OpenOffice.org 2.2.1 code (which NeoOffice 2.2.5 is based on), I think that I have found the OpenOffice.org bug and I think that I have fixed it in the following test patch. I found that the OpenOffice.org 3.0.1 code would override the Mac encoding that it found at the beginning of the file with the default Windows encoding every time a font tag is encountered. This code makes no sense as the RTF file's encoding should be used as the default.
Can you installed the following test patch and tell us if the bug is fixed for you?:
Intel:
http://joe.neooffice.org/test/NeoOffice-3.0-Patch-5-Test-8-Intel.dmg
PowerPC:
http://joe.neooffice.org/test/NeoOffice-3.0-Patch-5-Test-8-PowerPC.dmg
Note: I moved nggalai's post to its own separate topic as it is a different problem than the problem discussed in the topic that nggalai originally posted to.
Patrick |
|
Back to top |
|
 |
narf The Anomaly

Joined: Jan 21, 2007 Posts: 1075
|
Posted: Tue Jul 28, 2009 6:15 pm Post subject: |
|
I have opened bug 3505 to track this issue. When there is new status it will be posted here.
--fran |
|
Back to top |
|
 |
pluby The Architect


Joined: Jun 16, 2003 Posts: 11949
|
Posted: Wed Jul 29, 2009 12:59 pm Post subject: |
|
narf wrote: | I have opened bug 3505 to track this issue. When there is new status it will be posted here. |
I have already posted the test patch in my previous post so there is no new status to post.
nggalai,
Can you install the test patch in my previous post and tell us if the bug is fixed for you?
Patrick |
|
Back to top |
|
 |
pluby The Architect


Joined: Jun 16, 2003 Posts: 11949
|
Posted: Fri Jul 31, 2009 9:12 am Post subject: |
|
nggalai,
Can you tell us if the test patch works? I am planning on releasing an official NeoOffice patch on Monday but before I do that, it would be nice to have you verify that the fix works.
Patrick |
|
Back to top |
|
 |
pluby The Architect


Joined: Jun 16, 2003 Posts: 11949
|
|
Back to top |
|
 |
|