On 9 Feb 2014, at 22:08, Scott Derrick <[log in to unmask]> wrote:
> And that is a simple example. With books, parts, chapters, sections, line groups, paragraphs, sentences, etc... The indent level to make it readable to humans comes at a great cost, just because of the pesky white space.
if you apply the indenter in e.g. oxygen, it does exactly the right thing with
<lb/>When 'Omer smote 'is bloomin' lyre,<lb/>He'd 'eard men sing by and an' sea;<lb/>An' what he thought 'e might require,<lb/>'E went an' took -- the same as me!
and doesn’t introduce spurious white space. it looks perfectly readable to my (admittedly odd) eyes.
> The evidence of how broken TEI is in regard to white space is the plethora of "fixes" and kludgy code to deal with it.
I have to dispute this. I don’t think the TEI is broken at all as regards white space. You may argue that
_XML_ is complex and counterintuitive sometimes, but the ways of processing it are quite clear
and shouldn’t be classified as “fixes”. It’s just that you have to write processing code carefully.
> We have a <lb/>(line break) tag why not a <le/>(line end) tag?
well, it’s in the name - <lb> says “line break”, not “line start” ….
> Though I do think using paired, <lb n="x"/>line of text goes here<lb n="x" type="end"/> may solve the problem. And reduce the kludge factor in the white space handlers. in
then you break the semantics of <lb/> which mean “here is where a line breaks”. you’re implying there are two breaks,
when there is only one.
if you mean you actually want
<sl/>When 'Omer smote 'is bloomin' lyre,<el/>
<sl/>He'd 'eard men sing by and an' sea;<el/>
then you can already do this with <milestone> and <anchor> or the like.
Director (Research) of Academic IT
University of Oxford IT Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
Não sou nada.
Nunca serei nada.
Não posso querer ser nada.
À parte isso, tenho em mim todos os sonhos do mundo.