Description: This appears to be a regression of a bug 38242 previously reported and fixed/closed. Using the default setting for ordinal superscript suffixes no longer works. For example typing April, 22nd, 2021 no longer will cause the "nd" to become changed to a superscript font when (the default setting of): Tools -> Autocorrect -> AutoCorrect Options... (dialog) -> Localized Options (tab) -> Format ordinal numbers suffixes is Checked Steps to Reproduce: 1. Make sure the option Tools -> Autocorrect -> AutoCorrect Options... (dialog) -> Localized Options (tab)-> Format ordinal numbers suffixes is Checked (both checkboxes) 2.Type April 22nd, 2021 Actual Results: Observe that the "nd" suffix on 22nd does not become "superscripted" as it should Expected Results: The "nd" suffix becomes auto-corrected to use a superscript font when keying whitespace following the suffix. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.0.4.2 Environment: CPU threads: 8; Os: Linux 5.10 User interface: UI render: default; VCL: gtk3 Locale: en-Us(en_US.UTF-8);UI: en-US Misc: Calc: threaded
I can't confirm this with Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 21c602913d98ef46b49fc9b6f9071db92a1597c6 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL Make sure, that you use a language, that have the convention of formatting ordinal numbers as superscript [1]. English should work for you. Does this solve your problem? => NEEDINFO [1] https://help.libreoffice.org/7.2/en-GB/text/shared/01/06040400.html?System=WIN&DbPAR=WRITER&HID=cui/ui/applylocalizedpage/ApplyLocalizedPage#bm_id59906554
Well I did nothing that I can think of to fix it but now I can no longer reproduce this problem. I keep a journal and I type the date each entry, the story is suddenly this feature stopped working, but now it's working. Same document, same OS and machine. I would suggest that this problem might be sporadic and hard to reproduce, but if it happens again I'll keep this bug number written down for further reference. Thank you very much
(In reply to Chris Kaltwasser from comment #2) > Well I did nothing that I can think of to fix it but now I can no longer > reproduce this problem. => RESOLVED WORKSFORME