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

Re: [RFC/PATCH] commit messages not 8-bit compatible

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-05-30 17:36:27 CEST

Greg Hudson <ghudson@MIT.EDU> writes:
> It sounds like we don't have a lot of consensus here (which is
> unfortunate for Marcus, who I think signed onto this task with the
> understanding that there was a pre-existing choice). Karl seems to side
> with Marcus on translating because UTF-8 and the local charset for all
> interesting values; Mike and I would rather be charset-neutral; Branko
> wants to use UTF-8 for paths and be charset-neutral for everything
> else. (I'm not sure why pathnames deserve special treatment.)

No, I'd also prefer not to enforce a charset, but I think a good
compromise solution available. What if we simply say:

   "Subversion log messages may use any charset, so long as no byte in
   the message is zero."

This works for most charsets, and it's easy for us to enforce (without
looking, I know just where to put the check in the code :-) ), and
it's easy to explain.

In other words, we never *munge* anyone's log message data, but we
might *reject* it under certain (rare) circumstances.

> (I'd just like to point out at this juncture that, if we didn't use XML
> so damned much, we wouldn't have any problems being charset-neutral.
> That is all.)

Nah, XML isn't really causing this problem -- it's *technically* easy
to go either way on this question. We're just trying to find the best
policy from a usability standpoint.

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:34:40 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.