public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Sylvan Ravinet <sylvan@ravinet.com>
To: Jochem Huhmann <joh@gmx.net>
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: <38A176A0.C174218B@ravinet.com> (raw)
In-Reply-To: <m3ln4u6f8o.fsf@nova.revier.com>

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)

>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! :-)

>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.

Jade and JadeTex are definitely not my cup of tea...

Regards,

-Sylvan
-- 
________________________________________
Sylvan Ravinet - Contact information:
http://www.ravinet.com/contact-info.html

  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 [this message]
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=38A176A0.C174218B@ravinet.com \
    --to=sylvan@ravinet.com \
    --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).