Hontvari Jozsef <hontvari@solware.com> writes:
> Brane Čibej
> > But you /can/ do exactly that on Windows. Even worse, you can change the
> > input locale used by any program on the fly, without touching the system
> > locale, and there is *no* way for the svn client (that only sees the
> > system locale, and the contents of a file) to figure out what happened.
>
> You can fool all three of the proposed systems in this way (UTF-8, email,
> binary). But if you consider this then you are optimizing for a user who
> works hard to fool the system - instead of the user who simply wants to use
> it in an international environment. That is a question of specification, it
> must be stated that svn command line client expects any log message in the
> system locale (if not specified otherwise, especially "UTF-8 already" can be
> a useful option theoretically).
Or, as kfogel proposed earlier, I think a good client application
should allow the user to specify a temporary locale for the log
message. Something like
svn commit -m "log message" --locale=some.locale
This way the 95% case is covered by assuming the system locale, and
when weirdos like kfogel occasionally decide to write a BIG5 log
message in emacs, he can "nudge" the svn client as a one time thing.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 4 17:09:03 2002