Re: DOCBOOK: argh ... how do i define page breaks using CSS?

2002-07-27 Thread Bob Stayton

On Fri, Jul 26, 2002 at 04:21:59PM -0400, Robert P. J. Day wrote:
 On Fri, 26 Jul 2002, Stefan Seefeld wrote:
 
  Robert P. J. Day wrote:
 probably off topic for this list, but the only outstanding
   issue i have is how to force page breaks before each section.
   and by that, i mean each section, regardless of its level.
   
 what i want is a CSS definition that lets me say i want a
   page break before every chapter element and every section
   element.  as it stands, i get a page break before every
   first-level section in a chapter, and that's it.  i've checked
   on google, added what looks like the right directive to the
   css file -- no luck.
  
  uhm, what is a page in html ? Are you talking about getting
  separate html files for sections ? That's done with the chunker,
  and there are parameters in the xsl stylesheets to control the
  granularity of the chunks.
  
  I can't see how css relates to pages, but may be you are talking
  about something entirely different.
 
 no, i'm just explaining this badly.  yes, i'm referring to chunking.
 as a basis for my first docbook manual, i used tim waugh's
 selfdocbookx example.  one of the .xsl files refers to a .css
 file, so i figured i'd add a page-break-before directive in
 that file to break before every section.  didn't work.
 as it stands, each first-level section is generated as a chunk,
 when i'd really like *every* section directive to define a new
 chunk.
 
 i've read everything i can find, and haven't figured out how to
 fix this.

You might want to check out the DocBook XSL doc
that I'm writing.  It's currently unfinished, but
does have a section on chunking.

http://www.sagehill.net/xml/docbookxsl/index.html

My intended audience is folks like you that are just
getting started.  I'd appreciate any feedback
you might have.
-- 

Bob Stayton 400 Encinal Street
Publications Architect  Santa Cruz, CA  95060
Technical Publications  voice: (831) 427-7796
Caldera International, Inc. fax:   (831) 429-1887
email: [EMAIL PROTECTED]



DOCBOOK: hierarchical element reference list for docbook?

2002-07-27 Thread Robert P. J. Day


  is there a hierarchical reference list for the current
docbook elements somewhere?  you know, grouped by association
or category or something like that. 

  at the moment, google isn't turning up anything like that.
thanks.

rday




Re: DOCBOOK: hierarchical element reference list for docbook?

2002-07-27 Thread Dave Pawson

At 07:11 27/07/2002, Robert P. J. Day wrote:

  is there a hierarchical reference list for the current
docbook elements somewhere?  you know, grouped by association
or category or something like that. 


I'd suggest the index in docbook, the definitive guide,
though perhaps a seperate index into the book might be
a good addition,

I use the table of contents in docbook which is complete,
when I want to hunt out a particular element.

HTH DaveP





Re: DOCBOOK: hierarchical element reference list for docbook?

2002-07-27 Thread Robert P. J. Day

On Sat, 27 Jul 2002, Dave Pawson wrote:

 At 07:11 27/07/2002, Robert P. J. Day wrote:
 
   is there a hierarchical reference list for the current
 docbook elements somewhere?  you know, grouped by association
 or category or something like that. 
 
 
 I'd suggest the index in docbook, the definitive guide,
 though perhaps a seperate index into the book might be
 a good addition,
 
 I use the table of contents in docbook which is complete,
 when I want to hunt out a particular element.

actually, i'm in the process of creating a hierarchical list
(in emacs outline mode) of all of the elements listed in TDG
(updated when i get the chance).

when i'm done, i can post it if anyone's interested.  the 
point is to list elements in categories, such as

* lists
* function display
* code/screen display
* Q/A

and so on, so i can just jump to the appropriate section to
see all of the related elements.

rday




Re: DOCBOOK: hierarchical element reference list for docbook?

2002-07-27 Thread Dave Pawson

At 08:58 27/07/2002, Robert P. J. Day wrote:

actually, i'm in the process of creating a hierarchical list
(in emacs outline mode) of all of the elements listed in TDG
(updated when i get the chance).

