Bug 77770 - FILEOPEN: bad display of cyrillic text in .rtf
Summary: FILEOPEN: bad display of cyrillic text in .rtf
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: All Windows (All)
: medium major
Assignee: Not Assigned
Depends on:
Reported: 2014-04-22 15:26 UTC by Ivan
Modified: 2015-02-12 17:06 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

not specified encoding (10.90 KB, application/rtf)
2014-04-22 15:26 UTC, Ivan
Normal visualization .rtf in Microsoft Word Viewer (79.63 KB, application/pdf)
2014-04-22 15:28 UTC, Ivan

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan 2014-04-22 15:26:53 UTC
Created attachment 97754 [details]
not specified encoding

I can not read file .rft (encoding), but in the MS 2003 no problems.
Comment 1 Ivan 2014-04-22 15:28:11 UTC
Created attachment 97755 [details]
Normal visualization .rtf in Microsoft Word Viewer
Comment 2 tommy27 2014-04-22 18:23:52 UTC

I can load your test .rtf file in LibO under Win7x64 however I do not see cirillic fonts rendered as in the .pdf version (maybe I don't have the proper font installed)

so, what do you exactly mean "I can not read .rtf (encoding" 

do you receive error messages or it's all about bad rendering?

could you pleas post a screenshot of what you see in LibO?

set status to NEEDINFO, revert it to UNCONFIRMED once you answer my questions.
Comment 3 Ivan 2014-04-22 19:44:04 UTC
Comment 4 tommy27 2014-04-23 05:34:41 UTC
thanks. so it's exactly the same issue I see.
I set status to NEW.

I also change summary notes from:
FILEOPEN: not specified encoding

FILEOPEN: bad display of cyrillic text in .rtf

I've reproduced the bug with older LibO releases (till  3.3.3) and it behaves the same even in OOo 3.3.0 and AOO 4.0.0 so this bug seems inherited from OOo

I also add a developer with expertise in .rtf files to CC-list.
Comment 5 tommy27 2014-04-23 05:44:43 UTC
seems the same old issue reported here. let's continue discussion over there.

*** This bug has been marked as a duplicate of bug 51898 ***
Comment 6 Urmas 2014-04-26 16:46:42 UTC
This bug is unrelated to 51898. The operator used a very old TT font made for compatibility with English Windows 3.1. It maps Cyrillic glyphs to Latin-1 codepoints. In RTF file it appears like a valid Latin-1 font, so it cannot be worked around easily.