Re: Spaces in Keyword Expansion

Vincent Lefevre wrote:
> In particular, how are control characters in filenames handled?

They aren't [currently] escaped/encoded.

> Are they encoded? If not, what about the end-of-line characters
> vs the svn:eol-style property?

All keywords must be a single line (and placing a EOL character in a
file name, while technically legal, is a really poor choice).

> And what about the '$' character
> in a filename, which must not appear inside a keyword expansion?

Don't do that (including '$' in a filename).

>
> Also, when are locales considered for keyword expansion?

They aren't [currently].

> How do Subversion developers suggest to parse keywords (in
> particular, Id)?

Don't parse it. $Id$ is just made up of (rev, url, date, author)
without explicit delimiters, so if you want any of those individual
values, just use $Rev$ or whatever.

If the keywords-as-hash code every gets applied (Hi Max!), those changes
will make it easier to revisit how the expansion should handle
non-alphanumeric characters (both in terms of escaping and encoding).
Keywords are very primitive now, and ever after the patch are still not
going to be useful for anything really bizarre.

HTH

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org