From kde-i18n-doc Sat Nov 26 23:35:33 2016 From: Chusslove Illich Date: Sat, 26 Nov 2016 23:35:33 +0000 To: kde-i18n-doc Subject: A note on proliferation kde-* format flags in catalogs Message-Id: X-MARC-Message: https://marc.info/?l=kde-i18n-doc&m=148020342710032 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--Kt33CS8OWPmMCNpT82eJafx5GPVovQeCX" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --Kt33CS8OWPmMCNpT82eJafx5GPVovQeCX Content-Type: multipart/mixed; boundary="I1gOAQ5vSUFKUgdc8SAaUsJ5I3Ogq69UT"; protected-headers="v1" From: Chusslove Illich To: kde-i18n-doc@kde.org Message-ID: Subject: A note on proliferation kde-* format flags in catalogs --I1gOAQ5vSUFKUgdc8SAaUsJ5I3Ogq69UT Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, Since the move to the new l10n server apparently also a newer Gettext package is used, and this had the result that now just about all messages throughout catalogs have kde-format flags, and some kde-kuit-format flags. The reason for this is that this is actually semantically correct. Unlike with other format types (e.g. c-format), every Ki18n message is a "format-applying" message, in the sense that Ki18n will at runtime do some interpretation on it. For example, now seeing kde-format flag the translator knows for sure that the message can be scripted (Transcript), and seeing the kde-kuit-format flag that semantic tags (KUIT) can be used in it. Also the checker tools can now decide what to do based on the format flag. The current Gettext maintainer, Daiki Ueno, was very kind some time ago to implement this. xgettext in --kde mode will now recognize all standard Ki18n call names (no need for the long list of -k options any more), and set the appropriate format flag according to call name (kde-format for *i18n* calls and kde-kuit-format for *xi18n* calls). --=20 Chusslove Illich (=D0=A7=D0=B0=D1=81=D0=BB=D0=B0=D0=B2 =D0=98=D0=BB=D0=B8= =D1=9B) --I1gOAQ5vSUFKUgdc8SAaUsJ5I3Ogq69UT-- --Kt33CS8OWPmMCNpT82eJafx5GPVovQeCX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAlg6HEYACgkQMSGXgigGr3ETogCeNiZKd+W6cHgPUbnyQexleuKv BE8AoKNnV11pHVUm5k7iC8s0b8+mOOve =6p0s -----END PGP SIGNATURE----- --Kt33CS8OWPmMCNpT82eJafx5GPVovQeCX--