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

Re: Remaining l10n issues

From: <lundblad_at_softhome.net>
Date: 2004-05-07 15:50:50 CEST

[UTF-8] Branko Œibej writes:

> lundblad@softhome.net wrote:
>
>> Else, we have other problems in the svn code I'm afraid. For example,
>> when looking at internal paths, we check for the slash character by the
>> character constant '/' (in the execution charset). If this doesn't match
>> UTF-8/ASCII, then we're in trouble and have to use constants for the code
>> point instead.
>
> No we don't, internal paths are always converted to UTF-8 first.
>
Yes, but you don't convert '/' and '.' from the execution character set to
UTF-8, do you? When I say "execution character set" I am refering to
something in the C standard (in case someone doesn't know). The compiler
converts string literals from the source character set to the corresponding
characters in the execution character set. If the system uses a character
set that isn't ASCII-base, I don't see how '/' could map to the correct
value in UTF-8. The numeric ASCII code for /, i.e. 47 would, however.

Still, if someone can say authorotatively that we don't need to care about
non-ASCII-based systems, this ddiscussion is pointless and our problems are
gone.

Hope I expressed myself better this time:-)
Regards,
//Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 7 15:51:16 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.