You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openoffice.apache.org by bu...@apache.org on 2023/01/02 22:02:41 UTC
[Issue 128550] New: Wrong accentuated characters from old .rtf files
https://bz.apache.org/ooo/show_bug.cgi?id=128550
Issue ID: 128550
Issue Type: DEFECT
Summary: Wrong accentuated characters from old .rtf files
Product: Writer
Version: 4.1.13
Hardware: Mac
OS: All
Status: UNCONFIRMED
Severity: Normal
Priority: P5 (lowest)
Component: open-import
Assignee: issues@openoffice.apache.org
Reporter: filhol@ill.eu
Target Milestone: ---
Let me 1st stress that macOS OpenOffice is the last software I know that is
still able to open early 90's RTF files containing PICT (or PCT)
bitmap/vectorial images. This an invaluable tool when, like me, you're digging
old corporate archives for an historical work. Long live OpenOffice!
Both LibreOffice and Microsoft Word import only the text from those old .rtf
files but miss an embedded pict-image converter.
However OpenOffice has a problem with accentuated characters from these old
files. Each one is displayed as an invalid character as shown below:
OpenOffice: Ž ‘ ‰ Š ” Ÿ ž Ÿ Ï
Hexa : C5BD EF8690 EF868F E28098 E280B0 C5A0 E2809D C5B8 C5BE C5B8 EF868D
C38F
Characters: é ê è ë â ä î ü û ü ç œ
Hexa : C3A9 C3AA C3A8 C3AB C3A2 C3A4 C3AE C3BC C3BB C3BC C3A7 C593
This is not a critical bug but it should be relatively easy to correct it since
both LibreOffice and Word display the right accentuated characters.
The attached file is a .rtf file dating back to 1990 and containing both a lot
of accentuated characters and some pict-images.
It was prepared on Mac OS (classic) with the vintage WriteNow 4.0
<https://en.wikipedia.org/wiki/WriteNow> which wrongly adds a space after each
accentuated character.
--
You are receiving this mail because:
You are the assignee for the issue.
[Issue 128550] Wrong accentuated characters from old .rtf files
Posted by bu...@apache.org.
https://bz.apache.org/ooo/show_bug.cgi?id=128550
Peter <pe...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #4 from Peter <pe...@apache.org> ---
yes, both are the same. Thanks !
*** This issue has been marked as a duplicate of issue 128549 ***
--
You are receiving this mail because:
You are the assignee for the issue.
[Issue 128550] Wrong accentuated characters from old .rtf files
Posted by bu...@apache.org.
https://bz.apache.org/ooo/show_bug.cgi?id=128550
Keith N. McKenna <kn...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |knmc@apache.org
Status|RESOLVED |CLOSED
--
You are receiving this mail because:
You are the assignee for the issue.
[Issue 128550] Wrong accentuated characters from old .rtf files
Posted by bu...@apache.org.
https://bz.apache.org/ooo/show_bug.cgi?id=128550
Matthias Seidel <ms...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mseidel@apache.org
--- Comment #3 from Matthias Seidel <ms...@apache.org> ---
(In reply to Peter from comment #2)
> And a test file would be nice... :)
There is one in issue 128549
This issue seems to be a duplicate?
--
You are receiving this mail because:
You are the assignee for the issue.
[Issue 128550] Wrong accentuated characters from old .rtf files
Posted by bu...@apache.org.
https://bz.apache.org/ooo/show_bug.cgi?id=128550
--- Comment #2 from Peter <pe...@apache.org> ---
And a test file would be nice... :)
--
You are receiving this mail because:
You are the assignee for the issue.
[Issue 128550] Wrong accentuated characters from old .rtf files
Posted by bu...@apache.org.
https://bz.apache.org/ooo/show_bug.cgi?id=128550
Peter <pe...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |petko@apache.org
--- Comment #1 from Peter <pe...@apache.org> ---
do you know what encoding has been used?
--
You are receiving this mail because:
You are the assignee for the issue.