public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Norman Walsh <ndw@nwalsh.com>
To: Hugo van der Kooij <hvdkooij@vanderkooij.org>
Cc: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: SGML beautifier?
Date: Fri, 20 Dec 2002 19:23:00 -0000	[thread overview]
Message-ID: <87d705f76z.fsf@nwalsh.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0201192017590.30460-100000@ultra1.hugo.vanderkooij.org> (Hugo van der Kooij's message of "Sat, 19 Jan 2002 20:21:31 +0100 (CET)")

/ Hugo van der Kooij <hvdkooij@vanderkooij.org> was heard to say:
| Is there a way to reformat (and indent correctly) an existing DocBook SGML 
| document?
[...]
| Any suggestions?

Proceed with caution. As a general rule, you cannot pretty-print an
SGML or XML document without knowing the schema (lowercase S)
associated with it. That's because the significance of whitespace is
not apparent from the tags along, only from the content models.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Time wounds all heels.
http://nwalsh.com/            | 

WARNING: multiple messages have this Message-ID
From: Norman Walsh <ndw@nwalsh.com>
To: Hugo van der Kooij <hvdkooij@vanderkooij.org>
Cc: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: SGML beautifier?
Date: Sun, 20 Jan 2002 06:07:00 -0000	[thread overview]
Message-ID: <87d705f76z.fsf@nwalsh.com> (raw)
Message-ID: <20020120060700.b7rbSFX_BIJv-bqRLC7sDobOBfdUhfTRbgG7GUZ891k@z> (raw)
In-Reply-To: <Pine.LNX.4.44.0201192017590.30460-100000@ultra1.hugo.vanderkooij.org> (Hugo van der Kooij's message of "Sat, 19 Jan 2002 20:21:31 +0100 (CET)")

/ Hugo van der Kooij <hvdkooij@vanderkooij.org> was heard to say:
| Is there a way to reformat (and indent correctly) an existing DocBook SGML 
| document?
[...]
| Any suggestions?

Proceed with caution. As a general rule, you cannot pretty-print an
SGML or XML document without knowing the schema (lowercase S)
associated with it. That's because the significance of whitespace is
not apparent from the tags along, only from the content models.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Time wounds all heels.
http://nwalsh.com/            | 

  parent reply	other threads:[~2002-01-20 14:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-20 19:23 Hugo van der Kooij
2002-01-19 11:21 ` Hugo van der Kooij
2002-12-20 19:23 ` Ismael Olea
2002-01-22  2:03   ` Ismael Olea
2002-12-20 19:23   ` Hugo van der Kooij
2002-01-22 11:46     ` Hugo van der Kooij
2002-12-20 19:23     ` Ismael Olea
2002-01-24 12:33       ` Ismael Olea
2002-12-20 19:23 ` Norman Walsh [this message]
2002-01-20  6:07   ` Norman Walsh

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=87d705f76z.fsf@nwalsh.com \
    --to=ndw@nwalsh.com \
    --cc=docbook-tools-discuss@sourceware.cygnus.com \
    --cc=hvdkooij@vanderkooij.org \
    /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).