From: Peter Toft <pto@sslug.dk>
To: Norman Walsh <ndw@nwalsh.com>
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: <Pine.LNX.4.30.0012052258020.1160-100000@pto.sslug> (raw)
In-Reply-To: <87ofyse10q.fsf@nwalsh.com>
On 4 Dec 2000, Norman Walsh wrote:
> | Fine - which tools are available for writing
> | SGML/DocBook on Linux+xBSD or Windows?
>
> The future is XML, not SGML.
Agree. Can we get MANY people to use the tools?
How do we get the tools working?
- Which tools should the ordinary person download?
- How are they installed?
- Where is the first "lets try it" - example
- Where is the tutorials?
- Where is the full documentation?
- Can we get standard Linux/*BSD distributions
to carry the tools?
These the the *KEY* questions to answer in the best
possible way. I am sorry to say that I find it hard to
find it.
>
> | - 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.
URL - again, download?, install?, howto? + full docs.
>
> | - and what is being made in general
>
> What is being made of what in general?
Who is making what at the moment for DocBook?
>
> | 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?)
Eg. IMT-2000 standardization (UMTS) - check
http://www.3gpp.org -> all the work is Word-files.
I care a lot. I find that Word is eating WAY to much of
the areas, where DocBook could have been cool. I think
Word is preferred for many companies today - many do
not consider DocBook - that is a shame - we can all
agree on that!
>
> | Can't we do better???
>
> I'm sure we can.
We have to IMHO!
>
> | 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.
Ok ;-))
--
Peter Toft, Ph.D. [pto@sslug.dk] http://www.sslug.dk/~pto
"You don't win a battle by asking, `Will we win?'
You win it by doing your best to win" - Richard M Stallman
LinuxKonference i København: http://LinuxForum.dk/
WARNING: multiple messages have this Message-ID
From: Peter Toft <pto@sslug.dk>
To: Norman Walsh <ndw@nwalsh.com>
Cc: <docbook-tools-discuss@sourceware.cygnus.com>
Subject: Re: Where, what and how - The future of DocBook
Date: Tue, 05 Dec 2000 14:12:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.30.0012052258020.1160-100000@pto.sslug> (raw)
Message-ID: <20001205141200.ovw_281tUJ6UPxel0Y_3aWtp36E_0g4zrU8SrZD4J0Q@z> (raw)
In-Reply-To: <87ofyse10q.fsf@nwalsh.com>
On 4 Dec 2000, Norman Walsh wrote:
> | Fine - which tools are available for writing
> | SGML/DocBook on Linux+xBSD or Windows?
>
> The future is XML, not SGML.
Agree. Can we get MANY people to use the tools?
How do we get the tools working?
- Which tools should the ordinary person download?
- How are they installed?
- Where is the first "lets try it" - example
- Where is the tutorials?
- Where is the full documentation?
- Can we get standard Linux/*BSD distributions
to carry the tools?
These the the *KEY* questions to answer in the best
possible way. I am sorry to say that I find it hard to
find it.
>
> | - 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.
URL - again, download?, install?, howto? + full docs.
>
> | - and what is being made in general
>
> What is being made of what in general?
Who is making what at the moment for DocBook?
>
> | 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?)
Eg. IMT-2000 standardization (UMTS) - check
http://www.3gpp.org -> all the work is Word-files.
I care a lot. I find that Word is eating WAY to much of
the areas, where DocBook could have been cool. I think
Word is preferred for many companies today - many do
not consider DocBook - that is a shame - we can all
agree on that!
>
> | Can't we do better???
>
> I'm sure we can.
We have to IMHO!
>
> | 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.
Ok ;-))
--
Peter Toft, Ph.D. [pto@sslug.dk] http://www.sslug.dk/~pto
"You don't win a battle by asking, `Will we win?'
You win it by doing your best to win" - Richard M Stallman
LinuxKonference i København: http://LinuxForum.dk/
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
2000-12-04 6:08 ` Norman Walsh
2000-12-27 6:36 ` Peter Toft [this message]
2000-12-05 14:12 ` Peter Toft
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 ` Eric Bischoff
2000-12-06 5:23 ` Eric Bischoff
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 ` 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
[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
2000-12-27 6:36 ` Gregory Leblanc
2000-12-06 11:12 ` Gregory Leblanc
[not found] ` <200012061858.LAA06946@gw.estinc.com>
2000-12-27 6:36 ` Craig Boone
2000-12-06 11:46 ` Craig Boone
-- 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=Pine.LNX.4.30.0012052258020.1160-100000@pto.sslug \
--to=pto@sslug.dk \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
--cc=ndw@nwalsh.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).