From kde-i18n-doc  Mon Jan 26 23:44:22 2004
From: Lauri Watts <lauri () kde ! org>
Date: Mon, 26 Jan 2004 23:44:22 +0000
To: kde-i18n-doc
Subject: Re: obsolete docs
Message-Id: <200401270044.26451.lauri () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-i18n-doc&m=107516083905127
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--Boundary-02=_aZaFAIam4ihg00q"


--Boundary-02=_aZaFAIam4ihg00q
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Tuesday 27 January 2004 00.04, G=E9rard Delafond wrote:
> Hi
>
> I am working on the translation of some documentation.
>
> It appears that many of them are out of date.
>
> The described functions or the screenshots do not match to the GUIs in ma=
ny
> cases.
>
> The question is What is the best way to get some "clean" documentations ?

Recruit more people.  There's only so much documentation Phil and I can man=
age=20
on our own, and you're seeing the result.  =20

Report them as bugs, we *are* going through the bugs and fixing things, and=
=20
yes, translators make great bug reporters.  An actual list of 'things that=
=20
need fixing' saves a lot of time.

There's a pre KDE 3.2 list at http://people.fruitsalad.org/lauri/docs/ - mu=
ch=20
of what's on there, Phil has now filed as bugs, and we intend to use Bugzil=
la=20
in future to help with tracking what needs doing.

> I think the best should be developers send an information to the docs
> writers when new functions appear.

Best of luck making that happen.  All they have to do is put a GUI: in thei=
r=20
cvs commit logs, and I will get a separate copy of the mail to forward to t=
he=20
(largely nonexistent) document maintainers.=20

> Is there somebody or a team to check the consistency of all the
> documentations ?

What there is of a team, is on the kde-doc-english@ mailing list, not this=
=20
one.  Bug reports also show up there.    Phil and I went through literally =
a=20
couple of hundred documents each pre KDE 3.2, and cleaned up a whole lot of=
=20
things, and this is an ongoing process.

Right now, bugzilla reports are the best thing you can do currently.  It's=
=20
helpful if you file bugs on a per doc basis (makes it easier to keep track =
of=20
as we work on fixing them.)

Regards,
=2D-=20
Lauri Watts
KDE Documentation: http://i18n.kde.org/doc/
KDE on FreeBSD: http://freebsd.kde.org/

--Boundary-02=_aZaFAIam4ihg00q
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQBAFaZa/gUyA7PWnacRApA5AJ9IxlCzHsBVKN0+vPck+U3IcMYSqACfZVPT
9lwtYQEdjaokhL9UPL6h5yo=
=AaNs
-----END PGP SIGNATURE-----

--Boundary-02=_aZaFAIam4ihg00q--