Description: Language, font family, and font size of the Japanese characters in the attached file mess up after save to .rtf and reload. Steps to Reproduce: 1. Open the attached file. 2. Save it as .rtf 3. Reload Actual Results: Language of the Japanese text and Hebrew becomes Arabic (Egypt). The font family of Japanese text becomes Mangal. The font size become 10.5. Expected Results: The font family was MS UI Gothic and Verdana;Tahoma;Helvetica;Arial for Japnese and Hebrew text. The font size was 20 and 32. Reproducible: Always User Profile Reset: No Additional Info: 版本：6.4.6.2 (x64) 組建 ID：0ce51a4fd21bff07a5c061082cc82c5ed232f115 CPU 執行緒：16; OS：Windows 10.0 Build 18363; UI 算繪：GL; VCL: win; 語言地區：zh-TW (zh_TW); 介面語言：zh-TW Calc: CL
Created attachment 166889 [details] Source document for the test.
Created attachment 166890 [details] Side by side screen capture
Font family and language change reproducible in 版本：5.4.7.2 組建 ID：c838ef25c16710f8838b1faec480ebba495259d0 CPU 執行緒：16; OS：Windows 6.2; UI 算繪：GL; 語言地區：zh-TW (zh_TW); Calc: CL Font size change seems to be a newer regression.
Reproduced in: Version: 7.0.3.1 (x64) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded .rtf shows the following results on my system: Japanese text: Mangal, 10.5(black),12(red) Hebrew: Century Gothic, 12 English: Century Gothic, 10.5 Expected: Japanese text: MS UI Gothic, 10.5(black),20(red) Hebrew: Verdana;Tahoma;Helvetica;Arial, 32 English: Century Gothic, 10.5 Reproduced on an entirely new file too. Expected: Japanese text: NSimSun, 10.5 Hebrew: Arial, 12 English: Liberation Serif, 12 in .rtf is Japanese text: Arial, 12 Hebrew: Liberation Serif, 12 English: Liberation Serif, 12 *** This bug has been marked as a duplicate of bug 89491 ***
I tested and this is not a duplicate of bug 89491. Bug 89491 is about saving to .doc. If I save Mark's file to .doc, I don't see the problems that are shown with .rtf.
Mark Hung committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/f97af19460fbd7483a0e1c1d0137e814f5390e69 tdf#137894 separate associated character properties It will be available in 7.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Mark Hung committed a patch related to this issue. It has been pushed to "libreoffice-7-1": https://git.libreoffice.org/core/commit/efe85aa1ef4034ae70c50a256b491737199b8747 tdf#137894 separate associated character properties It will be available in 7.1.0.0.beta2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
I verify the fix Arch Linux 64-bit Version: 7.2.0.0.alpha0+ Build ID: 79ec66700266a22966d9e308a716be56c9c3a4a7 CPU threads: 8; OS: Linux 5.9; UI render: default; VCL: kf5 Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 30 November 2020
Created attachment 177932 [details] The original file and the roundtripped RTF in Writer This mostly looks good in Writer now, except the Hebrew text loses its green color and after reopen it's "automatic". On the attachment 166890 [details] you can see this was saved correctly some time ago -> regression.
Created attachment 177933 [details] The example files RTF version in Writer master and Word 2013 The Hebrew text looks quite differently in Word: * the RTL direction is not recognized - unlike in Writer * and the font becomes Mangal instead of Verdana.
Dear Mark Hung, 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 https://www.libreoffice.org/download/ 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 https://downloadarchive.documentfoundation.org/libreoffice/old/ 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: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug