On 5 October 2013 23:36, Andrea Pescetti <pesce...@apache.org> wrote:

> On 28/09/2013 janI wrote:
>
>> I will use "keyid".
>> Do you know if I need to change somewhere in the code itself also ?
>>
>
> I don't know. For a normal language it would probably make sense to have a
> look at
> main/i18npool/source/**localedata/data
> too, but in the case of "keyid" this is a fake language (we don't support
> text written in the "keyid" language, obviously) so it might be that what
> you did is enough.
>

Thanks for the hint it works on my ubuntu now (I really need to get the
windows build going). I needed to add a entry in
main/i18npool/source/localedata/data

It works real nice if you build with target language + keyid (or for now
kid), that way the translator can very fast switch between translated text
and keyid.


>  I have btw changed xx_XX to xx-XX in branch l10n40, so we dont have a mix
>> of _ and -.
>>
>
> main/i18npool/source/**localedata/data consistently uses underscores. On
> the other hand, the old "extras/l10n/source" consistently uses dashes... so
> I don't know which one is best here. If there's a way to adopt a common
> convention, very good.
>

This part uses underscores, but all texts have [ en-US ], so to make it
consistent will be a simple but large change that I think should be done
with "lazy consensus" before implementation.

rgds
jan I.

Regards,
>   Andrea.
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: 
> dev-unsubscribe@openoffice.**apache.org<dev-unsubscr...@openoffice.apache.org>
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Reply via email to