From: Jochem Huhmann <joh@gmx.net>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: DocBook to LaTex?
Date: Wed, 27 Dec 2000 06:36:00 -0000 [thread overview]
Message-ID: <m3wvod2l6a.fsf@nova.revier.com> (raw)
In-Reply-To: <38A176A0.C174218B@ravinet.com>
* Sylvan Ravinet <sylvan@ravinet.com> 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)
You don't have to dig around in the sgml with regexps yourself. Look for
readily available packages for your favourite scripting language (I like
tclxml by Steve Ball a lot) and look at the documentation. It's quite
simple, I've hacked up a script to convert the contents of the
revhistory element to HTML this morning, just 50 lines of code,
including HTML headers and such.
> >And I'm quite sure that a lot of people have written such
> > throw-away scripts.
>
> Then people please tell us about - or throw us - yours! :-)
Such scripts tend to be ugly, undocumented and thrown away as early as
possible ;-) Especially my scripts, since I'm actually not a programmer.
> >The hard part is covering *all* DocBook markup in a
> > meaningful way and building LaTeX constructs from this which make
> > typographically sense. But I would like to see at least a extensible
> > framework to do such a conversion too.
>
> I can spend some little time on this, if we and others wanna join.
I guess the best thing one could do to get a start is to start
coding. But since the ways to get a result for a given problem as fast
as possible or to get a solid framework are quite different...
> Jade and JadeTex are definitely not my cup of tea...
I'm quite lucky these are available at all. But I've never really tried
to understand JadeTex.
Jochem
--
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
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
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 [this message]
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=m3wvod2l6a.fsf@nova.revier.com \
--to=joh@gmx.net \
--cc=docbook-tools-discuss@sourceware.cygnus.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).