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

Re: svn blame and filenames with non-ascii chars

From: Julian Reschke <julian.reschke_at_gmx.de>
Date: 2003-12-13 20:01:10 CET

Erik Huelsmann wrote:

> Hi Stefan,
> Are you sure this the correct order? it means that if you decode the URL you
> can be stuck with a non-UTF-8 encoded URL. I think Subversion libraries
> ...

I don't have an opinion on this particular issue, but it certainly would
be good to keep the terminology straight...:

There is no such thing as a "non-encoded" or "encoded" URI. RFC2396
describes legal URIs, and legal URIs never ever contain non-ASCII

The process of mapping the *characters* for instance -- inside a
filename -- containing non-ASCII characters should always be:

- encode using UTF-8, resulting in a byte sequence
- apply "hex"-escaping to those bytes that are outside ASCII or need to
be escaped inside a URI (such as a space character)


<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 13 20:02:58 2003

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.