From: Rahul Dave <rahul@reno.cis.upenn.edu>
To: joh@gmx.net (Jochem Huhmann)
Cc: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: DocBook to LaTex?
Date: Wed, 27 Dec 2000 06:36:00 -0000 [thread overview]
Message-ID: <200002121614.LAA02492@reno.cis.upenn.edu> (raw)
In-Reply-To: <m3snz12kfn.fsf@nova.revier.com>
SGMLS.pm:
http://www.cpan.org/modules/by-authors/David_Megginson/
Rahul
I got this from you:
>
> * Jorge Godoy <godoy@conectiva.com.br> wrote:
> > On Wed, Feb 09, 2000 at 04:16:00PM +0200, Sylvan Ravinet wrote:
> > > Jochem Huhmann wrote:
> > >
> > > > > > ftp://ftp.sol.no/public/users/v/vigu/sgml/dtd/docbook/docbk2latex.pl
> > > > It's no more there, yes. And I don't have a copy of it either. This
> > > > script was quite primitive btw, everyone with a scriptable parser (perl,
> > > > python, tcl...) and some knowlegde of DocBook and LaTeX should be able
> > > > to write a script that converts a given instance of (a subset of)
> > > > DocBook.
> > >
> > > So what would be the "design" of such a script? I can think of some
> > > regexps, but maybe it's not the best way (I never manipulated any XML
> > > parser)
> >
> > Seems that this tool (bcc) can do the job.
> > I've just downloaded that and I'll try to convert some documents into
> > LaTeX documents.
> >
> >
> > http://www.multimania.com/jcalles/XML/
>
> Oh dear. This is written in scheme, you need a scheme compiler (bigloo)
> to get it up and running. And patience, since this is written in C++,
> compiling took its time. The example scripts are a toolchain to convert
> the old LinuxDoc-DTD to DocBook (the ld2db stylesheet from the newer
> sgmltools does this also very fine, btw.) and then to LaTeX. Since
> LinuxDoc is very simple (no tables, no graphics) the supported DocBook
> is also quite simple. This surely can be extented (and bigloo comes with
> a nice IDE for XEmacs, too), but all the comments in the code are in
> french. I haven't even tried to understand what's going on in there.
>
> If I would start to code such a converter, I would use tcl, perl or
> python.
>
> Jochem
>
> --
> Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
>
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
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 [this message]
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=200002121614.LAA02492@reno.cis.upenn.edu \
--to=rahul@reno.cis.upenn.edu \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
--cc=joh@gmx.net \
/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).