Created attachment 123943 [details] Sample showing monospace font and strikethrough text This file - as with all from the site it comes from, isn't rendered nicely with LibreOffice. Text is in a monospace font, and from a few lines in, all has the strikethrough effect enabled. Document renders much better in WPS (for once!) Version set to 5.0.0.5, though I believe the bug has been around for a LOT longer. Also tested in the latest daily, with no difference.
Also of interest is that apostrophes seem to be stripped from the text, and the strikethrough starts where the first apostrophe in the text is...
I can confirm with Version: 5.2.0.0.alpha0+ and Version 4.0.0.3 in terminal: :1: parser error : Document is empty SchoolsLive Session
This is a plain text file, and has nothing to do with RTF. :-) In a dbgutil build I also see: OdtGenerator: Document Body: Finished writing all doc els.. So probably the strikethrough text is caused by one of the DLP import libs volunteering to import the doc and then not handling plain text input. David: any idea? ;-)
The most likely culprit is WordPerfect 4 import in libwpd. That format is just a plain text with inserted control characters.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
Dear Nicholas van Oudtshoorn, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still present. This might just have been a malformed download (from a website that no longer exists). Even so, it would be nice for the filters to fail gracefully when there is just plain text. Version: 7.0.0.0.alpha1+ Build ID: 97e9b250426ff09bba4546835ee9138d91e03fbb CPU threads: 4; OS: Linux 5.6; UI render: Skia/Vulkan; VCL: kf5; Locale: en-AU (en_AU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-05-19_08:36:14 Calc: threaded
(In reply to Nicholas van Oudtshoorn from comment #7) > Still present. This might just have been a malformed download (from a > website that no longer exists). Even so, it would be nice for the filters to > fail gracefully when there is just plain text. Well, WordPerfect 4.2 document *is* just plain text: pure ASCII, with 15-20 characters from the 0x80-0xff range acting as function codes that handle basic text formatting. So no, the libwpd filter cannot "fail gracefully", because there's simply nothing by which it could tell the file is not a WP 4.2 document (it would reject the file if it contained only ASCII characters, but that's not the case here). Btw, the libwpd filter (along with all the other filters) is only tried because the file does have extension .rtf instead of .txt . If I rename it, LibreOffice opens it directly using its plain text filter. (I still have to pick the "Text - Choose Encoding" file type and then choose the right encoding to make it look right, but that's "plain text" for you--there's no way around this.) Btw 2, LibreOffice (and OpenOffice.org before it) has been opening plain text files using a monospace font since forever. That has nothing to do with another filter being used.
Sounds good! A bad source document - from a web site that's been retired. Thanks for the time, David.