From kde-core-devel  Thu Feb 16 13:06:48 2006
From: Lauri Watts <lauri () kde ! org>
Date: Thu, 16 Feb 2006 13:06:48 +0000
To: kde-core-devel
Subject: Re: docbook writers: please no empty para's
Message-Id: <200602161406.52118.lauri () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=114009550321590
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart3217874.0ivgVBb3s8"

--nextPart3217874.0ivgVBb3s8
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Thursday 16 February 2006 11:33, Erik K. Pedersen wrote:
> Torsdag den 16. februar 2006 07:28 skrev Lauri Watts:
> > On Wednesday 15 February 2006 22:24, Erik K. Pedersen wrote:
> > > With "to be written" it is ok
> >
> > It's ok from a "makes the docbook compile" point of view.  From a useful
> > documentation for users to read, it's _horrible_
>
> I guess I would agree with that, would it not be a solution not to write
> <para></para> ?

That's not valid either, in fact, that's the reason for most of the empty=20
para's showing up: people put placeholder chapters/sections/listitems there=
,=20
and never write the docs to go in them, and these elements require content =
to=20
be valid.

=46or the example given, you'd have to comment out the entire <listitem> (o=
r if=20
it's in a varlistentry, comment that out)

The really best solution is to fill in the para with some actual content, o=
r=20
not put empty sections in the doc in the first place.

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

--nextPart3217874.0ivgVBb3s8
Content-Type: application/pgp-signature

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

iD8DBQBD9Hjs/gUyA7PWnacRAvOrAJ9sClQnANlEM66UWO3rvYzT91PFKwCcDH2y
WM6LXzEyqdmZBnHXDPfGiL0=
=vvIP
-----END PGP SIGNATURE-----

--nextPart3217874.0ivgVBb3s8--