public inbox for
 help / color / mirror / Atom feed
From: Norman Walsh <>
To: Eric Bischoff <>
Cc: Peter Toft <>,
Subject: Re: Local change of stylesheet
Date: Wed, 27 Dec 2000 06:36:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

/ Eric Bischoff <> was heard to say:
| > Or set the stylesheet using a custom driver. But maybe the dbhtml PI
| > should be extended...I can imagine wanting per-document stylesheets.
| > Kindof.

Actually, the dbhtml PI would be the wrong answer, support for
Associating Style Sheets with XML Documents[1] is the "right" answer.

| Nice idea, but it would somehow break the separation between the
| document and its style sheets, no? You would have to find *in the
| document* information about the style sheets you want. There's a big
| conceptual problem behind that.

It's a problem, but it has practical applications. Suppose that you
implement some one-off markup in a single document. For example, the
second edition of the XML REC has "erratum numbers" identified by

  <loc role="erratumreference" href="xxx">[E999]</loc>

In the "plain" presentation of this document, the E-numbers are to be
suppressed.  The stylesheet that accomplishes this is

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.


                                        Be seeing you,

Norman Walsh <> | No man's knowledge here can go beyond            | his experience.--John Locke

  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 [this message]
2000-12-27  6:36         ` Eric Bischoff

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

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