Date: Tue, 10 Jul 2001 14:57:57 +0100 From: Nik Clayton <nik@freebsd.org> To: Nik Clayton <nik@freebsd.org> Cc: Dima Dorfman <dima@unixfreak.org>, doc@freebsd.org Subject: Re: State of the Handbook Message-ID: <20010710145757.J16152@clan.nothing-going-on.org> In-Reply-To: <20010710135753.G16152@clan.nothing-going-on.org>; from nik@freebsd.org on Tue, Jul 10, 2001 at 01:57:53PM %2B0100 References: <20010710114034.E16152@clan.nothing-going-on.org> <20010710113247.A2B863E28@bazooka.unixfreak.org> <20010710135753.G16152@clan.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--SLfjTIIQuAzj8yil
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Jul 10, 2001 at 01:57:53PM +0100, Nik Clayton wrote:
> On Tue, Jul 10, 2001 at 04:32:47AM -0700, Dima Dorfman wrote:
> > Nik Clayton <nik@freebsd.org> writes:
> > > 2. Supplement the ASCII art with images.
> > >=20
> > > Something else on WRS' todo list, although it doesn't prevent an=
yone
> > > else with an artistic bent from picking some of the existing ASC=
II art
> > > and producing images for it as well. WRS expect to have this do=
ne by
> > > the end of August.
> >=20
> > Do we have a mechanism so that we can keep the ASCII art and display
> > it where necessary? I.e., I'd rather not see the ASCII art thrown
> > away; not everybody wants to start a graphics-capable browser to read
> > the docs (I know I don't).
>=20
> Yes we do. See section 4.2.6 of the primer.
>=20
> We've previously talked about adding another format to the set that's
> generated; html-no-images (or similar). That's trivial to generate
> (since we already generate it in order to produce the plain text version
> of the docs).
>=20
> However, it brings up an additional issue -- currently, the output formats
> are all produced in the 'current' directory. This works OK for the
> formats that we have, since none of them have filenames that 'collide'
> with one another.
>=20
> It won't work with a hypothetical 'html-no-images' format. The likes of
> 'book.html' is perfectly legitimate in this format, which would collide
> with the files generated by the 'html' format. It's also feasible that
> people would want an 'html-split-no-images' format as well, the output
> files for which would collide with the output from the 'html-split'
> format.
Looks like I forgot to finish this before sending :-) =20
I'm thinking that perhaps we should have an output directory (that defaults=
=20
to ${.curdir}) and that the output is placed in subdirectories of this,=20
according to the format, ${.curdir}/html/book.html, ${.curdir}/ps/book.ps,
${.curdir}/html-split-no-images/index.html, and so on.
Maybe make the directory names all caps, or have a leading '_', or
something, so that they cluster at the beginning of ls(1) output. . .
N
--=20
FreeBSD: The Power to Serve http://www.freebsd.org/
FreeBSD Documentation Project http://www.freebsd.org/docproj/
--- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 ---
--SLfjTIIQuAzj8yil
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjtLCeQACgkQk6gHZCw343XK6QCfSCbX4y0Pfa6YuDGz2XOBQhAf
gF0AoIYCB3vOvCkNjwy2bbALjMdOOauf
=Jsch
-----END PGP SIGNATURE-----
--SLfjTIIQuAzj8yil--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010710145757.J16152>