This is the mail archive of the
docbook@lists.oasis-open.org
mailing list for the DocBook project.
OMITTAG, SHORTTAG, SHORTREF (Re: Including OS Version information on DocBook elements)
- To: docbook at lists dot oasis-open dot org
- Subject: DOCBOOK: OMITTAG, SHORTTAG, SHORTREF (Re: Including OS Version information on DocBook elements)
- From: Karl EICHWALDER <ke at gnu dot franken dot de>
- Date: 06 Jan 2000 10:53:53 +0100
- References: <19991221122224.B75275@catkin.nothing-going-on.org> <sh4sdcfeva.fsf@Frechet.suse.de> <6339-Tue21Dec1999122219-0500-ndw@nwalsh.com> <shogbjh0ae.fsf@tux.gnu.franken.de> <7780-Wed22Dec1999104211-0500-ndw@nwalsh.com>
- Reply-To: docbook at lists dot oasis-open dot org
Norman Walsh <ndw@nwalsh.com> writes:
| OMITTAG and SHORTTAG are only convenient for the author that uses
| them. Some other author, less familiar with the DTD is just going
| to be confused.
Both these features are easy to understand. To my experience, authors
are upset if they aren't allowed to use these features anymore[1]; I'm
talking about authors coming from quertz/linuxdoc or from HTML (in case
of OMITTAG). I'm curious how fast XHTML (once approved) will be
accepted; don't take me wrong: I've strong feelings that XHTML will be a
_big_ win for the community[2].
DATATAG and SHORTREF are different animals; SHORTREFs are too clever.
Of course, Adam, you're right: If the author feels comfortable to use
this feature, SGML normalization and sgml-to-xml are not that difficult
:)
___
[1]I want to exclude "unclosed short tags"; those tags are looking
ugly.
[2]I don't know whether the lynx parser is already fixed -- last time I
checked lynx I noticed that it treats the presence of "</p>" in a very
strange manner. Sometimes it wants a superfluous "<p>" to close(!) a
paragraph (before <pre>)...
--
work : ke@suse.de |
: http://www.suse.de/~ke/ | ------ ,__o
personal: ke@gnu.franken.de | ------ _-\_<,
: http://www.franken.de/users/gnu/ke/ | ------ (*)/'(*)