Andre Poenitz wrote:
On Thu, Oct 04, 2007 at 09:55:58PM +0200, Dov Feldstern wrote:
[...]
Rather we'd need to store that as something like
<par>
<data>................</data>
<range>
<from>...</from>
<to>...</to>
<type>emph</emph>
</range>
<range>
<from>...</from>
<to>...</to>
<type>strong</emph>
</range>
</par>
Hmm, yes, this does describe the structure that I'm thinking of, I think
that it's the right approach.
There is however one main problem with this that I can think of: it
makes it harder to understand the .lyx file; even worse, if anyone tries
to edit the .lyx file directly, it would be disastrous, the ranges could
suddenly point to the wrong things, or to nowhere...
Well... then what about
<par>
....<begin>emph</begin>...<begin>strong</begin>..
....<end>emph</end>.....<end>strong</end>...
</pat>
This is 1:1 translatable to the structure above _and_ is more robust under
manual editing.
Andre'
OK, good. I believe this is very similar one of the solutions proposed
by TEI for this issue (http://www.tei-c.org/P4X/NH.html#NHMI).
Dov
