From: jari.aalto@poboxes.com (Jari Aalto+list.ding)
Subject: Re: <ULink>
Date: 27 Nov 1998 16:43:17 +0200 [thread overview]
Message-ID: <tbu2zl2o3e.fsf@blue.sea.net> (raw)
In-Reply-To: Norman Walsh's message of "Thu, 26 Nov 1998 09:05:40 -0500"
|Thu 1998-11-26 Norman Walsh <ndw@nwalsh.com> list.ding
| | OK. So it's probably just the result of cut'n paste from some SGML
| | source? The source for a linux HOWTO maybe? Hm... no... they use a
| | DTD called linuxdoc, it looks like...
|
| I believe that many (most, all, some?) linux documentation is being
| migrated from linuxdoc to DocBook. See also http://www.sgmltools.org/
Latest Linux journal had an article of SGMLtools 2, where is was specifically
stated that the Linux specific DTD will be abandoned as soon as SGMLTools 2
appears. Instead the DocBook DTD is now the only DTD they continue to use.
The transition phase from Linux DTD to DocBook (support for old DTD) is
6 months after SGMLTools 2 has been puslished.
jari
prev parent reply other threads:[~1998-11-27 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-26 11:07 <ULink> Steinar Bang
1998-11-26 11:22 ` <ULink> Norman Walsh
1998-11-26 12:17 ` <ULink> Steinar Bang
1998-11-26 14:05 ` <ULink> Norman Walsh
1998-11-27 14:43 ` Jari Aalto+list.ding [this message]
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=tbu2zl2o3e.fsf@blue.sea.net \
--to=jari.aalto@poboxes.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 NNTP newsgroup(s).