Dave Pawson:
Hence the question. Is it truly a topic (DITA wise) if its not standalone?
Punting to the DITA FAQ:
A topic is a chunk of information organized around a single subject.
Structurally, it is a title
At 13:30 19/03/2002 -0500, [EMAIL PROTECTED] wrote:
Dave Pawson:
Which would be easier?
a)To provide a mini DTD for 'glue' which then becomes a topic,
b)Process glue content as a special?
Most glue really isn't appropriate for treatment as a topic.
I was moving to ease of processing over
Dave Pawson:
Which would be easier?
a)To provide a mini DTD for 'glue' which then becomes a topic,
b)Process glue content as a special?
Most glue really isn't appropriate for treatment as a topic. Topics are
supposed to be independently readable, reusable units of titled information
organized
At 14:54 19/03/2002 -0500, Nancy (Paisner) Harrison wrote:
Toolsmiths, including authors who are toolsmiths, tend to prefer 'ease of
processing;' authors who aren't toolsmiths generally prefer 'rules that
make sense.'
chuckles/
In which case is it another rule that topics should be
Michael,
The last time I asked (Don Day, I think it was) for a pointer to someone at
IBM who was using DITA as a model for print books, I was told that no one
there was doing it yet. That was a while ago, and DITA was fairly new then.
Now that it's been around a bit, could you point me to
Information Development
Nancy (Paisner) Harrison [EMAIL PROTECTED] on 03/18/2002 02:55:30 PM
Please respond to Nancy (Paisner) Harrison [EMAIL PROTECTED]
To: Bradford, Denis [EMAIL PROTECTED], Michael
Priestley/Toronto/IBM@IBMCA, [EMAIL PROTECTED]
cc:
Subject: RE: DOCBOOK-APPS: Help project
At 15:16 18/03/2002 -0500, [EMAIL PROTECTED] wrote:
1. accomodate the 'glue text' that books need to connect physically
sequential topics
You can factor this out into a map document,
Isn't glue text simply a tiny, short lived chunk Michael?
Regards DaveP
RE: using recursive sections for topics instead of chapters in HTML Help
I've been testing docbook 1.48 (and the latest htmlhelp.xsl from CVS) on the
following help project structure:
book
chapter
titleHelp for My App/title
topic1;
topic2;
/chapter
/book
, January 31, 2002 11:47 AM
To: [EMAIL PROTECTED]
Subject: RE: DOCBOOK-APPS: Help project structure
RE: using recursive sections for topics instead of chapters in HTML Help
I've been testing docbook 1.48 (and the latest htmlhelp.xsl from CVS) on the
following help project structure:
book
I would love to see a parameter that allows you to exclude
the generation of
book and chapter files.
What you (and I) really want is for the xsl to check to see if there's
content in the chapter or section before the next section begins. So the
following two cases would be handled
about foo/title
David
-Original Message-
From: David Cramer
Sent: Thursday, January 31, 2002 1:59 PM
To: Maggie Strevell; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: RE: DOCBOOK-APPS: Help project structure
I would love to see a parameter that allows you to exclude
-Original Message-
From: Maggie Strevell
I don't need the depth you mention so I haven't taken it that far.
I also have files for which I want in the help file, but I
don't want in my table of contents.
-Original Message-
From: David Cramer
The xsl for chunking is
[EMAIL PROTECTED] wrote:
1. htmlhelp.xsl generates chunks for book and chapter, and also lists them
in FILES section of .hhp project file. What's the best way to NOT generate
these elements and to exclude them from the .hhp project file? I couldn't
get any parameters to do it.
This
At 16:47 29/01/2002 -0500, [EMAIL PROTECTED] wrote:
I followed Norm's straw proposal too. As I recall there was some argument
that a recursive section is just the ticket for doing online docs, and maybe
we don't need a special dtd. Maybe trying this will convince me one way or
the other.
Are
-Original Message-
From: Jirka Kosek
chunk.first.sections=1
chunk.sections=1
chunk.section.depth=5
You can partially control this by parameter
chunk.section.depth. But if
you need different depth of chunking in different places of your
document this won't help you.
Aha,
I'm
new to all this and recently madea guess at this myself. I am using
a section to represent each help topic. The type of driver file
(book|chapter|section).
I am
using the latest htmlhelp.xsl with Instant Saxon to generate the htm
files. Maybe those more experienced than I can point me
-Original Message-
From: Maggie Strevell [mailto:[EMAIL PROTECTED]]
I am using a section to represent each help topic. The type
of driver file (book|chapter|section).
This looks sensible to me. How come some people recommend article instead of
chapter? Is there some advantage I'm
for it. Haven't thought enough about that. I'm pretty new to all of this
myself, so this is like the blind leading the blind.
Maggie
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 29, 2002 12:59 PM
To: [EMAIL PROTECTED]
Subject: RE: DOCBOOK-APPS
Thank you both, I think I've got what I need.
I use sect1, sect2, etc.
I'm interested in using only sections, for the reason that Dave mentions:
to avoid a rigid book structure.
Norm added a chunk.section.depth parameter to let you control that
between 1.47 and 1.48.
Great - I missed
[EMAIL PROTECTED] wrote:
Does 'first file' mean the first section? With recursive sections, you could
have a topic with subsections like this, right?
section
content...
sectionSubsection 1.../section
sectionSubsection 2.../section
sectionSee also.../section
Steffen Maier [EMAIL PROTECTED] writes:
Hello Maggie,
[...]
Prevent the titles for each section from repeating at the top of each
section (I only need one)
http://www.dpawson.co.uk/docbook/styling/custom.html#d61e810, the section
called 14. Table of content, or toc's. It's about xsl
21 matches
Mail list logo
