From: Norman Walsh <ndw@nwalsh.com>
To: Peter Toft <pto@sslug.dk>
Cc: <docbook-tools-discuss@sourceware.cygnus.com>
Subject: Re: Where, what and how - The future of DocBook
Date: Wed, 27 Dec 2000 06:36:00 -0000 [thread overview]
Message-ID: <87ofyse10q.fsf@nwalsh.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0012031814190.1638-100000@pto.sslug>
| Fine - which tools are available for writing
| SGML/DocBook on Linux+xBSD or Windows?
The future is XML, not SGML.
| - Emacs and alike tools?
Naturally.
| - Any WYSIWYG editors?
That said, for Windows there are lots of XML editing tools coming
online. For production environments, I would recommend Arbortext's
Epic (disclaimer: I used to work for them). SoftQuad's XMetaL is less
expensive.
| - Any *fast* syntax verification system
James Clark's SP.
| - and what is being made in general
What is being made of what in general?
| Many companies don't accept DocBook - why?
Many companies do. Bug ones. With lots of documentation: Sun, HP,
Novell, etc. Who doesn't accept it (and why do you care that they
don't?)
| Can't we do better???
I'm sure we can.
| What is the future for SGML/DocBook versus XML/DocBook
| - again also regarding tools, the work efford going on
| at the moment etc.
XML is the future. But since XML is SGML, there's no loss here. You
can continue to use your favorite SGML tools. But I don't expect any
more SGML tools to be written. Ever.
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | We dance around in a ring and suppose,
http://nwalsh.com/ | but the Secret sits in the middle and
| knows.--Robert Frost
WARNING: multiple messages have this Message-ID
From: Norman Walsh <ndw@nwalsh.com>
To: Peter Toft <pto@sslug.dk>
Cc: <docbook-tools-discuss@sourceware.cygnus.com>
Subject: Re: Where, what and how - The future of DocBook
Date: Mon, 04 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <87ofyse10q.fsf@nwalsh.com> (raw)
Message-ID: <20001204060800.-kQ23gZmX8U4qW_x_C7vrJp5txV0D3k6TC8SFu_2S7Q@z> (raw)
In-Reply-To: <Pine.LNX.4.30.0012031814190.1638-100000@pto.sslug>
| Fine - which tools are available for writing
| SGML/DocBook on Linux+xBSD or Windows?
The future is XML, not SGML.
| - Emacs and alike tools?
Naturally.
| - Any WYSIWYG editors?
That said, for Windows there are lots of XML editing tools coming
online. For production environments, I would recommend Arbortext's
Epic (disclaimer: I used to work for them). SoftQuad's XMetaL is less
expensive.
| - Any *fast* syntax verification system
James Clark's SP.
| - and what is being made in general
What is being made of what in general?
| Many companies don't accept DocBook - why?
Many companies do. Bug ones. With lots of documentation: Sun, HP,
Novell, etc. Who doesn't accept it (and why do you care that they
don't?)
| Can't we do better???
I'm sure we can.
| What is the future for SGML/DocBook versus XML/DocBook
| - again also regarding tools, the work efford going on
| at the moment etc.
XML is the future. But since XML is SGML, there's no loss here. You
can continue to use your favorite SGML tools. But I don't expect any
more SGML tools to be written. Ever.
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | We dance around in a ring and suppose,
http://nwalsh.com/ | but the Secret sits in the middle and
| knows.--Robert Frost
next prev parent reply other threads:[~2000-12-27 6:36 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 6:36 Peter Toft
2000-12-03 9:23 ` Peter Toft
2000-12-27 6:36 ` Norman Walsh [this message]
2000-12-04 6:08 ` Norman Walsh
2000-12-27 6:36 ` Peter Toft
2000-12-05 14:12 ` Peter Toft
2000-12-27 6:36 ` Jorge Godoy
2000-12-05 16:58 ` Jorge Godoy
2000-12-27 6:36 ` Eric Bischoff
2000-12-06 5:10 ` Eric Bischoff
2000-12-27 6:36 ` Michael Wiedmann
2000-12-06 5:36 ` Michael Wiedmann
2000-12-27 6:36 ` Eric Bischoff
2000-12-06 5:53 ` Eric Bischoff
2000-12-27 6:36 ` Mark Johnson
2000-12-06 8:05 ` Mark Johnson
2000-12-27 6:36 ` Eric Bischoff
2000-12-06 8:15 ` Eric Bischoff
2000-12-27 6:36 ` madhu
2000-12-15 9:22 ` madhu
2000-12-27 6:36 ` Michael Smith
2000-12-15 10:40 ` Michael Smith
2000-12-27 6:36 ` Alan W. Irwin
2000-12-05 15:53 ` Alan W. Irwin
2000-12-27 6:36 ` Michael Smith
2000-12-05 21:27 ` Michael Smith
2000-12-27 6:36 ` Alan W. Irwin
2000-12-05 22:50 ` Alan W. Irwin
2000-12-27 6:36 ` Gregory Leblanc
2000-12-06 9:39 ` Gregory Leblanc
2000-12-27 6:36 ` Michael Smith
2000-12-06 0:51 ` Michael Smith
2000-12-27 6:36 ` Eric Bischoff
2000-12-06 5:23 ` Eric Bischoff
[not found] <200012061914.UAA08546@mailserv.caiw.nl>
2000-12-27 6:36 ` Hugo.van.der.Kooij
2000-12-06 12:31 ` Hugo.van.der.Kooij
[not found] <200012061723.KAA06519@gw.estinc.com>
2000-12-27 6:36 ` Craig Boone
2000-12-06 11:06 ` Craig Boone
[not found] ` <200012061858.LAA06946@gw.estinc.com>
2000-12-27 6:36 ` Craig Boone
2000-12-06 11:46 ` Craig Boone
2000-12-27 6:36 ` Gregory Leblanc
2000-12-06 11:12 ` Gregory Leblanc
-- strict thread matches above, loose matches on Subject: below --
2000-12-27 6:36 Peter Ring
2000-12-07 3:45 ` Peter Ring
2000-12-27 6:36 Peter Ring
2000-12-05 7:45 ` Peter Ring
2000-12-27 6:36 Pfaffner, Peter
2000-12-05 7:18 ` Pfaffner, Peter
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=87ofyse10q.fsf@nwalsh.com \
--to=ndw@nwalsh.com \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
--cc=pto@sslug.dk \
/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).