On Fri, 2012-02-24 at 17:28 +0100, Petr Vorel wrote:
First I thought it would be better to recode all of them to utf8. But
these files are taken from ispell, aren't they? Do we want to increase
diversity from upstream?
For hunspell dictionaries, the .aff files contain the encoding for
the .dic files, the .aff needs to be changed to specify UTF-8 if you
change the encoding of the .dic files. This tool though looks like its
for validating thesaurus files, though they probably have the same thing
where there's a field somewhere to indicate the encoding they are in.
Some of the hunspell dicts might share ispell lineage I guess, but
either way most of them and the thesauri have their own active upstreams
and so on, so yeah, changing the encoding just add unnecessary diversity
from their upstreams.
anyway, the last patch looks pretty minimal and it seems to make no
difference to the "typical" setup, so I pushed that now to dictionaries
C.
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.