From kde-i18n-doc  Sun Oct 25 21:57:25 2009
From: Chusslove Illich <caslav.ilic () gmx ! net>
Date: Sun, 25 Oct 2009 21:57:25 +0000
To: kde-i18n-doc
Subject: Re: Why does kde-i18n-doc translate outdated documentation?
Message-Id: <200910252257.28537.caslav.ilic () gmx ! net>
X-MARC-Message: https://marc.info/?l=kde-i18n-doc&m=125650796128485
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1517255.SNWFbOOZm1"

--nextPart1517255.SNWFbOOZm1
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable

> [: Albert Astals Cid :]
> So basically you are proposing a way to do mediawiki -> po and po ->
> mediawiki and po -> docbook/html
>
> What all of us is proposing.

Well, naturally, but I tried to put it in more concrete terms, of who needs
to do what and who needs to maintain what, such that there is least headache
down the road. For example, I specifically do not require of documentation
maintainers to deal with PO files in daily workflow. (Of course, anyone's
welcome to write/find converters for specific formats, that we would use
internally.)

> I disagree however that having new untranslated documentation is
> acceptable.

I think new documentation will take some time to shape up, such that
hopefully there won't be much to translate before support from KDE TP side
is ready (the thingy that will fetch English and put translated documents,
and internal stuff).

=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

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

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

iEYEABECAAYFAkrkycYACgkQMSGXgigGr3G1ewCfeuNB+74q3zOGd4L44D+rIIvF
KOkAnjyLmvcEw9i2C4t42/cf9bzFQYIz
=t7PI
-----END PGP SIGNATURE-----

--nextPart1517255.SNWFbOOZm1--