[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: DTD formal syntax
- From: "Bullard, Claude L (Len)" <email@example.com>
- To: Marcus Carr <firstname.lastname@example.org>, XML-Dev <email@example.com>
- Date: Fri, 08 Jun 2001 08:17:55 -0500
Markup being rather regular when formatted lends
itself to scanning by eye at least in the structures.
YeOldeRightMissing Quote is the one that is hard
to spot and for some reason is almost epidemic.
Of course, taking away minimization helped for
eyeballing it in many cases.
Am I the only one who doesn't like fully endtagged
samples in texts? I realize people like to copy
them and online it makes some sense, but in a
printed text, a deeply nested example takes up
a lot of space and as much as half of it can
be the end tags de-nesting.
Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h
From: Marcus Carr [mailto:firstname.lastname@example.org]
Sent: Thursday, June 07, 2001 6:14 PM
Subject: Re: DTD formal syntax
"Bullard, Claude L (Len)" wrote:
> Weirdly, after some time, they go to editing
> in the ASCII editor again. If the elements
> and attributes are named reasonably, and they
> know their subject domain, they can do it and
Absolutely. Before the Philipines and India got so good at marking up data,
ran a reasonably sized team of people who cleaned up the anomalies left over
from programmatic conversion. We always had plenty of structured editors
inhouse, but the vast majority of people found themselves using their
ASCII editor anyway. Even for CALS tables, there were a number of people who
felt that this was a more productive approach.
Marcus Carr email: email@example.com
Allette Systems (Australia) www: http://www.allette.com.au
"Everything should be made as simple as possible, but not simpler."
The xml-dev list is sponsored by XML.org, an initiative of OASIS
The list archives are at http://lists.xml.org/archives/xml-dev/
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: firstname.lastname@example.org