Date: prev next · Thread: first prev next last
2020 Archives by date, by thread · List index


Dear fellow l10n teams,

There is a bug asking for improvement of spellchecking for text with mixed language [1].  The issue 
is that currently spellchecker takes space as separator between words, and then check the spelling 
of each word individually.  However in some language other characters may be used between words -- 
the bug reporter gave an example of mixing Italian and English, "Questo รจ un rapporto 
sull'International Conference on..." -- and the spellchecker obviously fail when two words of 
different languages are connected with such non-space separators.

As developers usually only speak a few languages, to get an idea of the bigger picture, opinions 
from l10n people are sought.  So if your language have some special rules for separating/connecting 
words/affixes, especially if your language also uses spellchecking intensively, please share your 
knowledge, either on this list or directly on Bugzilla.

1. https://bugs.documentfoundation.org/show_bug.cgi?id=131487

Regards,
Ming
-- 
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.