Better still, you can use openjade 1.3.1 and jadetex 3.12 for generally
excellent quality (certainly good enough for real books).
http://sourceforge.net/projects/openjade
http://sourceforge.net/projects/jadetex
You will also need DSSSL stylesheets.
To process an XML file you will need the
Hiroki Sato [EMAIL PROTECTED] writes:
Tim Waugh [EMAIL PROTECTED] wrote
in [EMAIL PROTECTED]:
twaugh On Mon, Jan 28, 2002 at 05:44:51AM -0600, Michael Smith wrote:
twaugh
twaugh * XSLT engine: xsltproc (outputs ISO-8859-1 with character references
twaugh for the Japanese
Ian,
I'm also using openjade, but it depends which stylesheets Massimiliano
wants to use. With openjade he must use dsssl stylesheets...
I thought he was looking for a tool to be used with xsl stylesheets...
Massimiliano, I agree with Ian: if you plan to use dsssl stylesheets,
it would be
Allin Cottrell wrote:
The xsl version stumbles on some material that is OK in the sgml
version. For example:
informalequation
alt
XSL stylesheets needs alt role=tex to take content of alt as TeX
math.
\begin{eqnarray*}
y_t = \alpha + \beta(1/x_t) +
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At 10:43 27-01-2002, Norman Walsh wrote:
For any given bibliography style, it's not too hard. But doing
anything that works for you and me out of the box is essentially
impossible.
Hmm... it should be possible to collect code for standard and house
On Mon, Jan 28, 2002 at 11:33:31PM -0500, Allin Cottrell wrote:
The xsl version stumbles on some material that is OK in the sgml
version. For example:
Of course it stumbles, because what you've presented below is completely
invalid XML. :)
informalequation
alt
sgml2x 0.99.3 is now released. This is the second beta version for
1.0. Probably only bugfixes will be integrated until 1.0 comes out.
This release addresses all bugs reported though Savannah: the problem
with finding a default stylesheet, and the ability to install
somewhere else than in
There are a few requests locally for multilingual community based sites - to
support small groups. I am researching into using a Unicode based front end,
with DocBook related tools on the server - perhaps generating PDF's to be
stored on the site?
Could anyone advise on the issues: an example of
Hello...
Rather than launch into the latest of a seemingly
endless list of issues that I seem to be having with dynamically transforming
docbook xmlusing the XSL stylesheets and IIS (msxml4), I figured it was
better and less painful for everyone else to ask... is anyone doing this?
If so,
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
/ Bang, Steinar [EMAIL PROTECTED] was heard to say:
| David Cramer [mailto:[EMAIL PROTECTED]] wrote:
|
| I'd suggested of using a background image, but was told
| that's cheating.
|
| http://lists.oasis-open.org/archives/docbook-apps/200107/msg00034.html
Seems reasonable to me. I've just
From: Bruce Morrison
Basically loading the xml into DOM 1
Loading docbook.xsl into DOM 2
and then (attempting) to spit out the transform using
DOM1.transformNode(DOM2)
If you're using the HTML stylesheets, the output is not XML so you can't
transform to a DOM.
Use
-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
I never saw a recommendation for using article, so I don't know of the
advantages. Would like to know if there are any.
First file is the first section as you thought.
I use sect1, sect2, etc.. for section tags and nesting. As for
suppressing chunking of subsections, I have no need to do
On Tue, 29 Jan 2002, Jirka Kosek wrote:
Replace with amp; or put whole TeX stuff in CDATA section:
![CDATA[...]]
Thanks, that works fine. One other observation. Your math.xsl
automatically inserts math delimiters ($ for inline and $$ for
display) in the PI for xmltex, when it encounters an
My apologies- I didn't read the question properly! ;(
(although you should really use transformNodeToObject(Response) anyway)
RobSmith
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At 13:03 8-01-2002, Togan Muftuoglu wrote:
I am interested currently I am trying to do with Docbook also but as
separate files which makes life difficult. You can send me directly or
point a location to be downloaded. If sending directly
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
-Original Message-
On Mon, Jan 28, 2002 at 11:33:31PM -0500, Allin Cottrell wrote:
The xsl version stumbles on some material that is OK in the sgml
version. For example:
Of course it stumbles, because what you've presented below is
completely
invalid XML. :)
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
RefDB stores far more information for a bibliographic reference than
just the bibliographic data. As RefDB was designed from the ground up
as a collaborative tool, it is necessary to store a part of this
information, like personal notes or availability information (i.e. a
URL to an electronic
22 matches
Mail list logo
