[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: [libkunitconversion] Currenciess pluralss
From:       John Layt <johnlayt () googlemail ! com>
Date:       2009-12-04 14:33:56
Message-ID: 200912041433.56957.johnlayt () googlemail ! com
[Download RAW message or body]

On Thursday 03 December 2009 05:31:41 Yuri Chornoivan wrote:
> написане Thu, 03 Dec 2009 02:42:56 +0200, John Layt
> 
> <johnlayt@googlemail.com>:
> > 3) The synonym list will only have correctly capitalised names and no
> > repeated
> > lowercase versions.  The Currency Code will no longer be translated and
> > the
> > Country Name and Currency Name will come from KLocale and KCurrencyCode
> > already translated.  So only the unit names will be left to be
> > translated,
> > i.e.
> > 	"schilling;schillings;ATS;ats;Austria;austria" => "schilling;schillings"
> 
> I am not sure, does this mean that conversions like "1.23 USD > ATS" will
> no longer be valid?

It will still work as the Currency Code will be appended onto the end of the 
synonym list untranslated, the Currency Name and Country Name will also be 
appended, but will already have been translated elsewhere.  So the only part 
of the string actually needing translation will be the unit names.

This is based on the assumption that no languages currently translate the 
Currency Code in KSpread.  If you do want to be able to use local synonyms for 
the Currency Codes, then I will add the code to the translatable part of the 
string again, as well as having an untranslated code appended.  As mentioned 
in 1), when used as a key the Currency Code must stay untranslated for 
interchange purposes.

The code could look like either:

    i18nc("unit synonyms for matching user input",
          "schilling;schillings;%1;%2;%3",
          "ATS",
          KGlobal::locale()->countryCodeToName("at"),
          KCurrencyCode::currencyCodeToName("ATS"))

or

    i18nc("unit synonyms for matching user input", "schilling;schillings") +
    ';' + "ATS" + ';' +
    KGlobal::locale()->countryCodeToName("at") + ';' + 
    KCurrencyCode::currencyCodeToName("ATS");

> What about making difference between e.g. Belgian and French francs?



> > 4) The author is now wondering if the SI unit symbols like kg (kilogram)
> > and
> > mm (millimeter) should be translated or not?  I'm not sure, but I think
> > they
> > should be.  Would an Arabic speaker write kg or something in Arabic
> > script?
> 
> Please do not remove them. They definitely be translated. For example, at
> least in Ukrainian and Russian kg is *always* translated as "кг".

Cool, that's what I thought.

Cheers!

John.

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic