From: "Eric S. Raymond" <esr@thyrsus.com>
To: Tim Waugh <twaugh@redhat.com>
Cc: docbook-tools-discuss@sources.redhat.com
Subject: Re: I've written an xml profiling tool
Date: Fri, 20 Dec 2002 19:23:00 -0000 [thread overview]
Message-ID: <20020919092410.GA31181@thyrsus.com> (raw)
In-Reply-To: <20020919085834.GN9457@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
Tim Waugh <twaugh@redhat.com>:
> > stylesheet=/usr/tmp/xmlprofile$$.xml
>
> Not in my package! I will change this to use mktemp. :-)
Oh, yeah. Duh. Good call.
> > <!-- Generate DocBook instance with correct DOCTYPE -->
> > <xsl:output method="xml"
> > doctype-public="-//OASIS//DTD DocBook XML V4.1.2//EN"
> > doctype-system="http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd"/>
>
> I'm a bit confused about what's happening here. We don't know that
> DocBook XML V4.1.2 is the correct version to use, do we? What if the
> input is DocBook XML V4.2 for instance? Also, the system identifier
> seems to be for a different version altogether.
I don't grok XSLT yet, so I copied the skeleton for the profiling
stylesheet straight from Jira Kosek's stylesheet and hacked it as
little as I could. It seems to work. That's all I know.
The original is at <http://www.kosek.cz/xml/dboscon/profiling/frames.html>.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
WARNING: multiple messages have this Message-ID
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Tim Waugh <twaugh@redhat.com>
Cc: docbook-tools-discuss@sources.redhat.com
Subject: Re: I've written an xml profiling tool
Date: Thu, 19 Sep 2002 02:27:00 -0000 [thread overview]
Message-ID: <20020919092410.GA31181@thyrsus.com> (raw)
Message-ID: <20020919022700._tZjFgqq9gEd9fWKFl0nSGLbDSLUoleSxeqb3UaEaBc@z> (raw)
In-Reply-To: <20020919085834.GN9457@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
Tim Waugh <twaugh@redhat.com>:
> > stylesheet=/usr/tmp/xmlprofile$$.xml
>
> Not in my package! I will change this to use mktemp. :-)
Oh, yeah. Duh. Good call.
> > <!-- Generate DocBook instance with correct DOCTYPE -->
> > <xsl:output method="xml"
> > doctype-public="-//OASIS//DTD DocBook XML V4.1.2//EN"
> > doctype-system="http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd"/>
>
> I'm a bit confused about what's happening here. We don't know that
> DocBook XML V4.1.2 is the correct version to use, do we? What if the
> input is DocBook XML V4.2 for instance? Also, the system identifier
> seems to be for a different version altogether.
I don't grok XSLT yet, so I copied the skeleton for the profiling
stylesheet straight from Jira Kosek's stylesheet and hacked it as
little as I could. It seems to work. That's all I know.
The original is at <http://www.kosek.cz/xml/dboscon/profiling/frames.html>.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-09-19 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 19:23 Eric S. Raymond
2002-09-18 17:16 ` Eric S. Raymond
2002-12-20 19:23 ` Tim Waugh
2002-09-19 1:58 ` Tim Waugh
2002-12-20 19:23 ` Eric S. Raymond [this message]
2002-09-19 2:27 ` Eric S. Raymond
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=20020919092410.GA31181@thyrsus.com \
--to=esr@thyrsus.com \
--cc=docbook-tools-discuss@sources.redhat.com \
--cc=twaugh@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).