Bob Stayton wrote:
FrameMaker's online help index uses this format:
cats [1]
dogs [1] [2]
where the [1] is the hot text that takes you to the point destination.
All entries have [1], and any duplicates get more numbers. It is pretty
obvious that those are not page numbers.
Just another
-I don't understand what you mean by breakup.
With breakup i mean hyphenation. Sorry bout my worse english. :)
- This works when I try it. Does your XML file declare the xl namespace?
It works in PDF and HTML Help but in Java Help they don't work.
- the formatting with CSS doesn't work. Is
Norman Walsh wrote:
I wonder if *both* would be a better compromise.
Using square brackets to indicate hot text, suppose there's one index
term in the section with section title, two in the section with
other section title, three in the section with third section title
and one again in the
Dave Pawson [mailto:[EMAIL PROTECTED] wrote:
My basic point is that the author should identify duplicates
(perhaps from viewing the presented format) and do something about it.
I disagree with this, because it forces the author to presume a specific
output format when creating the source. If
/ Dave Pawson [EMAIL PROTECTED] was heard to say:
| Norman Walsh wrote:
| I wonder if *both* would be a better compromise.
| Using square brackets to indicate hot text, suppose there's one index
| term in the section with section title, two in the section with
| other section title, three in the
/ Dave Pawson [EMAIL PROTECTED] was heard to say:
| Bob Stayton wrote:
| FrameMaker's online help index uses this format:
|
| cats [1]
| dogs [1] [2]
|
| where the [1] is the hot text that takes you to the point
| destination. All entries have [1], and any duplicates get more
| numbers. It is
Including the section titles should be made optional, if they are included
at all. While they provide some context for selecting a reference, we don't
use them in PDF indexes, and they clutter up the index considerably. Once
you accept references to point destinations, the original reason for
Hi
While tinkering with the header.content template I hit upon a problem where
I can't control the style used to render a retrieve-marker. As the example
shows below I can demonstrate the problem by outputting text and the marker
text. But when rendered the header shows the text in a plain
Bob Stayton wrote:
Including the section titles should be made optional, if they are
included at all. While they provide some context for selecting a
reference, we don't use them in PDF indexes, and they clutter up the
index considerably. Once you accept references to point destinations,
Hello Folks,
I am trying to add a parameter list, which will have a list of
parameters.
I added new element parlist by duplicating the existing element
"itemizedlist" and I added, as it's member, an element "paritem" (duplicated
the existing element "listitem"). I have created a customized
Anagha,
The code you included below has a few problems:
- I wouldn't combine the itemizedlist and parlist templates;
Rather, I'd copy the itemizedlist template and turn it into
a separate parlist template.
- Then, you can replace matches for listitem with matches
for paritem and not
Hello Dick,
Thank you for your reply. I will try it out this way.
I am adding customized elements because, besides documentation, these
need to be further processed in our applications.
Regards,
Anagha
Dick Hamilton wrote:
Message
Anagha,
The code you included below has a
12 matches
Mail list logo
