In LO 5.2+, goto: Options > Language settings > english sentence checking > others. You can now click on 'convert to metric' and 'convert to non-metric' at the same time. I think these conflict with each other. You either have one or the other, but not both.
Just to be clear, to repro I need http://extensions.libreoffice.org/extension-center/languagetool installed?
(In reply to Buovjaga from comment #1) > Just to be clear, to repro I need > http://extensions.libreoffice.org/extension-center/languagetool installed? No, I don't have any extensions installed. Some systems might not have the 'english sentence checking' as option in prefs. LO language (user interface / LO setting) is set as 'Default - English (USA)'.
Created attachment 127649 [details] conflicting options
Did you check you don't have Languagetool (or some similar extension) installed? I don't see the option entry even though I have English (USA) as the UI language. I see no other way of getting the entry except installing such an extension: http://askubuntu.com/questions/525544/libreoffice-english-sentence-checking-option-missing
I see the option in 5.2.2.2 / Windows 7. I wonder what's the user-friendly way to have it look. First of all, bring the options next to each other. Is any kind of visual aid needed to show the two settings belong together? (and basically function as a 3-way switch) Jay, what are your thoughts?
I'd say they should likely be radio buttons rather than checkboxes. @Stuart, @Adolfo, @Cor, @Heiko: What you guys think?
(In reply to Yousuf Philips (jay) from comment #6) > I'd say they should likely be radio buttons rather than checkboxes. that is what one would expect. Looking in the Help, I see no explanation.
(In reply to Yousuf Philips (jay) from comment #6) > I'd say they should likely be radio buttons rather than checkboxes. Metric is mutually exclusive to _imperial_ units, no question. But I still do not know how to get these aids.
(In reply to Yousuf Philips (jay) from comment #6) > I'd say they should likely be radio buttons rather than checkboxes. > Yes, a radio button with none/metric/non-metric will do fine.
Before we get to excited about this, can anyone point to where in source the Lightproof grammar checker performs the filtering? Couldn't find it yet, but suspect the two filter sets are not exclusive--so should not (can not?) be linked action via radio button. And check boxes must remain.
Well, it's true that you could mix metric and non-metric units in a text, and then have the checker suggest conversion for both kind of units.
(In reply to Aron Budea from comment #11) > Well, it's true that you could mix metric and non-metric units in a text, > and then have the checker suggest conversion for both kind of units. An added option for 'both' then ?
(In reply to MM from comment #12) > (In reply to Aron Budea from comment #11) > > Well, it's true that you could mix metric and non-metric units in a text, > > and then have the checker suggest conversion for both kind of units. > > An added option for 'both' then ? Or just leave things as they are with check-boxes. But move the two entries adjacent rather than split by the "Thousand separation of large numbers" entry.
** 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
still in 6.2-master
(In reply to V Stuart Foote from comment #13) > Or just leave things as they are with check-boxes. But move the two entries > adjacent rather than split by the "Thousand separation of large numbers" > entry. As it doesn't seem to hurt either.. @mm: what is your idea now?
Dear MM, 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
Dear MM, 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
Behavior still present in: Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 450471ebbdbff40998509731028b28e0ada53f58 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: da-DK (da_DK); UI: en-US Calc: CL But in light of discussion here -- maybe this is NAB?
If a documentation issue, then see bug 143754
Dear MM, 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