Garrett Rooney <rooneg@electricjellyfish.net> writes:
> On Thu, May 30, 2002 at 10:36:27AM -0500, Karl Fogel wrote:
> > 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."
>
> how does this solve the "i'm writing a gui svn client and i need to
> shove the log message in a text box to display it" problem. they
> still need to know the charset to be able to display it correctly, and
> if we don't provide either a standard char set for log messages or a
> way to figure out the char set, there is no way to make a client that
> will work with all subversion repositories automatically.
<not-serious>
How about just requiring that all log messages be valid HTML 4.0
strict, complete with charset and everything. The clients can launch
the browser of choice to view log message. :-)
</not-serious>
---------------------------------------------------------------------
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:58 2002