[Pkg-shadow-devel] Solution to translate shadow documentation

[Martin Quinson]

--ZOudaV4lSIjFTlHv
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 23, 2005 at 01:19:10PM +0100, Tomasz K?oczko wrote:
> On Wed, 23 Mar 2005, Martin Quinson wrote:
> [..]
> > Sure, that's just what Christian proposed. Why is he wrong?
>=20
> To Christian: sorry .. my mistake (tooday I have very hard day in work=20
> :>).

No problem, I guess, he's used to worse on the various debian ML he work on=
 ;)

> > > I'm not perform yet some experiments but probably for generate .po fi=
les
> > > from XML rerfentry can be used plain gettext because xgettext can han=
dle
> > > XLM files (I don't know now is it can handle refentry).
> >=20
> > Were did you get this information from? From the info xgettext, the lis=
t of
> > supported format are:=20
> > -L NAME'
> > --language=3DNAME'
> >      Specifies the language of the input files.  The supported languages
> >      are `C', `C++', `ObjectiveC', `PO', `Python', `Lisp', `EmacsLisp',
> >      `librep', `Smalltalk', `Java', `JavaProperties', `C#', `awk',
> >      `YCP', `Tcl', `Perl', `PHP', `GCC-source', `NXStringTable', `RST',
> >      `Glade'.
> >=20
> > (xgettext (GNU gettext-tools) 0.14.1)
>=20
> Glade files this XML files so some startup framework for sucking
> phrases without additional tools from XML files exist in xgettext.
>=20
> BTW: finish this for allow xgettext for fully operate on XML refentry
> and/or book will allow simplify for example translate all docbook LDP
> documentation. Few projects have now man pages in XML primary format=20
> (IIRC: gnupg, mc and few other).

The only issue is that the glade support is only in xgettext. That is to say
that there is no mecanism to reinject the translations into the xml file
afterward. Such a mecanism seems to be in place for java properties (from
what I see in source code, don't see how to use it in documentation).

If you follow that way (which I agree to feel appealing), we could recode
po4a to C in order to integrate it into gettext. It would be great, but we
do use a great deal of perl regular expressions for parsing.=20

And moreover, I'm rather happy with the po4a modular design, and it's
something which seems difficult to integrate in the existing gettext tool
suite as is. Please just check the two following links:
http://po4a.alioth.debian.org/en/Locale/Po4a/TransTractor.html
http://po4a.alioth.debian.org/en/po4a.7.html

That being said, I'm interested in merging po4a into gettext, if you have
any viable solution.

Thanks for your time,
Mt.

--ZOudaV4lSIjFTlHv
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iD8DBQFCQWZOIiC/MeFF8zQRAqHwAJ9uMqIbdo7iFUQ9mndi0f4VZkFK3QCfZzBN
sDYgUuAQ8hpQvEo/WkZ5pnI=
=DwzK
-----END PGP SIGNATURE-----

--ZOudaV4lSIjFTlHv--