----- Original Message -----
From: "John Szakmeister" <john@szakmeister.net>
[snip]
> Wow, can't say I like this either. Any recommendations
> on how we should solve this problem? I saw the
> discussion about performing UTF-8 encoding, and
> *then* URI encoding. But how are we to validate
> something like 'http://localhost:8888/obj/repo/%e9'.
> Do we need to URI decode it, UTF8 encode, and
> the URI encode it again?
I heard that there will soon be domain names with
special characters in it, not just ASCII chars. How
is the definition of that encoding? Does someone know?
All I found about that is
ftp://ftp.rfc-editor.org/in-notes/rfc3490.txt
ftp://ftp.rfc-editor.org/in-notes/rfc3491.txt
ftp://ftp.rfc-editor.org/in-notes/rfc3492.txt
http://www.ietf.org/html.charters/OLD/idn-charter.html
http://www.ietf.org/proceedings/00jul/SLIDES/idn-race/
> Who should be responsible
> for doing this? The command line client, or client library?
I guess that depends on the solution for the problem.
But I'd prefer to handle that kind of conversion inside
the library so that clients only have to convert their
internal data to UTF8 - such a conversion is possible
from all programming languages. More special conversions
may not be available in some scripting languages.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 13 23:17:15 2003