I request a way to define default values by language for Autocorrect localized options. Case: Tools>AutoCorrect>AutoCorrect Options…>Localized Options, “Format ordinal numbers suffixes (1st → 1^st)” is enabled as default for **all** languages. For Catalan (and maybe other languages), it should be disabled by default or alternatively permanently. I can disable this option at user's profile, but I didn't find any way to disable this Autocorrect option for Catalan language as default.
This and some other options should be customizable with/during installation (langpacks or language versions of LO).
In some languages such constructs, or transformations, are meaningless anyway. Hebrew doesn't have an equivalent of "1st"; you have ראשון (meaning first) and that's that. I _think_ there is no such thing in Arabic but I'm not 100% sure. In fact, I wonder how many languages _do_ have this...
(In reply to Martin Srebotnjak from comment #1) > This and some other options should be customizable with/during installation > (langpacks or language versions of LO). AutoCorrect options are about _document content_, not UI languages, so having that depend on langpacks doesn't make sense.
László Németh committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/4c7686b7e1f4d012c00892f1cac1ae8a3298da5a tdf#156792 sw Catalan AutoCorrect: no superscript ordinal indicator It will be available in 24.8.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
I've disabled the (partial) superscript for Catalan (it was already for Swedish). Note: It's possible to do for other languages, which have letter-only ordinal indicators defined in i18npool/ICU, but without superscript formatting, if they exist. I've close this report, because the known problem has been solved. @Joan et al.: thanks for your report and feedback!