I just read that report and could not see a way to add comments, so I'm
replying here. I know I should really send this to the subversion, list,
I'll cc them.
Couldn't we just 'extent' the keyword syntax to include an encoding
or $Id:latin1$ --- probably ambiguous
or some other format (a SPECIAL Keyword to set encoding)
Where the $KeywordEncoding[<setencoding>]$ is consumed and no bytes are
Having the special keyword $KeywordEncoding[<encoding_here>]$ would be the
most transparent to users and probably the simplest and most useful.
On Sat, Feb 26, 2011 at 09:10, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 26.02.2011 16:58, rubis wrote:
> > Good morning Exuser me from my English but I am francais
> > I have a probleme with TortoiseSVN 1.6.12, Build 20536 and windows XP SP3
> > And autoprops
> > Under linux debian I have no probleme
> > local on debian
> > groenland:/depot# locale
> > When I edite a file I have
> > # Renseignements de révision de SVN :
> > # SVN: $Revision: 11 $
> > # SVN: $Author: stephane $
> > # SVN: $Date: 2011-02-26 16:30:46 +0100 (sam. 26 fÃ©vr. 2011) $
> > I have therefore for February of the strange caracteres fÃ©vr
> That's a known issue in the svn library:
> For now, all keywords are expanded as utf8. But your file seems to be in
> local encoding so you see the utf8 encoded chars as they are, i.e., not
> properly encoded.
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest Interface to (Sub)Version Control
> /_/ \_\ http://tortoisesvn.net
> To unsubscribe from this discussion, e-mail: [
Received on 2011-03-02 05:58:21 CET