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

Re: Removing the --enable-utf8 flag

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-07-18 23:53:24 CEST

Marcus Comstedt <marcus@mc.pp.se> writes:
> I'm with Bill here. While basically working, this approach is not as
> robust as it could be. It's possible to fool it, by using things like
> ISO-646-whatever for example. (I don't seriously expect anyone to use
> any ISO-646 variant other than ISO-646-US novadays, that was in the
> time before ISO-8859, but it still feels a little flakey.) My
> intention for the --disable-utf8 variants was as a transitory measure
> while we iron out the problems with the real code. It was never meant
> to stay.

I think it's a question of how dangerous is it, versus how much will
it help people who are having iconv problems but need Subversion
working in the meantime? Anyway, I'll check it in for now, since it's
basically the same level of robustness as the old code, just without
the extra compile-time option. We can iron out the robustness at our

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 19 00:06:05 2002

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.