From: Eric Bischoff <ebisch@cybercable.tm.fr>
To: Norman Walsh <ndw@nwalsh.com>
Cc: Peter Toft <pto@sslug.dk>, docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: Local change of stylesheet
Date: Wed, 27 Dec 2000 06:36:00 -0000 [thread overview]
Message-ID: <39D4A758.F37479CB@cybercable.tm.fr> (raw)
In-Reply-To: <8766nf2vnj.fsf@nwalsh.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2132 bytes --]
Norman Walsh wrote:
>
>
> At the moment, I always put that filename on the command line, but is
> it completely wrong to point to that stylesheet from the document?
> Hard to say. What we really need is better facilities for handling XML
> documents and stylesheets at the system level. What I really want is
> simply a (possibly local, possibly global) association between that
> document and that stylesheet.
>
> [1] http://www.w3.org/TR/xml-stylesheet/
>
Someone (I don't remember who) proposed once a system-specific solution
to address something I believe is a system-specific problem: "aliases".
SGML-tools has something very near.
An "alias" would be an association of:
- the style sheet you need
- the catalogs you need
- the command line options you need
so it would define some kind of processing as a whole, while the current
system is splitting everything apart for modularity's sake.
Currently, the docbook-utils take a different approach:
- they try to determine the centralized catalogs (in /etc/sgml) from the
document's prologue
- the centralized catalogs point to "real" catalogs (in
/usr/share/sgml), like the one for Jade, the ones from the DBMSS, the
one for the iso entities, etc...
- the "real" catalogues define a lot of things, including with respect
to style sheets
but at this point you still don't know which style sheet you want to use
- you have to specify it on the command line. If you don't specify any
style sheet on the command line, then a default one for this DTD is
taken. Per default it's your html/docbook.cat or print/docbook.cat if
you are processing some docbook file.
--
Ãric Bischoff - mailto:ebisch@cybercable.tm.fr
__________________________________________________
\^o~_.
.~. ______ /( __ )
/V\ Toys story \__ \/ ( V
// \\ \__| (__=v
/( )\ |\___/ )
^^-^^ \_____( )
Tux Konqui \__=v
__________________________________________________
prev parent reply other threads:[~2000-12-27 6:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 6:36 Peter Toft
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` Norman Walsh
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` Norman Walsh
2000-12-27 6:36 ` Eric Bischoff [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=39D4A758.F37479CB@cybercable.tm.fr \
--to=ebisch@cybercable.tm.fr \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
--cc=ndw@nwalsh.com \
--cc=pto@sslug.dk \
/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).