[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: DOCBOOK-APPS: Best Practices
I don't know if we should
continue this offlist?
I have a scenario which
might shed light on what I need in a markup guide.
Example from http://www.dpawson.co.uk/docbook/markup.html
:
You
make a cross reference by identifying where you want to go, and then making a
link to it. To identify where you want to go, you add an id attribute to the element you are targeting. An
id attribute is a simple text string without
spaces that uniquely identifies that element in your document. Each id attribute
has to be unique within your document, or your document won't validate. For
example, if you want to cross reference to a table of sales figures, you add the
id attribute to the table start tag like this:
<table id="MyJulySales"> To form a link to that table, you have two DocBook elements to choose from. In both cases you add a linkend attribute whose value is the id of the element you are pointing to. The two elements are xref and link. Here we have the "id"
attribute. In DocBook there is no simple attribute-tag, but there are the
parameter, option and varname tags. Did I forget any? Which one should I
use to markup the "id" attribute?
What tags to combine and in what order they should be combined is
something I think my users would appreciate.
best
regards,
/Kenneth
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC