Issue 128550 - Wrong accentuated characters from old .rtf files
Summary: Wrong accentuated characters from old .rtf files
Status: CLOSED DUPLICATE of issue 128549
Alias: None
Product: Writer
Classification: Application
Component: open-import (show other issues)
Version: 4.1.13
Hardware: Mac All
: P5 (lowest) Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-02 22:02 UTC by Alain Filhol (linus38120)
Modified: 2023-01-04 20:57 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Alain Filhol (linus38120) 2023-01-02 22:02:41 UTC 
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.
Comment 1 Peter 2023-01-02 22:58:21 UTC 
do you know what encoding has been used?
Comment 2 Peter 2023-01-02 23:00:24 UTC 
And a test file would be nice... :)
Comment 3 Matthias Seidel 2023-01-03 19:37:53 UTC 
(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?
Comment 4 Peter 2023-01-03 19:48:33 UTC 
yes, both are the same. Thanks !

*** This issue has been marked as a duplicate of issue 128549 ***