On Fri, 7 May 2004, [UTF-8] Branko Ä^Libej wrote:
> > 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:-)
>
> Ah yes, you have a point. It looks like we only support platforms where
> the exec charset is a superset of ASCII. If AS/400 and OS/390 systems
> can run programs in this mode, then I'm quite happy to keep this
> restriction.
>
This will simplify svn_revnum_to_cstring and svn_cmdline_printf. I will go
forward under this assumption until someone objects...
//P
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 8 01:32:33 2004