Created attachment 171143 [details] Example of unreadable RTF file RTF files with tables are unreadable. Files are published by the Ukrainian government and meta info says it is produced by Crystal reports. http://www.dus.gov.ua/content/паспорти-бюджетних-програм-на-2021-рік
MS Word opens these files normally https://products.aspose.app/words/viewer also opens them without problems
Created attachment 171145 [details] Screenshot
Reoro 7.2+ Windows and Linux so not Mac related. This is 9 pages RTF that opens as 5 pages in Lo and garbled. There were changes but it was never fine from OO. Related to bug 59547 but I'll confirm as New. If resaved in MSO as DOCX, opens fine in LO.
On pc Debian x86-64 with master sources updated today, it takes quite some time to open (about 1 minute) and still garbled text. Miklos: thought you might be interested in this one since it concerns rtf. Of course, it's not rtf generated by Word and perhaps Crystal Reports does something wrong. On console logs, I just noticed several of these ones: warn:writerfilter:1680410:1680410:writerfilter/source/dmapper/DomainMapper.cxx:1293: DomainMapper::lcl_attribute: unhandled token: 0 warn:legacy.osl:1680410:1680410:svx/source/unodraw/unoshape.cxx:1942: SvxShape::GetAnyForItem() Returnvalue has wrong Type! warn:sw.core:1680410:1680410:sw/source/core/docnode/node.cxx:1985: Wrong cond collection, skipping check of Cond Colls.
Dear Denis Kurochkin, 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