unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Jason Rumney <jasonr@gnu.org>, 'Emacs Devel' <emacs-devel@gnu.org>
Subject: Re: Indentation contest nxml vs xml-mode
Date: Thu, 06 Mar 2008 23:38:12 +0100	[thread overview]
Message-ID: <47D07254.9020508@gmail.com> (raw)
In-Reply-To: <00da01c87fd8$6c881420$0600a8c0@us.oracle.com>

Drew Adams wrote:
>> ***** xml-mode
>> <outermost>
>>    <inner1><inner2>
>>        <inner3>Duh</inner3>
>>      </inner2>
>>    </inner1>
>> </outermost>
>>
>> ***** nxml-mode
>> <outermost>
>>    <inner1><inner2>
>>      <inner3>Duh</inner3>
>>    </inner2>
>>    </inner1>
>> </outermost>
> 
> IMO, neither is great (both are ugly and confusing). I've never seen XML
> indented like either of those (except when it wasn't formatted at all).
> FWIW, I use this:
> 
> <outermost>
>   <inner1><inner2>
>             <inner3>Duh</inner3>
>           </inner2>
>   </inner1>
> </outermost>
> 
> IOW: 1. Align opening and closing tags. 2. Indent just enough so that nested
> tags start after the </ of their parent.
> 
> Why? Because (1) you need to be able to easily find corresponding tags and
> (2) XML is verbose, so the less indentation the better. You could indent
> only one space, but I think it's more readable with two.
> 
> Another possibility is what we (most of us) use in Lisp - avoid starting
> lines with closing tags:
> 
> <outermost>
>   <inner1><inner2>
>             <inner3>Duh</inner3></inner2></inner1>
>   <inner1>some more</inner1></outermost>

Both your suggestions looks good IMO.

> That can also work well in some contexts.
> 
> I present lots of XML in doc everyday. I haven't found anything more
> readable than just indenting two spaces and aligning the corresponding
> element tags. I also align attributes. But I never, ever introduce or change
> significant whitespace, such as that within a text() node, if I can avoid
> it. For example, I never indent the text here:
> 
>        <foo>some text that is too
> long for a printed line</foo>
> 
> That should never be changed by automatic indentation to, say, this:
> 
>        <foo>some text that is too
>        long for a printed line</foo>
> 
> or this:
> 
>        <foo>some text that is too
>             long for a printed line
>        </foo>


Though as Jason (I believe) pointed out when we discussed it last time 
whitespace is not significant (most of the time ...) in XHTML, only in 
XML. But it is sometimes -- and those times are really hard to detect 
since they might depend on the style sheet, or?




  reply	other threads:[~2008-03-06 22:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06 18:41 Indentation contest nxml vs xml-mode Lennart Borgman (gmail)
2008-03-06 18:50 ` Drew Adams
2008-03-06 21:52   ` Lennart Borgman (gmail)
2008-03-06 22:21     ` Drew Adams
2008-03-06 22:38       ` Lennart Borgman (gmail) [this message]
2008-03-07  3:31         ` Drew Adams
2008-03-06 22:18   ` Jason Rumney
2008-03-06 22:34     ` Lennart Borgman (gmail)
2008-03-07  3:31     ` Drew Adams
2008-03-07  0:28 ` Miles Bader

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47D07254.9020508@gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).