public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Hugo van der Kooij <hvdkooij@vanderkooij.org>
To: DocBook Mailing List <docbook-tools-discuss@sourceware.cygnus.com>
Subject: Re: SGML beautifier?
Date: Fri, 20 Dec 2002 19:23:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0201222034500.8028-100000@ultra1.hugo.vanderkooij.org> (raw)
In-Reply-To: <1011693152.17391.160.camel@lisergia.olea.org>

On 22 Jan 2002, Ismael Olea wrote:

> El sáb, 19-01-2002 a las 20:21, Hugo van der Kooij escribió:
> > Hi,
> > 
> > Is there a way to reformat (and indent correctly) an existing DocBook SGML 
> > document?
> 
> A friend had wrote a perl tool for that. I've got it for some weeks but
> I haven't got the time to test it.
> 
> If you test it I'll thanks your comment.
> 
> http://www.olea.org/tmp/indent-sgml-xml/                              

I tried to feed it some coffee:

../../SOFTWARE/indentar.pl Coffee.sgml 

syntax error at line 1, column 61, byte 61 at ../../SOFTWARE/indentar.pl line 34

I found another script that does them all but it jumbles my <screen> 
sections.

Hugo.

-- 
All email send to me is bound to the rules described on my homepage.
    hvdkooij@vanderkooij.org		http://hvdkooij.xs4all.nl/
	    Don't meddle in the affairs of sysadmins,
	    for they are subtle and quick to anger.

WARNING: multiple messages have this Message-ID

From: Hugo van der Kooij <hvdkooij@vanderkooij.org>
To: DocBook Mailing List <docbook-tools-discuss@sourceware.cygnus.com>
Subject: Re: SGML beautifier?
Date: Tue, 22 Jan 2002 11:46:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0201222034500.8028-100000@ultra1.hugo.vanderkooij.org> (raw)
Message-ID: <20020122114600.5Ymkpq_2mippFdX1tu0WQoCHaQmFIX33A-KkkvR--NE@z> (raw)
In-Reply-To: <1011693152.17391.160.camel@lisergia.olea.org>

On 22 Jan 2002, Ismael Olea wrote:

> El sáb, 19-01-2002 a las 20:21, Hugo van der Kooij escribió:
> > Hi,
> > 
> > Is there a way to reformat (and indent correctly) an existing DocBook SGML 
> > document?
> 
> A friend had wrote a perl tool for that. I've got it for some weeks but
> I haven't got the time to test it.
> 
> If you test it I'll thanks your comment.
> 
> http://www.olea.org/tmp/indent-sgml-xml/                              

I tried to feed it some coffee:

../../SOFTWARE/indentar.pl Coffee.sgml 

syntax error at line 1, column 61, byte 61 at ../../SOFTWARE/indentar.pl line 34

I found another script that does them all but it jumbles my <screen> 
sections.

Hugo.

-- 
All email send to me is bound to the rules described on my homepage.
    hvdkooij@vanderkooij.org		http://hvdkooij.xs4all.nl/
	    Don't meddle in the affairs of sysadmins,
	    for they are subtle and quick to anger.

  parent reply	other threads:[~2002-01-22 19:46 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 ` Norman Walsh
2002-01-20  6:07   ` Norman Walsh
2002-12-20 19:23 ` Ismael Olea
2002-01-22  2:03   ` Ismael Olea
2002-12-20 19:23   ` Hugo van der Kooij [this message]
2002-01-22 11:46     ` Hugo van der Kooij
2002-12-20 19:23     ` Ismael Olea
2002-01-24 12:33       ` Ismael Olea

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=Pine.LNX.4.44.0201222034500.8028-100000@ultra1.hugo.vanderkooij.org \
    --to=hvdkooij@vanderkooij.org \
    --cc=docbook-tools-discuss@sourceware.cygnus.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).