Date: Thu, 11 Jan 2001 09:45:24 +0000 From: Nik Clayton <nik@freebsd.org> To: "Bruce A. Mah" <bmah@freebsd.org> Cc: Nik Clayton <nik@freebsd.org>, doc@freebsd.org Subject: Re: Version specific documentation Message-ID: <20010111094523.A97901@canyon.nothing-going-on.org> In-Reply-To: <200101102139.f0ALdsh06635@bmah-freebsd-0.cisco.com>; from bmah@freebsd.org on Wed, Jan 10, 2001 at 01:39:53PM -0800 References: <20001221135340.B61525@canyon.nothing-going-on.org> <200012281823.eBSINeV06392@bmah-freebsd-0.cisco.com> <20010110161524.G93855@canyon.nothing-going-on.org> <200101102139.f0ALdsh06635@bmah-freebsd-0.cisco.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 10, 2001 at 01:39:53PM -0800, Bruce A. Mah wrote:
> > How much overlap is there likely to be between different architectural
> > versions of the release notes? It's certainly possible. DocBook
> > already has an 'arch' attribute on most elements, so you could write
> > something like
> >
> > <para arch="i386 alpha">...</para>
> >
> > and the stylesheets could do something with it. Essentially, this would
> > be identical to the code I still have to write to support an osversionin
> > attribute.
>
> Errr. Does this mean that an arch= attribute is now supported but it
> doesn't handle multiple architectures?
The "arch" attribute is a standard part of DocBook. It's not a FreeBSD
extension. You can see all the elements that have an 'arch' attribute
at
http://www.docbook.org/tdg/html/pe-common-attrib.html
<aside>I can't recommend http://www.docbook.org/tdg/html/docbook.html
highly enough.</aside>
The content of the attribute is entirely at our discretion. The DTD and
stylesheets do not mandate any particular values for it. What you can't
have is multiple copies of the same attribute on one element. You can't
write something like
<para arch="i386" arch="alpha">
you have to do something like
<para arch="i386 alpha">
or
<para arch="i386,alpha">
Spaces, commas, it's all the same to me, I don't care which we use, but
the code we right in the stylesheets will.
Remember, the DTD and processing tools have no knowledge of any special
semantic meaning we might have for the tokens "i386" or "alpha" (or
"ppc", or whatever). It's up to the stylesheet to do something with
them.
A quick
# cd /usr/local/share/sgml/docbook/dsssl/modular
# grep ' arch' * */*
shows that the stylesheets only care about it in relation to <olink>,
which we never use. If we were to start assigning meanings to 'arch'
then the stylesheets would have to do something with that before we got
any different output.
> To answer your question I'd say that overlap is much more likely once we
> support more than 2 architectures.
OK.
> > Depends on the processor you're using. Jade doesn't support it, all it
> > lets you do is set previously unset values. However, OpenJade lets you
> > assign values on the command line.
>
> I just discovered OpenJade, thanks to your doc/ commit to make OpenJade
> generate the navigation menu for Acrobat. Do we have a preference for
> using jade vs. openjade?
The project as a whole uses Jade. Personally, I use Jade (too lazy to
switch to OpenJade). It's my understanding that OpenJade has issues
with wide character support that make it impossible for us to migrate to
OpenJade without breaking the Japanese (and possibly other) translation
builds.
N
--
Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95.
Telephone line, $24.95 a month. Software, free. USENET transmission,
hundreds if not thousands of dollars. Thinking before posting, priceless.
Somethings in life you can't buy. For everything else, there's MasterCard.
-- Graham Reed, in the Scary Devil Monastery
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?20010111094523.A97901>