Download it now!
Bug 118214 - FILEOPEN FILESAVE RTF treats MS language ID 1024 wrong
Summary: FILEOPEN FILESAVE RTF treats MS language ID 1024 wrong
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: filter:doc, filter:docx, filter:rtf
Depends on:
Blocks: RTF DOCX DOC DOCX-Character DOC-Character RTF-Character
  Show dependency treegraph
Reported: 2018-06-17 18:55 UTC by Phil Krylov
Modified: 2019-06-25 02:42 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

An RTF document to reproduce the bug (32.08 KB, text/rtf)
2018-06-17 19:07 UTC, Phil Krylov

Note You need to log in before you can comment on or make changes to this bug.
Description Phil Krylov 2018-06-17 18:55:33 UTC
The RTF specification says that language 1024 (0x400) denotes text without a language set. LibreOffice Writer treats \lang1024 in RTF as "Switch to system-default language" (English here) and does not switch off language proofing. Then, if one creates some text in Writer, sets its language to None and saves as RTF, Writer emits \lang255 for this text. \lang255 is not a valid (per RTF Specification) value. However, when an RTF text with \lang255 is open in Writer, it is treated as \lang1024 should be - that is, it sets text language to None.

Steps to Reproduce:
1. Open the attached RTF document (generated from MS Word).

Actual Results:
The word "proofeng" is visually marked as misspelled and when you put the caret on it is shows English (USA) as its language

Expected Results:
The word "proofeng" should not be marked as misspelled and its Language should be set to None

Reproducible: Always

User Profile Reset: No

Additional Info:
Build ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf
CPU threads: 4; OS: Mac OS X 10.9.5; UI render: default; 
Locale: en-US (en.UTF-8); Calc: group

A recent master build is still there:

Build ID: b292a27698e85fd9d60c03613c3b0c67835c4dc1
CPU threads: 4; OS: Mac OS X 10.9.5; UI render: default; 
TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-06-06_23:25:55
Locale: en-US (en.UTF-8); Calc: group threaded
Comment 1 Phil Krylov 2018-06-17 19:06:08 UTC
The bug is also seen when opening DOC and DOCX document.

I am not sure if I should file another bug for the RTF export issue (and probably DOC/DOCX as well). I hope there is a single place where both import and export can be fixed.
Comment 2 Phil Krylov 2018-06-17 19:07:39 UTC
Created attachment 142829 [details]
An RTF document to reproduce the bug
Comment 3 Buovjaga 2018-06-24 17:15:29 UTC

Arch Linux 64-bit
Build ID: 5b42a17dc99fba2ccf8dd8d0a8e0e4e836e30120
CPU threads: 8; OS: Linux 4.17; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded
Built on June 22nd 2018

Arch Linux 64-bit
LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-
Comment 4 QA Administrators 2019-06-25 02:42:46 UTC
Dear Phil Krylov,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat:

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team