Dov Feldstern wrote:
3) No ambiguity about nesting order.
I'm confused about the difference between 2 and 3. They sound like the
same thing: an inset UI enforces, clearly, a hierarchical style tree.
If what Martin means is that *LyX* will have no ambiguity, e.g, when
generating latex/XML, then I think that the disambiguation algorithm
suggested in this thread
http://permalink.gmane.org/gmane.editors.lyx.devel/95997 (plus the
refinement suggested by JMarc, which uses the extent of the ranges,
see the whole thread) would solve any ambiguities that might arise
with ranges; hence, this is not an advantage relative to ranges.
I think Martin's point was that nesting is (easily) user-controllable,
and unambiguous. Nesting behavior with ranges is magic.
rh
--
==================================================================
Richard G Heck, Jr
Professor of Philosophy
Brown University
http://frege.brown.edu/heck/
==================================================================
Get my public key from http://sks.keyserver.penguin.de
Hash: 0x1DE91F1E66FFBDEC
Learn how to sign your email using Thunderbird and GnuPG at:
http://dudu.dyn.2-h.org/nist/gpg-enigmail-howto
