On 07/08/2015 09:49 PM, Robert Heller wrote:
> At Wed, 08 Jul 2015 20:36:42 +0100 Peter Flynn <
pe...@silmaril.ie> wrote:
[...]
>> Same applies to XML. The users shouldn't need to know what the markup is
>> unless they are trying to do something *very* complex (like linguistic
>> tagging in TEI). But not all editors are that good.
>
> The difference between editing XML and LaTeX is that 90% of the time LaTeX
> source is just text with paragraphs indicated by a blank line. I presume an
> XML document is going to look something like HTML 'gibberish', with <tag>'s
> all over the place:
Yes, exactly (well, almost)
> <section heading="This is a section">
That would be a bit like using the optional argument to \item: not
everything will work there (eg \verb won't). XML would typically use
even more of those dreaded tags:
<section>
<title>This is a section</title>
> <p>This is a paragraph. Blah, blah, blah...</p>
> <p>This is another paragraph. Mumble, mumble.</p>
> </section>
>
> As opposed to:
>
> \section{This is a section}
> This is a paragraph. Blah, blah, blah...
SGML could be simpler, with omissible end-tags and lots of cunning stuff
to abbreviate the markup, because it was designed in the days when it
all had to be typed in by hand. No-one in their right minds would do
that today, when editors can do it for you.
The reason for insisting on fully-enclosed elements is that it makes it
far easier to handle the resulting documents programmatically: you know
exactly where everything starts and ends before you begin.
But yes, it's more verbose if you insist on reading the markup as text.
We knew that. That's why the 10th design goal says what it says. The
benefits far outweigh the drawbacks.
> This is another paragraph. Mumble, mumble.
>
> OTOH, if you mean some sort of semi-WYSIWYG editor that 'hides' the markup,
> that is something different.
That is precisely what I meant. It's what people ask for, partly because
they have been conditioned by three decades of graphical interfaces to
believe that that is the only interface model in existence; and partly
because most authors shouldn't need to see pointy brackets or
backslashes and curly braces. As I said, it's unfortunate that there are
no editors out there good enough to satisfy this requirement *for the
non-XML-expert or non-TeX-expert author*.
> And no *I* refuse to use that sort of editor.
> When I edit a file I want to see what is really there, warts, markup,
> whatever. I don't want it colored or with markup (of whatever sort) 'hidden'
> from view.
Me too. I use Emacs for everything anyway :-)
///Peter