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

List:       kde-i18n-doc
Subject:    Re: Number localization in KDE4
From:       Chusslove Illich <caslav.ilic () gmx ! net>
Date:       2007-04-29 9:54:19
Message-ID: 200704291154.19656.caslav.ilic () gmx ! net
[Download RAW message or body]


> [: Krzysztof Lichota :]
> Maybe if it was more enforced (Krazy check?), it would be used.

Hm, Krazy check would mean that every number has to be either marked by 
<amount> or <numid>, no default (since the script cannot decide).

But worse, I don't really know how the check would be made, as the script 
would have to be able to resolve type of arguments in i18n call (to know 
which are numbers), which seems highly non-trivial to me.

> I think it will bite much more translators and users than developers. I
> know (and you probably too) how long it might take to correct and i18n
> bug in apps.

One thing is that I do expect the developers to be prime users of their apps, 
so given that problem would appear not only in translations, the feedback 
loop is shorter than typical for i18n bugs.

Then, I don't know if you take that into account, if the translator clearly 
sees that an unmarked number is not an amount but an identifier, nothing 
stops him from using <numid> in the translation.

Also, some easy Krazy checks could be done here. One would be to detect 
classic numeric id's, i.e. by seeing "...port %1..." or "...line %1..." 

Another possibility would be for a script to go through translations and look 
out for any message that has extra semantic tags in the msgstr compared to 
msgid. Then, it could automatically notify developers about translators' 
semantic corrections, including the missing <numid> in case of numbers. 
Though this really wouldn't be appropriate for Krazy, but for something I'm 
currently just having a rough mental sketch of, codename Transglas (i.e. 
Transgłos :)

-- 
Chusslove Illich (Часлав Илић)
Serbian KDE translation team

[Attachment #3 (application/pgp-signature)]

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

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