--nextPart3176037.3tYx1OYddp
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

> [: 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=20
<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=20
would have to be able to resolve type of arguments in i18n call (to know=20
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 app=
s,=20
so given that problem would appear not only in translations, the feedback=20
loop is shorter than typical for i18n bugs.

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

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

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

=2D-=20
Chusslove Illich (=D0=A7=D0=B0=D1=81=D0=BB=D0=B0=D0=B2 =D0=98=D0=BB=D0=B8=
=D1=9B)
Serbian KDE translation team

--nextPart3176037.3tYx1OYddp
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBGNGtLMSGXgigGr3ERAsasAKCvWTClA8htWvzKro8/qjfy9XPUfQCeN/D/
bw9ktttr6LtnifbWvQzmEdo=
=JTDX
-----END PGP SIGNATURE-----

--nextPart3176037.3tYx1OYddp--