citerar Karl Fogel <kfogel@newton.ch.collab.net>:
> Colin Putney <cputney@whistler.net> writes:
> > 1) Do as Marcus and gstein propos and decree that log messages will
be
> > stored as UTF-8 in the repository and do the necessary conversion on
> > input and output as a crutch for those without Unicode capable-tools
> >
> > 2) Decree that log messages must be text, and store the metadata
> > specifiying the character set. Have the clients pass the character
set
> > to the core libraries and have the libraries return the character
set
> > along with the log messages at retrieval time.
>
> I like (2), but it doesn't even have to decree that they be "text".
> If we're storing another property saying what the charset is (or what
> Subversion's best guess is, anyway), then we just store the exact
> sequence of bits the user specified for the log message, along with
> metadata saying how to interpret that sequence of bits.
>
> This wins all around, because:
>
> - Clients receiving log msgs from the repository don't have to
> guess what encoding to use. The repository tells them.
>
> - The original data is still there, in case svn guessed wrong at
> input time.
>
> It means passing another parameter along with log_msg itself, but
> that's no big deal.
>
> +1 on this, for what it's worth.
>
> > I think we're still thrashing through the issue, so a vote is
premature.
>
> Agreed.
>
The problem with this is that a resonable complete subversion client
needs to be able to convert between several charsets. And if a text is
stored with a (to the client) unknown charset it can not be displayed.
Please have a look at the linked document.
http://www.unicode.org/unicode/uni2book/ch05.pdf
---------------------------------------------------------------------
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:11:03 2002