From kde-i18n-doc  Sat Nov 29 22:44:59 2014
From: Chusslove Illich <caslav.ilic () gmx ! net>
Date: Sat, 29 Nov 2014 22:44:59 +0000
To: kde-i18n-doc
Subject: Re: xi18n, frameworks and KStars
Message-Id: <201411292344.59912.caslav.ilic () gmx ! net>
X-MARC-Message: https://marc.info/?l=kde-i18n-doc&m=141730112627269
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart2978653.RsHQmqTgCy"

--nextPart2978653.RsHQmqTgCy
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable

> [: Burkhard L=C3=BCck :]
> What is the difference between i18n*() and xi18n*() and what's their use
> cases?

The difference is in the amount of processing done to the text. i18n*() only
replaces argument placeholders with values, if any. This is what most
programmers want. xi18n*() additionally process XML-like (KUIT) markup,
transforming text into target formats as instructed. There are some built in
tags and formats, and programmers can define new tags and target formats.
=46ew programmers have expressed desire for something like this.

The i18n*() from KDE 4 is in fact nearer to xi18n*() from KF5, only more lax
with respect to markup treatment. This was causing unexpected behavior for
many programmers who didn't want to use KUIT markup. Since KUIT markup was
used very little, in KF5 markup processing was removed from basic i18n*(),
and put into xi18n*().

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

--nextPart2978653.RsHQmqTgCy
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEABECAAYFAlR6TGsACgkQMSGXgigGr3G0kQCfYZ4LAnHwUGW0TivHRfg49WRd
NgAAoJLAu+vVpEJDpbb9O+4Zkxui4yJ3
=GmSN
-----END PGP SIGNATURE-----

--nextPart2978653.RsHQmqTgCy--