Created attachment 170472 [details] Footnote is good in Writer but broken in ms-word After recent updates, RTL footnotes that are added to ms-word files appear mirrored in ms-word (the order of the letters is reversed in each word). This is a serious regression. To reproduce: 1. Open an existing RTL ms-word file. 2. Add an RTL footnote, save and close. 3. Open the file in ms-word. Expected result: 1. The file looks the same. Actual result: 2. The footnote text is mirrorred (the letter order is reversed). I attach an example ms-word file showing the issue. The footnote is readable in Writer but not in MS-word (and somehow the original line is invisible as well - something really bad happened). This is a serious regresiion, blocking RTL interoperavility.
Yotam, I can see the difference. I assume, that the document has been created in LO Writer and saved as DOC-File, correct? Could you please add a sample odt-file (before saving as DOC)? This would make it easier for us to verify the bug. => NEEDINFO BTW: Regression is defined as "issues previously fixed but somehow broken again". So has it worked in a previous version of LO?
The document has been created in ms-word, and was edited in LO.
(In reply to Yotam Benshalom from comment #2) > The document has been created in ms-word, and was edited in LO. Is it possible for you to create a new document in LO with footnotes in Hebrew and to save it as doc and reopen in MS-Word. This will show, if it is a problem with LO or not. If it is possible for you to reprodce the problem this way, please attach odt-file. Thank you.
I can't reproduce it on my windows 10 environment, neither when adding the comment in ms-word nor when adddin it in LO (note that the buggy scenario was this: I received a document created by a client on ms-word\windows, I used LO\linux to add comments to it, and the text I added looked fine in LO but garbled on the client's ms-word\windows; I don't know exactly what ms-word or windows my client uses). This seems to me to be a regression, because I have been doing this for many years now, and the problem never occured before.
Sorry, correction - the problem was of course in footnotes, not comments.
Thank you for further explanation. I'm not familiar with such a case, so I don't want to assess, if it is a bug of LO or has it reason somewhere else. Buovjaga, how to proceed in such a case? cc: Buovjaga
(In reply to Dieter from comment #6) > Thank you for further explanation. I'm not familiar with such a case, so I > don't want to assess, if it is a bug of LO or has it reason somewhere else. > > Buovjaga, how to proceed in such a case? > cc: Buovjaga I think finding out the exact MSO version used to create the .doc would be nice.
My client sent me his MSO version: MS Word 2003 (11.8169.8172) SP3 (MSO Proffessional Edition)
So the next step is to have a clean version of the document that has not yet been edited by LO. Can you provide the original document as your client gave it to you? (And please first confirm that adding a footnote to this document does produce the problem described here before adding the unedited file.) Better yet would be finding out how to reproduce this from scratch, but that might be difficult. Another thing to try would be some older documents that worked before - do they also break now, or is it just something about this particular document?
Created attachment 170938 [details] Original file as received from sender The file is attached.
(Sorry for not checking again for the bug - usually I do not have access to a Windows system).
I can reproduce it with Version: 7.1.2.2 (x64) / LibreOffice Community Build ID: 8a45595d069ef5570103caea1b71cc9d82b2aae4 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL Steps to reproduce: 1. Open attachment from comment 10 in LO 2. Add a RTL footnote (I took the first line of the footnote in attachment 170472 [details]) 3. Save and close 4. Open in MS Word (Word 2016)
Dear Yotam Benshalom, 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
Looks good to me with Version: 7.5.3.1 (X86_64) / LibreOffice Community Build ID: d29ee673721b12c92b3de9b9663473211414f0db CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded Saving as doc-file and open in MS Word 365 Yotam, could you please retest?
(In reply to Dieter from comment #14) > Yotam, could you please retest? YOTAM, let's change to RESOLVED WORKSFORME for the moment. Feel free to change it back to NEW, if you can still reproduce it in a 7.5.3 or newer.
Works for me as well with LO 7.4 on Windows 64bit.