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


2011/11/21 Eike Rathke <erack@redhat.com>

Hi Yury,

On Saturday, 2011-11-19 21:19:43 +0200, Yury Tarasievich wrote:

Now, where do we get a template for the new format of locale?

Um.. what template? There are the i18npool/source/localedata/data/*.xml
files (see also

http://cgit.freedesktop.org/libreoffice/core/tree/i18npool/source/localedata/data)
for each locale, and the new optional <GenitiveMonths> element goes
right after the <MonthsOfYear> element. You could copy the entire
<MonthsOfYear> element, paste it after itself, rename it to
<GenitiveMonths> (don't forget the </GenitiveMonths> closing tag as
well) and edit the month names. Then send the diff (in this case it's
only the addition of the new element, so you could send just that if
you're not familiar with git diff and such).


Hi Eike

I need to change case from months name due to new Portuguese settlement for
spellcheck. Can I get file mentioned, change case and send it to You for
commit?

-- 
Sérgio Marques

-- 
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.