Bug 140371 - autoinclude (in Exceptions tab of AutoCorrect Options) does not work for sMALL iNITIALS
Summary: autoinclude (in Exceptions tab of AutoCorrect Options) does not work for sMAL...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.3.0.4 release
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: AutoCorrect-Complete
  Show dependency treegraph
 
Reported: 2021-02-12 11:29 UTC by sdc.blanco
Modified: 2024-03-03 03:15 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sdc.blanco 2021-02-12 11:29:51 UTC
1. Tools > AutoCorrect > AutoCorrect Options - Options tab.
2. Uncheck all T options except for "Capitalize first letter of every sentence"
3. Switch to Exceptions tab, make sure "AutoInclude" is checked for  Correct TWo INitial CApitals or sMALL iNITIAL."
4. Make sure Tools > AutoCorrect > While Typing is enabled.
5. Enter a string that starts with a lower case (e.g.,  vPython)
   Actual and expected:  converted to Vpython
6. Undo

Actual Result:  vPython in document, but nothing in Exceptions list for " Correct TWo INitial CApitals or sMALL iNITIAL"

Expected result: vPython is added to Exceptions list, after Undo.
Comment 1 Buovjaga 2022-03-03 14:19:14 UTC
I reproduce (result is VPython, nothing added to exceptions).

Arch Linux 64-bit
Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: 896c097f1fa4bc9d2e5ea87a696c125bb335ecac
CPU threads: 8; OS: Linux 5.16; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded Jumbo
Built on 3 March 2022

Also in oldest of Linux 6.3 bibisect repo
Comment 2 QA Administrators 2024-03-03 03:15:08 UTC
Dear sdc.blanco,

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