when i'm done, i can post it if anyone's interested.  the 
point is to list elements in categories, such as

* lists
* function display
* code/screen display
* Q/A

and so on, so i can just jump to the appropriate section to
see all of the related elements.

I'd appreciate a copy (xml markup please) for the docbook faq.

TIA DaveP





Re: DOCBOOK: hierarchical element reference list for docbook?

2002-07-27 Thread Robert P. J. Day

On Sat, 27 Jul 2002, Dave Pawson wrote:

 At 08:58 27/07/2002, Robert P. J. Day wrote:
 
 actually, i'm in the process of creating a hierarchical list
 (in emacs outline mode) of all of the elements listed in TDG
 (updated when i get the chance).
 
 when i'm done, i can post it if anyone's interested.  the 
 point is to list elements in categories, such as
 
 * lists
 * function display
 * code/screen display
 * Q/A
 
 and so on, so i can just jump to the appropriate section to
 see all of the related elements.
 
 I'd appreciate a copy (xml markup please) for the docbook faq.

just fyi, here's the first part of it so you can see what i'm 
trying to do.  it's in emacs outline mode at the moment:

* Types of documents
set,setindex,setinfo
book,bookinfo
article
* Document meta-information
** General stuff
abstracttitleblah/title
appendix
dedication
edition
preface
** Author
author
authorblurb
authorgroup
authorinitials
** Copyright
copyright
holder
year
** Subject stuff
subject
subjectset
subjectterm
** Bibliography
bibliography
bibliodiv
biblioentry
bibliomset
bibliomisc
bibliomixed
biblioset
bookbiblio
** Glossary
glossary
glossentry
glosslist
glosssee,glossseealso
glossterm
glossdef
glossdiv
** Index
index
indexterm
indexentry
indexdiv
** Publisher info
publisher
publishername
pubdate
pubsnumber
* Document major parts
chapter
section,sectioninfo
sect1..sect5,sect1info..sect5info
simplesect
part,partintro
para,simpara
* References
reference
refname
refsect1..refsect3, refsect1info..refsect3info
refclass
refdescriptor
refentry,refentrytitle
refmeta
refmiscinfo
refnamediv
refpurpose
refsynopsis,refsynopsisinfo
* Lists
orderedlist
itemizedlist
listitem
simplelist,member
segmentedlist,seglistitem,segtitle,seg
variablelist,varlistentry
* Tips to readers
caution
imporant
note
tip
warning



... and so on.  just a really quick reference to related
elements.  so nothing like this is available on the net
somewhere already?  bummer.

rday




Re: DOCBOOK: Re: hierarchical element reference list for docbook?

2002-07-27 Thread Robert P. J. Day

On Sun, 28 Jul 2002, Tsuguya Sasaki wrote:

 Robert P. J. Day wrote:
 
  is there a hierarchical reference list for the current
  docbook elements somewhere?  you know, grouped
  by association or category or something like that.
 
 Check the section Logical Divisions: The Categories of
 Elements in DocBook in Chapter 2 Creating DocBook
 Documents in DocBook TDG, though the list is not
 exhaustive:
 http://www.docbook.org/tdg/en/html/ch02.html#ch02-logdiv
 
 I also made something humble based on the above, but the
 list is rather simplified, and has only major elements:
 http://www.ts-cyberia.net/docbook.html

hmmm ... not sure how i missed that section in the book.  duh.
what would be really useful is a foldout reference card.  but
now i'm dreaming.

rday




Re: DOCBOOK: hierarchical element reference list for docbook?

2002-07-27 Thread Dave Pawson

At 09:12 27/07/2002, Robert P. J. Day wrote:

just fyi, here's the first part of it so you can see what i'm 
trying to do.  it's in emacs outline mode at the moment:

snip/

... and so on.  just a really quick reference to related
elements.  so nothing like this is available on the net
somewhere already?  bummer.


Not grouped like that AFAIK, Norm? Bob?

If Norm has tdg id values marking the sections/pages it could easily
be linked via olink to tdg? 

I think that would make a very useful addition to the documentation.

Regards DaveP