--LZvS9be/3tNcYl/X
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Jan Schaumann wrote,

> No, there isn't, and we should try to focus the discussion on how we can
> improve the current build procedure in general, not which particular
> host may eventually end up building the website so we can serve it off
> nbwww.

It was not my attention to focus on special hosts - as I am quite new to
the documentation thing I am just wondering about several things. Sorry,
if it sounded a little bit aggressive.

>=20
> Regardless of which machine that may be (including the individual
> developers, if only for testing), we want to keep requirements at a
> minimum anyway. :-)

I am still thinking about different formats and their advantages. What
comes in mind when thinking about builds and toolchains are technical
things and needs we have for the documentation. When I looked into
htdocs I found alot eps and png images. Are both formats needed? Do we
need image conversion in the toolchain or should we keep them in the
cvs? Without ruining the toolchain discussion I think that issue needs
to be adressed, too. (same like the docbook version, encoding, ...)

I think the toolchain might be one thing to improve, are there any tasks
planned on how to create documentation before it's processed by the
toolchain?

If I am missing the documentation, please give me a hint where to find
it. Is there any specific toolchain documentation so far (except the URL
 http://www.netbsd.org/developers/htdocs.html)?


Uli

--LZvS9be/3tNcYl/X
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFD4VsKKLusNOvI6a4RApaUAKDiuJIBIXrKJcrM+AWNFGyiVidOZwCg8td0
g8YUhPUyx7l5ZY6mLsKhbio=
=ur7v
-----END PGP SIGNATURE-----

--LZvS9be/3tNcYl/X--