Description: In an odt-document from a friend I discovered false character counting. My analysis showed that in a line-feed are 65535 hidden spaces. During the analysis the attempt to replace double-spaces by single-spaces Writer hung up. Attached is a modified screen shot of the problem. I asked the author for the permission to upload the file for further analysis. Steps to Reproduce: 1. Open document 2. 3. Actual Results: Open document Expected Results: same as before Reproducible: Always User Profile Reset: No Additional Info: Version: 6.4.0.3 (x64) Build-ID: b0a288ab3d2d4774cb44b62f04d5d28733ac6df8 CPU-Threads: 4; BS: Windows 10.0 Build 18363; UI-Render: Standard; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: threaded
Created attachment 157990 [details] screen shot
(In reply to Dirk Stumpe from comment #0) > During the analysis the attempt to replace double-spaces by single-spaces > Writer hung up. I assume, this is a second issue and it is not part of the bug report, right? Steps to reproduce are not clear to me. I tried the following 1. Open an existing odt-file 2. Select all 3. Open word count from statusbar Actual result: Character counting between selection and document is different Are this the correct steps? There are also some bug reports with the same topic. Perhaps your report is related to them. Please see list in https://bugs.documentfoundation.org/showdependencytree.cgi?id=103479&hide_resolved=1
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Created attachment 158014 [details] odt-file with strange character count This is the document where the character count error occured. I unpacked it and found in content.xml this entry at the location marked in uploaded JPG: <text:s text:c="65549"/> The author wanted a linefeed at this position. I don't know what happened, maybe there was some text before. Or the doc was converted to MSW2003, edited and reimported.
(In reply to Dieter from comment #2) > (In reply to Dirk Stumpe from comment #0) > > During the analysis the attempt to replace double-spaces by single-spaces > > Writer hung up. > > I assume, this is a second issue and it is not part of the bug report, right? > > > Steps to reproduce are not clear to me. I tried the following > 1. Open an existing odt-file > 2. Select all > 3. Open word count from statusbar > > Actual result: Character counting between selection and document is different > > Are this the correct steps? There are also some bug reports with the same > topic. Perhaps your report is related to them. Please see list in > https://bugs.documentfoundation.org/showdependencytree. > cgi?id=103479&hide_resolved=1 I don't know if this is another issue or the result of the miscounting. Your steps are correct, but this is the first time I detected this problem. Pls see my last comment with the file.
I confirm ith with Version: 6.3.4.2 (x64) Build-ID: 60da17e045e08f1793c57c00ba83cdfce946d0aa CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: threaded and the document from comment 4. Number of words is the same in selection and document, but number of character differs. There are also no informations in LO help about character counting.
I don't know much of LO-XML. But I assume that <text:s text:c="2"/> represents two blanks. With this in mind <text:s text:c="65549"/> should show a large white area, but LO doesn't.
Dear Dirk Stumpe, 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
Still present in Version: 7.6.3.2 (X86_64) / LibreOffice Community Build ID: 29d686fea9f6705b262d369fede658f824154cc0 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-GB (de_DE); UI: en-GB Calc: CL threaded Steps: 1. Open attachment 158014 [details] 2. Status bar shows 300 words and 68.388 characters 3. Strg+a Expected result Status bar shows 300 words and 68.388 characters Actual result Status bar shows 300 words and 68.374 characters
I've just recognized, that there is something wrong with the document. After second part of thext there are aroung 65.000 spaces. If you delete them, problem disappears. So I would say NAB