From: Rahul Dave <rahul@reno.cis.upenn.edu>
To: rosalia@lanl.gov (Mark Galassi)
Cc: sylvan@ravinet.com (Sylvan Ravinet),
docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: DocBook to LaTex?
Date: Wed, 27 Dec 2000 06:36:00 -0000 [thread overview]
Message-ID: <200002021617.LAA32411@reno.cis.upenn.edu> (raw)
In-Reply-To: <7666w7iqck.fsf@odie.lanl.gov>
There are actually 2 tools available to do this:
Konrad Hinsen has written a script to do dome docbook conversions, and SGMLS.pm
from David Megginson also has similar functionality. Both tools dont
do many tags, but are very easily extensable, being written in sane
scripting languages ..:-)
Dunno where to find them, but a search will bring up something...
Rahul
I got this from you:
>
>
> Sylvan> Hello folks, Do you know a tool to convert from DocBook
> Sylvan> SGML or XML DTD to LaTex format? (I don't mean to JadeTex
> Sylvan> or such format, I really mean to LaTex format, processable
> Sylvan> by TeTex for example)
>
> I don't know of any currently supported approach to that, unless you
> go a long route with db2html and then html2latex and do a lot of
> hand-editing.
>
> But your question might reveal some confusion about the whole TeX
> scenario. teTeX is just a TeX distribution that will handle latex and
> jadetex quite nicely, as long as you have all the macros installed.
>
> Also, I think that current versions of jadetex are based on top of
> latex, for what that's worth.
>
next prev parent reply other threads:[~2000-12-27 6:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 6:36 Sylvan Ravinet
2000-12-27 6:36 ` Mark Galassi
2000-12-27 6:36 ` Rahul Dave [this message]
2000-12-27 6:36 ` Jochem Huhmann
2000-12-27 6:36 ` Sylvan Ravinet
2000-12-27 6:36 ` Jochem Huhmann
2000-12-27 6:36 ` Sylvan Ravinet
2000-12-27 6:36 ` Jochem Huhmann
2000-12-27 6:36 ` Jorge Godoy
2000-12-27 6:36 ` Jochem Huhmann
2000-12-27 6:36 ` Rahul Dave
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200002021617.LAA32411@reno.cis.upenn.edu \
--to=rahul@reno.cis.upenn.edu \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
--cc=rosalia@lanl.gov \
--cc=sylvan@ravinet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).