public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: luc <ltaesch@europemail.com>
To: docbook-tools-discuss@sources.redhat.com
Subject: update
Date: Wed, 19 Dec 2001 22:49:00 -0000	[thread overview]
Message-ID: <3A976379.4060105@europemail.com> (raw)

sorry guys, but I havent looked  at docbook for a while. so id like a 
refresh.

so
1) is there any stylsheet for db4, or is it still 3.1 the reference one ?
2) if yes, are these stylesheets decsss or xslt ?
3) it yes, which is the recomended parser/processort ? saxon ? xt ? xalan ?
4) pdf : what is the relation with apache fop to latex ? is fop using 
latex, or just interpret a stylesheet? then , should all the nice 
algorhytm from latex be ported into a stylsheet , to have such nice page 
settings ?

thanks  a lot.
Luc

WARNING: multiple messages have this Message-ID
From: luc <ltaesch@europemail.com>
To: docbook-tools-discuss@sources.redhat.com
Subject: update
Date: Fri, 23 Feb 2001 22:34:00 -0000	[thread overview]
Message-ID: <3A976379.4060105@europemail.com> (raw)
Message-ID: <20010223223400.36NgsA8lC9okvA9ap1Ff1kLtI-pzBcAmJHYvdLNhAlk@z> (raw)

sorry guys, but I havent looked  at docbook for a while. so id like a 
refresh.

so
1) is there any stylsheet for db4, or is it still 3.1 the reference one ?
2) if yes, are these stylesheets decsss or xslt ?
3) it yes, which is the recomended parser/processort ? saxon ? xt ? xalan ?
4) pdf : what is the relation with apache fop to latex ? is fop using 
latex, or just interpret a stylesheet? then , should all the nice 
algorhytm from latex be ported into a stylsheet , to have such nice page 
settings ?

thanks  a lot.
Luc

             reply	other threads:[~2001-12-19 22:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 22:49 luc [this message]
2001-02-23 22:34 ` update luc

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=3A976379.4060105@europemail.com \
    --to=ltaesch@europemail.com \
    --cc=docbook-tools-discuss@sources.redhat.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).