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


Hi,

2011/9/3 Juan Pablo Martínez Cortés <jpmart@unizar.es>:
Hi,
 I've been working with a colleague on a hunspell spellchecker for Aragonese
language (an_ES) that we'd like to integrate into libreoffice.   Which are
the steps to be followed?  Here you have a locale file.
http://www.it46.se/localegen/locale/1314999923_an_ES.xml

I tried to add your locale data but there were some errors and
warnings that you should correct first (or for the warnings, confirm
that they were intended).

Warning: ListSeparator equals DecimalSeparator.
Error: ListSeparator not ';' semicolon. Strongly recommended.
Currently required.
Warning: Time100SecSeparator is different from DecimalSeparator, this
may be correct or not. Intended?
Warning: Don't forget to adapt corresponding FormatCode elements when
changing separators.
Warning: QuotationStart may be wrong: U+201C “
Warning: QuotationEnd may be wrong: U+201D ”
Warning: DoubleQuotationStart may be wrong: U+2018 ‘
Warning: DoubleQuotationEnd may be wrong: U+2019 ’

Best regards,
Andras

-- 
Unsubscribe instructions: E-mail to l10n+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

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.