[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: [TSVN] Re: Cleaning up the doc indentation

From: Lübbe Onken <l.onken_at_rac.de>
Date: 2004-10-08 13:33:59 CEST

Simon,

> Do we have one 'clean' source file which follows your
> preferred layout, and
> has examples of most of the tag types? If so, let me know
> which one and I
> will change the others to conform to the same pattern.
I wouldn't say there's a single "perfect" file. "dug_propertypage" looks
good and contains examples for exceptions. Use your own good judgement.
Generally I'd like to have each xml tag on a single line, properly indented
with tabs of course. Exceptions are "inline" tags like <emphasis>,
<guibutton> or <literal> and others which do not contain other tags and most
of the time only a short text. As a rule of thumb. Give these "inline" tags
an own line when they are long.

So I'd leave: "folder, or the tree root (eg. <literal>C:\</literal>) is
found." untouched, but I'd split
"folder, or the tree root (eg. <literal>C:\documents and
settings\username\Application Data\Subversion\conf</literal>) is found."
into three lines like this:

"folder, or the tree root (eg.
<literal>C:\documents and settings\username\Application
Data\Subversion\conf</literal>)
is found."

(forgive me if my mailer wraps the long line)

Keep punctuation on the same line as the closing tag (as in my example
above) if you don't want a space before your comma, colon, bracket or
whatever.

Cheers
- Lübbe

--
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Oct 8 14:42:26 2004

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.