https://bugs.documentfoundation.org/show_bug.cgi?id=161637
--- Comment #3 from László Németh <[email protected]> --- (In reply to V Stuart Foote from comment #1) > @László, OK but is there some ICU lib transliteration in i18n for handling > of the U+0027 as U+2019 in the "suggested" correction? > > Otherwise, the swap of U+2019 for U+0027 (as keyboard input) when > spell-checked seems like it should follow the Autocorrect 'Localized > Options' tab (by CLDR) for Single Quotes 'Start quote' and 'End quote' and > be an autocorrection after the spellcheck is applied. > > Just asking... Good question. Word processors support professional appearance more and more, see the new default font Aptos of MS Office with real optical sizes. Typewriter-style apostrophes dropped from document editing likely 20 years ago. I have enabled it, as default setting in LibreOffice 9 years ago. Using typewriter apostrophe does not comply with typographic and orthographic rules. A clear problem for Writer, that (likely most of) the users add their words with typographic apostrophe to the user dictionary, but they will get suggestions with typewriter apostrophe. Also the (already) UTF-8 English dictionary added apostrophe conversion for the input (instead of fixing the apostrophe in the dictionary), but forgot to convert the output: ~/libreoffice/dictionaries$ grep '[IO]CONV' en/en_US.aff ICONV 1 ICONV ’ ' Also for non-UTF-8 Hunspell dictionaries, the conversion is really i18npool or ICU-level, but also without restoring the lost typographic apostrophe. Also the (e.g. English) AutoCorrect rules use typographic apostrophe. For example, typing "shouldnt" is immediately replaced by "shouldn’t". I suspect that anyone who doesn't know the difference won't be bothered by the correct apostrophe, but I'm sure there will be far fewer dissatisfied users than there are now. But you are right, we need more flexibility to support all the users. I plan to fix Bug 138258/Bug 149630 (search for apostrophe and single quote), which is very annoying for several users, and related to this problem, too. -- You are receiving this mail because: You are the assignee for the bug.
