Bug 170563 - Autocorrect exception fails for 'TWh/a'
Summary: Autocorrect exception fails for 'TWh/a'
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
25.8.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: AutoCorrect-Complete
  Show dependency treegraph
 
Reported: 2026-02-02 01:26 UTC by john
Modified: 2026-02-02 13:19 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 john 2026-02-02 01:26:57 UTC
Description:
I have added 'TWh' and 'TWh/a' (terawatt-hours and terawatt-hours per annum) to my LibreOffice Autocorrect exceptions (in Impress, specifically). The TWh one works as expected. The TWh/a one does not; even once it is added there, the autocorrect continues to modifiy to 'Twh/a' every time I type it. Seems that the non-alpha character '/' is messing up the autocorrect logic. 

Steps to Reproduce:
1. new Impress doc
2. new text box
3. enter 'TWh TWh/a ' (including the final space)
4. text is autocorrected to 'Twh Twh/a'
5. add 'TWh' and 'TWh/a' to autocorrect exceptions (under 'words with two initial capitals' or small initial')
6. enter 'TWh TWh/a ' (including the final space)


Actual Results:
(7.) the text is autocorrected to 'TWh Twh/a' (note the 'w' in 'Twh/a')

Expected Results:
(7.) the text should remain un-autocorrected.




Reproducible: Always


User Profile Reset: No

Additional Info:
Nil
Comment 1 V Stuart Foote 2026-02-02 13:19:09 UTC
Confirmed. 

Even entering the specific "TWh/a" in the "Words with TWo INitial CApitals..." AC Exceptions tab list box does not avoid the autocorruption.

This sort of makes sense, the TWh/a string could not match the two initial string correction bcz the "/" is not a word bound?

Just seems odd bcz logic for the AC "Replace" tab accepts the exact string including the "/".

But, simple workarounds:

1. After the space word bound (or an enter key) an immediate <Ctrl>+Z OR the 'Undo' button on the standard toolbar will correct.

2. Alternatively, you could disable the 'Correct TWo INitial CApitals' checkbox on the "Options" tab.

@Mike? Is the workaround sufficient and this a dupe of bug 74937? Or is there something that could be done for the Two initial caps logic to allow specific non-alpha characters to be included for the match?


=-testing-=
Version: 25.8.4.2 (X86_64)
Build ID: 290daaa01b999472f0c7a3890eb6a550fd74c6df
CPU threads: 28; OS: Windows 11 X86_64 (build 26200); UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded