[Pkg-shadow-devel] Re: Please push shadow-4.0.3-31sarge2 to sarge

[Tomasz Kłoczko]

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--568760595-649903725-1113844898=:4344
Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-2
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-ID: <Pine.LNX.4.61L.0504181925091.4344@boss.zie.pg.gda.pl>

On Mon, 18 Apr 2005, Christian Perrier wrote:

> > > I'll try to make again a release with the Dutch fix, because it
> > > affects d-i usability. I'll also correct the now wrong man page, of
> > > course.
> >=20
> > This typo was fixesd by me in upstream source tree in 1.19 revision thi=
s
> > file (2005/03/31).
>=20
> However, Tomasz, you may want to look at Colin's suggestion to improve
> English in that sentence. At this moment, I have put this:
>=20
> .IP "\fB-o\fR"
> When used with the \fI-r\fR option, this option allows to change the user=
 ID to a non-unique value.
>=20
> Not sure if that's perfect English but it's probably a bit better (no
> offense intended, really).

OK I'll commit this change in above (your) form.

kloczek
PS. Seem after fiew experiments I found very easy way for prepare=20
infrasctructure for translate man pages using XML/gettext.
Key command is xml2po (from gnome-doc-utils package). Fragment from=20
"xml2po --help" output shows how to use this:

EXAMPLES:
    To create a POTemplate book.pot from input files chapter1.xml and
    chapter2.xml, run the following:
        /usr/bin/xml2po -o book.pot chapter1.xml chapter2.xml

    After translating book.pot into de.po, merge the translations back,
    using -p option for each XML file:
        /usr/bin/xml2po -p de.po chapter1.xml > chapter1.de.xml
        /usr/bin/xml2po -p de.po chapter2.xml > chapter2.de.xml

So this tool allow in very easy way collect all prases for translate in=20
=2Epot file and generate XML documents with translated XML man pages (using=
=20
XML refentry). Seems it is realy much better solution than using po4a=20
because using XML allow realy keep all ducumentatuon in one/common/good=20
style.
Also if someone will prepare man tool which will allow generate roff=20
output from XML pages (probably will be possible using xmlroff) in future=
=20
it will allow prepare shadow for install man pages not in roff format but=
=20
directly .. as XML files.
For now texinfo tools allow generate XML files from .texi .. after prepare
info viewer which will allo operate on XMLed info pages abowe will allow=20
in future system with documentation in ONE format :)
Imagine .. man pages with embeded multimedia presentation ;o)
--=20
-----------------------------------------------------------
*Ludzie nie maj=B1 problem=F3w, tylko sobie sami je stwarzaj=B1*
-----------------------------------------------------------
Tomasz K=B3oczko, sys adm @zie.pg.gda.pl|*e-mail: kloczek@rudy.mif.pg.gda.p=
l*
--568760595-649903725-1113844898=:4344--