discuss: Author Guide - Writing a New HOWTO in DocBook
Subject:
RE: Author Guide - Writing a New HOWTO in DocBook
From:
Steven Peck ####@####.####
Date:
21 Mar 2001 19:18:35 -0000
Message-Id: <BB075B4F0B35914D80AFAF86E17BF34F063D67@base.blkmtn.org>
Would a HOSTS file on the local machine pointing to a local mirror help
while you are 'on the plane'?
127.0.0.1 oasis-open.org
OR this?
<!DOCTYPE article
PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://local/docbook/xml/4.1.2/docbookx.dtd">
With one, you would have to remember to redo your HOSTS file when you
reconnected, with the other, you would have to redo the doc header before
final release and with both you would have to have a web server loaded
locally, but don't we all have that? :)
or would this work while you were 'off the net'?
<!DOCTYPE article
PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"c:\docbook\xml\4.1.2\docbookx.dtd">
or Linux/UNIX equiv path name convention.
Just curious while trying to figure this out.
---------------------------------------------
Steven Peck ####@####.####
http://leaf.blkmtn.org
-----Original Message-----
From: Patrick K. O'Brien
To: LDP-Discuss
Sent: 3/21/2001 10:10 AM
Subject: RE: Author Guide - Writing a New HOWTO in DocBook
I think this is going to end up being tool specific. For example, I'm
using
a pretty generic XEmacs/PSGML setup on a Linux box that is NOT usually
connected to the Internet. XEmacs/PSGML has no problem with the
following
prolog. Instead of going to the Internet, it parses against the DTD
stored
on my local machine. (Though I haven't tested it from a plane, yet.
*grin*)
<?xml version="1.0"?>
<!DOCTYPE article
PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
<article>
</article>
---
Patrick K. O'Brien
Orbtech (http://www.orbtech.com)
"I am, therefore I think."
-----Original Message-----
From: Dan York ####@####.####
Sent: Tuesday, March 20, 2001 9:03 AM
To: Patrick K. O'Brien
Cc: LDP-Discuss
Subject: Re: Author Guide - Writing a New HOWTO in DocBook
Patrick,
> "If you're used to using catalog files to resolve system identifiers,
you
> may be dismayed to learn that system identifiers are required. Because
most
> tools favor system identifiers over public identifiers, all of the
> portability that was gained by the use of catalog files seems to have
been
> lost. In the long run, it'll be regained by the fact that XML system
> identifiers can be URNs, which will have a resolution scheme like
catalogs,
> but what about the short run?"
Interesting... I hadn't caught that part of TDG. The other problem
with "the long run" approach mentioned here is that URNs only help
you if you are online (at least how I understand them) since it might
reference a site somewhere. All well and good when you're in an office,
but rather lousy if you are sitting on a plane somewhere!
Thanks for the info,
Dan
_________________________
http://list.linuxdoc.org/
