Quoting Vincent Danjean ([EMAIL PROTECTED]):
> > I would therefore suggest having one of the two labelleed as "es" and
> > the other one kept as is.
>
> I will then keep es and es-ve. It seems more logical to me. I will however
> check that es_ES does not have less translations than es_VE : I jus
Christian Perrier wrote:
> Quoting Vincent Danjean ([EMAIL PROTECTED]):
>> Ok. Many thank for all your information.
>> So, unless collision, I keep only the two letters in the debian package name.
>> The exceptions for now are:
>> - es-es
>> - es-ve
>
> I don't agree with those. From what I heard
2008-08-20 (수), 02:08 +0800, Arne Goetje:
> Christian Perrier wrote:
> > Of course the very quirky way of upstream to name its files does not
> > help. Have they ever heard about ISO 639 and ISO 3166?
>
> It's not quirky at all. In fact they are very correct, and in many times
> "over-correct" (s
Quoting Vincent Danjean ([EMAIL PROTECTED]):
> I would add that I recall discussions on their ML about introducing variants
> for
> the French language itself. The fact is that, depending on the context, some
> strings may need to be translated differently. So it is possible that, in the
> future
Arne Goetje wrote:
> Christian Perrier wrote:
>> Of course the very quirky way of upstream to name its files does not
>> help. Have they ever heard about ISO 639 and ISO 3166?
>
> It's not quirky at all. In fact they are very correct, and in many times
> "over-correct" (see: RFC 4646). They simpl
Christian Perrier wrote:
> Of course the very quirky way of upstream to name its files does not
> help. Have they ever heard about ISO 639 and ISO 3166?
It's not quirky at all. In fact they are very correct, and in many times
"over-correct" (see: RFC 4646). They simply state the language, writing
Quoting Vincent Danjean ([EMAIL PROTECTED]):
> Upstream store its language dependent files in repository with
> non-classical names. For example: ar-Arab, bg-Cyrl, fr-FR, zh-Hans-CN, ...
> I made a debian/rules target to automatically update debian/control
> and debian/koha-l10n-XXX.install file
Hi,
I'm currently preparing the packaging of the Koha software (an
Integrated Library System).
There is already a support for a big number of languages upstream.
I'm coming here to get advices about the packaging.
Upstream store its language dependent files in repository with
non-classica
8 matches
Mail list logo
