This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigC489EACD4F60D963BE34BB65
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Philip Rodrigues napisa=C5=82(a):
>> Hm, I thought encoding problems have been solved many years ago.
>> Anyway, who is Phil and how can I contact him?
>=20
> That's me. Sorry for not getting back to you the first time. There are =
two=20
> issues with i18n/l10n and documentation in PDF: firstly, there's a litt=
le
> bit of autogenerated text (for example, "Chapter 1", etc) that needs to=
 be
> translated, or stolen from the DocBook->HTML stylesheets.=20

Thanks for the answer. While we are at it: where is this text and how
can I change the translation? The Polish translation is not very accurate=
=2E

> Secondly, we need
> to check that any formatting or page layout rules for the target langua=
ge
> are obeyed (and let's include in this bit that we have to check the
> handling of non-ASCII characters).

I don't understand :) I don't have much experience with these tools.
Can you just check which languages work and which don't and post the
results with some easy-to-follow steps, so we can solve these issues?

> There's a bit more information about this in the message I posted a whi=
le
> back:
> http://lists.kde.org/?l=3Dkde-i18n-doc&m=3D115090966330606&w=3D2

I have seen this thread but it got too technical with all these
db2latex, dblatex, etc.

Regards

	Krzysztof Lichota


--------------enigC489EACD4F60D963BE34BB65
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEznv9SHJB/1EhaUwRAt+wAJ4h1R9vX4+2hOhRzpAY6xcffx1gGACg8N1G
PTfzxS7W3F33w8pHlhvS8eM=
=B3s0
-----END PGP SIGNATURE-----

--------------enigC489EACD4F60D963BE34BB65--