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

Re: issue #1954

From: <kfogel_at_collab.net>
Date: 2004-12-03 19:33:17 CET

VK Sameer <sameer@collab.net> writes:
> That would be very nice. A couple of questions, though. Is 1954 going to
> go into 1.1.2 or 1.2? svn_ctype_* functions have been marked with @since
> 1.2, so does relying on them for is_valid_pathname() automatically mean
> a 1.2 release?

Yes, #1954 is for 1.2. It need not go into 1.1.2 IMHO. Basically,
just make your changes work with trunk, and everything should be fine.

> Also, will/do those functions support non-ASCII, valid XML characters? I
> don't know how to enter those characters, and hence haven't been able to
> test myself.

Are you asking about the svn_ctype_* functions? They support exactly
what they're documented to support: all of UTF8, including both the
ASCII and non-ASCII parts of UTF8. Some of these characters are not
valid in XML, such as most of the control chars. And we've decided
not to support the few control chars that *are* valid XML anyway.

(Again, just to be clear, when I say "valid in XML", I mean "able to
be represented in XML, although XML-standard escape codes may be
necessary for some characters such as <, >, etc".)

Btw, what editing environment do you use? If it's GNU Emacs, I can
help you create non-ASCII characters. Or just tell us what example
strings you need, and we can attach a file to the issue, containing
those strings.

> OK, will do. Hope to send a first cut at the patch soon :)

Looking forward to it, thanks!


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 3 19:38:19 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.