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

Re: svn checkout - special characters in file name are not encoding properly

From: Alexander Skwar <alexanders.mailinglists+nospam_at_gmail.com>
Date: Fri, 13 Aug 2010 09:47:37 +0200

Hi.

2010/8/13 Vincent Lefevre <vincent-svn_at_vinc17.net>:
> On 2010-08-13 08:16:48 +0200, Alexander Skwar wrote:
>> 2010/8/13 Vincent Lefevre <vincent-svn_at_vinc17.net>
>> >
>> > On 2010-08-12 17:16:37 +0200, Stefan Sperling wrote:
>>
>> > > ~/bin/mysvn:
>> > >  #!/bin/sh
>> > >  env LC_CTYPE="en_US.<preferred charset>" svn update
>> >
>> > Wrong, wrong, wrong! Security hole!
>>
>> No, not wrong, but totally correct - especially, if you need to parse the
>> output in some script, you (kinda) MUST set the locale to some value,
>> that you know. Leaving it in a undefined state is no good at all.
>
> No it is wrong because the above script may send non-printable
> characters to the terminal, such as control sequences. Such
> control sequences can wreck the terminal and depending on its
> configuration, send the contents to a printer.

Well, if you want or need to parse the output of a program,
you'll need to make sure that it's in the "correct" locale. The
way to do that, is by setting the locale variables to the expected
values. Thus, it's totally correct to set LC_CTYPE to some
predefined value. Omiting this is just plain wrong. You're suggesting
that this should be omitted.

Alexander

--
↯    Lifestream (Twitter, Blog, …) ↣ http://alexs77.soup.io/%c2    ↯
↯ Chat (Jabber/Google Talk) ↣ a.skwar_at_gmail.com , AIM: alexws77  ↯
Received on 2010-08-13 09:48:32 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.