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

Re: bad output format design issue: svn log -v format is not parseable :-(

From: C.A.T.Magic <c.a.t.magic_at_gmx.at>
Date: 2004-04-04 01:44:42 CEST

Bruce Elrick wrote:
> The XML standard states that all whitespace *between* tags, including
> line feeds, is to be preserved by the parser. It is up to the
> application to decide what to do. If your xml viewer is collapsing
> spaces then it is not following the standard
> I'm not sure what the standard says about spaces in tags, but I think
> that can be changed without changing the semantic meaning of the XML.
> So
> <path
> action=">
> can be changed to <path action="A"> because the carriage return is *in*
> the tag, but
> <sometag>
> Contents of the
> tag
> </sometag>
> Is such that the string representing the contents of the tag would be
> "\n Contents of the\n tag\n"
> The application could then choose to manipulate the string. The initial
> line feed comes as a suprise to some people.
> Cheers...
> Bruce

if this is true, then the svn --xml output is REALLY broken because

<msg>* branches/issue-531-dev/subversion: Merged -r2699:2702 changes&#13;
from /trunk/subversion.&#13;
* subversion/libsvn_fs/reps-strings.c (APR_ARRAY_IDX):&#13;
Remove duplicate definition.&#13;

would turn into somewhing like "\r\r\n" at least on Windows.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 4 01:44:52 2004

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

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