I wrote:
|So it looks like if we use a Section-like (instead of Chapter-like)
|content model for Topic, it'll mean that Topics can contain only
|recursive Sections, not numbered ones (Sect1-Sect5), and that
|Topics can't contain Refentrys at all (or Simplesect).
Norm wrote:
On Tue, Oct 16, 2001 at 01:57:17PM -0400, Norman Walsh wrote:
/ Phillip Shelton [EMAIL PROTECTED] was heard to say:
| I want to put The company name in the header and the filename and author in
| the footer.
The filename isn't available to Jade, so I don't think you can easily do
that. But
Norman Walsh [EMAIL PROTECTED] writes:
/ Phillip Shelton [EMAIL PROTECTED] was heard to say:
| I want to put The company name in the header and the filename and author in
| the footer.
The filename isn't available to Jade, so I don't think you can easily do
that.
Yes.
In the beginning of
1. Online-help peer to Set. Do we actually need one?
It would be useful for us. We currently package our book set containing
documentation on all of our products, with one version installable into an
online helpviewer in the QNX operating system. Most of our products can work
together,
/ Michael Smith [EMAIL PROTECTED] was heard to say:
| 1. Online-help peer to Set. Do we actually need one? What will the
|processing expectations be for it? Do any of the existing help
|systems -- HTML Help, Javahelp, or whatever -- provide any way for
|packaging up sets of HTML Help
At 13:56 16/10/2001 -0400, Norman Walsh wrote:
What's the plan:
The overall plan is to allow people to author Help Sets using all of
the rich technical structure of DocBook without shoe-horning it into
the classical print book model.
Guessing that 'topics' could be viewed in a similar way to
| 3. Content model for the set-of-topics element (Helpproject). Does
it
| need to include the navigational components (ToC,
LoT, Index)?
| These seem useful only if authors want to
manually author ToCs,
| LoTs, and Indexes, instead of leaving it up to
the
| stylesheets/helpcompiler to generate
/ Nancy (Paisner) Harrison [EMAIL PROTECTED] was heard to say:
| I, on the other hand, am concerned with not allowing sections in the
| mix, since that removes a transparent way to reuse data between
| print and online delivery.
If you need sections in a topic, use nested topics. Allowing
Found it. The link is [EMAIL PROTECTED] though.
Phill
-Original Message-
From: Karl Eichwalder [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 17 October 2001 5:24
To: [EMAIL PROTECTED]
Subject: DOCBOOK: Re: Page footers and Headers.
Norman Walsh [EMAIL PROTECTED] writes:
/
|So it looks like if we use a Section-like (instead of Chapter-like)
|content model for Topic, it'll mean that Topics can contain only
|recursive Sections, not numbered ones (Sect1-Sect5), and that
|Topics can't contain Refentrys at all (or Simplesect).
I am strongly opposed to
On Wed, Oct 17, 2001 at 10:09:29AM +0900, Michael Smith wrote:
Dislikes:
* non-Free software
For those who want a free-software gui, we're looking for help on the
ThotBook project (https://savannah.gnu.org/projects/thotbook/) -
nothing to test right now, though.
Likes:
*
When building my
docset for use in JavaHelp, the full text of some of the pages got built into
the map file, as follows:
mapID target="ansys.wid.dict"
url="Hlp_UI_WidFront.html"/ mapID target="d46e5"
url="Hlp_UI_UITOC.html"/Welcome to ANSYS 6.0 Documentation HTML Online
Bob,
Thank you very much for your response. This information is exactly what
I needed.
If anyone else in the list would like a copy of the template I am
creating please email me and I will forward it on to you.
Thanks again.
Brendan
I'm having problems
getting Saxon to generate table of contents. I've tried passing parameters
to DocBook via the command-line and in a stylesheet. I've tried having
every 'generate.xxx.toc' set to 1, and tried setting some of them to zero.
I haven't yet hit on the right combination to
14 matches
Mail list logo
