Re: written spec - adding to the TOC

--===============1266608924==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-Ive8QONNDpKQ20x0iBFt"


--=-Ive8QONNDpKQ20x0iBFt
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Thu, 2005-12-01 at 11:34 -0800, Nick Stoughton wrote:
> On Thu, 2005-12-01 at 05:07, Pradosh Adoni wrote:
> > what do I need to do to add my written spec so that it shows up in the
> > TOC of the parent module spec  .. ?=20
> >=20
> > -- pradosh=20
> I'm not sure I fully understand this question.
>=20
> A number of SGML tags make it to the TOC pages (and others also make it
> to the pdf bookmarks if this is to be published in pdf).
>=20
> Currently, the stylesheet (lsbspec/docbook-utils.dsl) adds things up to
> heading-level 3 (except appendices, which only get their top level) to
> the TOC, for both HTML and RTF.
>=20
> This means that tags such as <PART> (level 0), <CHAPTER> (level 1),
> <SECT1> and <SECT2> all go into the TOC.
>=20
> A <REFENTRY> does not go into the TOC (but does go into the pdf
> bookmarks).
>=20
> The stylesheet is just another program ... and there is no technical
> reason why Desktop couldn't use a different stylesheet to Core (though
> I'd question the appropriateness of this at a different level). If you
> wanted to have level 5 things in the TOC, its a simple change. Of
> course, you have to learn DSSSL, a variant of Scheme, in tuen a variant
> of Lisp, to figure out how to do this! The function is question is
> called "toc-depth", and currently has the following definition for RTF:
>=20
> ;;What depth should the TOC generate?
> ;;not for appendices
> ;;And sets have a toc for everything up front
> (define (toc-depth nd)
>   (if (string=3D? (gi nd) (normalize "book"))
>       (if (gi (parent nd))=20
>       0
>       3)
>       (if (string=3D? (gi nd) (normalize "appendix"))
>         0
>         (if (string=3D? (gi nd) (normalize "set"))
>           5
>           1))))
>=20
> [[Hint ... change the '3' to some other value!! But please do not change
> this in docbook-utils.dsl ... copy that and use a different stylesheet,
> otherwise you'll wreck the ISO publication work I'm handling right
> now.]]
>=20
> On the other hand .... maybe you are asking quite a different question!!
> If so, apologies, and please rephrase!

Ummm ... I was looking at which file I need to edit so that the spec
generation scripts pick up that a new section was added , and add that
section to the parent spec. for eg.
I'm adding fontconfig to the desktop spec and I need that to show up in
the TOC of the Desktop book (or spec.)

I'm trying to put a howto  together on adding to the spec here -=20
http://www.linuxbase.org/LSBWiki/WrittenSpecificationHowTo
Currently I've just ripped Nilesh's excellent notes on this topic from
the LibtoDB page=20
(sorry Nilesh :) ) and put them there to start off ..
I'm hoping to get a full-fledged howto documented there, so you guys can
add to that=20

thanks
-- pradosh=20
PS. Nick, the information you sent is still pretty useful though :)



--=-Ive8QONNDpKQ20x0iBFt
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iQEVAwUAQ5Pw93/NtiPREx7AAQIiLAgA0gaUNyRDsGqcr3rMipvHarZ7OB5MBv/K
WPkczf4vSHs8dml4CL0cWoD3bN7XUxnC0/s9Luz3bwqtAATu6sIIEX4F5DVs7b6F
DhZSjlMXBaj1pfXCejOXKjRfdqcgZ1ICxs6Q2TJO0RUqorHQnOc8mjK+Yd4UOtdx
68svtG0uXF6iV3y5xp53Y40mhtCu+PEcWORo8F9Et9BBzupgDCzK4BgQCd3s6J1m
kEs07NUQ8LDYqMArjhvRZlSz5bHlC68B6NSq/e2tRI33vpOsp0q7tCneMo6WTF4j
TIEDAc727fmwQQfHfX59Rpua3MCKy2iFe7tmoUiuRuWG6Mp7KXTaQA==
=66QD
-----END PGP SIGNATURE-----

--=-Ive8QONNDpKQ20x0iBFt--


--===============1266608924==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
lsb-spec mailing list
[email protected]
http://mail.freestandards.org/mailman/listinfo/lsb-spec

--===============1266608924==--