Re: Escaping single quotes in file names [was: --xml on all svn commands]

[kf...@collab.net]

Julian Foad <ju...@btopenworld.com> writes:
> (Note that a property name cannot contain a single quote character.)
> 
> I don't think there are any other places in the output produced by "svn".
> 
> AFAICT, our error messages were never meant to be machine-parsable.
> If they were, the quoting of file names must be the least of the
> difficulties. Certainly, at present, there is no programmatic way to
> tell whether and where a file name is present except by knowing the
> exact expected message.  Therefore there is almost no point in trying
> to escape single quotes in them.  It would only make them uglier for
> human readers.
> 
> The same goes for warnings except that there is more reason for a
> script to want to parse them (in a basic way) because they can be part
> of the expected output.  If the specific expected warning message is
> known, the file name can be extracted without any internal quote marks
> having been escaped.  So still no need.
> 
> The same goes for notifications as for warnings.
> 
> Therefore I don't think this is worth doing at all.

You know, when I originally wrote that we should be escaping single
quotes, I was thinking exactly of parsing error messages.  But now
that you point out all the above, I think you're right: the single
quotes would be the least of the problems, and no one's doing this
anyway.  So it's not worth it.

I withdraw the statement! :-)


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org