Problem description: when i finish a sentence with a number followed with a parenthesis or when the sentence is finished with a all caps word the next sentence does not start with a capital letter. the auto-correction option is on Steps to reproduce: 1. .... 2. .... 3. .... Current behavior: Expected behavior: Operating System: Windows 7 Version: 4.2.5.2 release
Created attachment 101741 [details] text with bugs
Confirmed in 4.2.5 and 4.3.0 on Linux Mint. Steps to reproduce: 1) Type "tomorrow, i'm going to be 5. but " all in smallcase 2) It will turn it into "Tomorrow, i'm going to be 5. but " The same goes for having parenthesis at before the period. Regarding the all caps word at the end of the sentence, i believe that if LibreOffice things the word is an actual word, it will auto-correct the following sentence. I tested this with "where are you going tomorrow JIMMY. what ".
(In reply to comment #2) > Confirmed in 4.2.5 and 4.3.0 on Linux Mint. reproducible under Win7x64 using 4.3.0.4 as well. > Steps to reproduce: > 1) Type "tomorrow, i'm going to be 5. but " all in smallcase > 2) It will turn it into "Tomorrow, i'm going to be 5. but " reproducible. > The same goes for having parenthesis at before the period. yes, but only with numbers followed by parenthesis. "See you later (come at 5). bye" "See you later (come at 5 o'clock). Bye" > Regarding the all caps word at the end of the sentence, i believe that if > LibreOffice things the word is an actual word, it will auto-correct the > following sentence. I tested this with "where are you going tomorrow JIMMY. > what ". I don't reproduce this. I get "where are you going tomorrow JIMMY. What ".
(In reply to comment #3) > I don't reproduce this. > I get "where are you going tomorrow JIMMY. What ". Yes that was an example of it working correctly, as previously mentioned, "LibreOffice thinks the word is an actual word, it will auto-correct the following sentence". I had an example of it not working, but cant seem to be able to remember what it was, as all the ones i try now seem to work. :)
I remember a bug report of someone complaining of lack of capitalization after some texts like CF. now I figure out that was becuase "cf." is listed under "Autocorrect Options/Exceptions/Abbreviations (no Subsequent Capital)" unfortunately I cannot find the exact bug number for that report
*** Bug 74887 has been marked as a duplicate of this bug. ***
Does this have something to do with numbering and abbreviations? Or is it because a number is not in the range of a-z? When using numbering, autocaptialise does not happen after the number unless the previous sentence or numbered item ends with a period. Any sentence ending with a number or letter (except I), and with or without parenthesis (opening and closing or just closing), before a period results in the first word of the next sentence not being capitalised. this is a test (a). this this is a test (A). this this is a test a). this this is a test a. this this is a test A. this this is a test (m). this this is a test m. this this is a test (aa). This <--(two letters and it capitalises) this is a tes (100). this this is a test (10000000). this this is a test 1). this 1. this is a test. <--(no numbering applied) (1). this is a test. <--(no numbering applied) 1). this is a test. <--(no numbering applied) this is a test 1a. This <--(number and letter and it capitalises) In a new document with numbering the first item is capitalised because that is the same as there not being any numbering. So: 1. Test 2. test 3. This is a test 1. test 2. test 3. This is a test. 1. Test 2. test. 3. Test 4. Windows Vista 64 Version: 4.4.3.2 Build ID: 88805f81e9fe61362df02b9941de8e38a9b5fd16
** 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.1.5 or 5.2.1 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-20160920
Dear josé faria, 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
Problem still present in LibreOffice 6.4.2.2
*** Bug 141470 has been marked as a duplicate of this bug. ***
*** Bug 152891 has been marked as a duplicate of this bug. ***
Hi there. Maybe it is possible to simply change some settings in a config file? These rules of capitalization must be written somewhere...
(In reply to Phagocytoz from comment #13) > Hi there. Maybe it is possible to simply change some settings in a config > file? These rules of capitalization must be written somewhere... Unfortunately not configurable, this is hard coded logic in one of several edit-engine sources that needs to be traced and refactored.