Garrett Rooney <rooneg@electricjellyfish.net> writes:
> perhaps not, but if we just go with UTF-8 for log messages we solve
> the problem and make life easier for client writers everywhere.
> they're already going to have to convert a bunch of stuff to UTF-8
> anyway, so why not be more consistent and say for all textual
> information used by the subversion API we use UTF-8?
One reason, and one reason only :-)...
I'm worried about failed conversions, where the failure is not
detected until later, when someone's trying to read the log message.
Locale does not always reliably indicate the charset a given edit
session is using. (At least, I know this is true in my life, so I'm
assuming I can't be the only one).
We can only convert something to UTF-8 if we know what the something
is. If we can't know that with close to 100% reliability, then it's
better not to transform the data at all.
Log messages are not "textual information used by the Subversion API".
They are textual information passed around opaquely by the Subversion
API. Subversion never *uses* it, not the way it uses paths (comparing
and finding separators and so forth).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jun 1 14:15:39 2002