[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] <part> "label" attribute handling
On 7/7/05 11:56, "Bob Stayton" <bobs@sagehill.net> wrote: > Hi Paul, > The stylesheets consider "label" to be just the number part. So "III" is > the label, and that is what should go into the label attribute. The word > "Part" is added to the label to form something that doesn't have a name. > Perhaps "Part III" should be called a named-label or something. If you > translate your documents, having the word "Part" in the label attribute > would require that the translator translate it. As it is, the generated > word "Part" is automatically translated. > > In your case, the TOC by default does not add the word "Part" or "Chapter" > in front of the label number. That is just the intended style, not an > inconsistency. Bob, thanks. I understood about the automatically generated "Part." What I found confusing was it being generated in some contexts and not others. I'll simply remove "Part" from the label attribute values. > > Bob Stayton > Sagehill Enterprises > DocBook Consulting > bobs@sagehill.net > > > ----- Original Message ----- > From: "Paul DuBois" <paul@kitebird.com> > To: <docbook-apps@lists.oasis-open.org> > Sent: Thursday, July 07, 2005 9:27 AM > Subject: [docbook-apps] <part> "label" attribute handling > > >> I have a question about how the DocBook XSL stylesheets handle the "label" >> attribute for <part> elements. >> >> The O'Reilly DocBook book says this about the label attribute: >> >> Label specifies an identifying string for presentation purposes. The > first >> Part in a Book might be labeled "Part I", for example. >> >> Generally, an explicit Label attribute is used only if the processing >> system >> is incapable of generating the label automatically. If present, the Label >> is >> normative; it will used even if the processing system is capable of >> automatic >> labelling. >> >> >> Okay, suppose I write a document with these <part> elements: >> >> <part label="Part I"> >> ... >> </part> >> <part label="Part II"> >> ... >> </part> >> <part label="Part III"> >> ... >> </part> >> <part label="Part IV"> >> ... >> </part> >> >> >> If I generate HTML, the TOC lines for the parts in the HTML document say >> "Part I", "Part II", "Part III", and "Part IV". >> >> Similarly, if I generate PDF (using FOP), the TOC lines say >> "Part I", "Part II", "Part III", and "Part IV". However, the PDF >> document also has a bookmarks list, and the bookmark lines for the parts > say >> "Part Part I", "Part Part II", "Part Part III", and "Part Part IV". Also, >> the pages generated within the document that begin each part say >> "Part Part I", "Part Part II", "Part Part III", and "Part Part IV". >> >> It appears to me that the PDF stylesheets are adding text inconsistently. >> (Adding "Part" in the bookmarks and in the part pages within the document, >> but not in the TOC.) I believe this is a stylesheet issue and not a FOP >> issue, because in the .fo file I can find elements like this: >> >> <fox:label>Part Part I. title of part</fox:label> >> <fox:label>Part Part II. title of part</fox:label> >> <fox:label>Part Part III. title of part</fox:label> >> <fox:label>Part Part IV. title of part</fox:label> >> >> And like this:: >> >> <fo:block xmlns:axf="http://www.antennahouse.com/names/XSL/Extensions"; >> keep-with-next.within-column="always" hyphenate="false">Part Part >> I. title of part</fo:block> >> >> >> So my question is whether I should consider this a bug and file a bug >> report, or whether it's intentional behavior that I'm misunderstanding? >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org >> For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org >> >> >> > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]