Created attachment 74033 [details] A file that shows LibreOffice not rendering apostrophe correctly Problem description: Steps to reproduce: 1. Open Write activity from Sugar 2. Type some text that includes an apostrophe (') 3. Press "Export to TXT" (Exported with Write activity v86 on XO-4 Touch, Build 1.5.0 for XO-4 One Education OS 1.5 build 3) 4. Use Journal to copy over to a USB stick 5. With the USB stick, copy the TXT file 6. Rename the file, adding ".txt" to the end of the file so it will open in Windows (OE OS bug) 7. Right click on the renamed file, and select "open with" 8. Select LibreOffice Writer 9. The apostrophes renders ’ instead of ' 10. Right click on the renamed file, and select "open with" 11. Select Notepad 12. The apostrophe renders ' Note: File is included Note2: This may possibly be reproduced in Abiword, as Write activity is based on Abiword Current behaviour: apostrophe renders as ’ Expected behaviour: apostrophe renders as ' Operating System: Windows 7 Version: 3.6.5.2 rc
You can also report a bug in Abiword, but I wouldn't expect anything constructive from that bunch.
** 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 (4.4.0.3 or later): 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) Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-02-19
Created attachment 113600 [details] screencopy of the bugdoc in LO 4.4.2.0.0+ I do not reproduce the problem with LibreOffice 4.4.2.0.0+ built at home under Ubuntu 14.10. It works fine too in versions 4.1, 4.2 and 4.3. Best regards. JBF
Closing as WorksForMe. Please feel free to reopen if you still experience this problem with current stable versions. Best regards. JBF
I am using LibreOffice 5.3.2.2 (x64) with Windows 7. And this bug still affects me. The standard encoding for .txt files without BOM should be utf-8 as the Unicode Standard does not require or recommend the use of BOM.
*** Bug 108941 has been marked as a duplicate of this bug. ***
** 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 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 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: 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
A code pointer: SwASCIIParser::ReadChars() in sw/source/filter/ascii/parasc.cxx does the autodetection of the encoding (of a 4 KiB buffer) using SwIoSystem::IsDetectableText. The latter only checks for BOM. I suppose we should not change that, but change the following processing (in case when currentCharSet == RTL_TEXTENCODING_DONTKNOW). In that case, we should possibly try treating the file as UTF-8, with options that strictly detect invalid sequences, and in case of failure, restart with RTL_TEXTENCODING_ASCII_US (or maybe user/working locale?).
Tomofumi Yagi committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/ef77a256de527f6d00212839e55f949024f2e7bc tdf#60145 sw: fix UTF-8 encoding without BOM is not detected It will be available in 7.1.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.
Hi Tomofumi Yagi, thank you very much for fixing this issue. Could you please add it to the release notes of LibreOffice 7.1 < https://wiki.documentfoundation.org/ReleaseNotes/7.1 > ?
(In reply to Xisco Faulí from comment #10) > Hi Tomofumi Yagi, > thank you very much for fixing this issue. Could you please add it to the > release notes of LibreOffice 7.1 < > https://wiki.documentfoundation.org/ReleaseNotes/7.1 > ? Thank you for your advice. I added it to the release notes of LibreOffice 7.1 https://wiki.documentfoundation.org/ReleaseNotes/7.1#Writer