On 2010-08-11 19:55:01 +0200, Stefan Sperling wrote: > On Wed, Aug 11, 2010 at 05:23:31PM +0200, Vincent Lefevre wrote: > > On 2010-08-11 16:26:32 +0200, Vincent Lefevre wrote: > > > Configuring a UTF-8 locale can yield non-portable behavior. > > Such as?
Outputting messages in a different language. Or any other non-portable behavior. Who knows... > > > There's a good reason why various scripts do a "LC_ALL=C". > > Then those scripts are written for projects which use ASCII filenames. That's unspecified. > > > Moreover there's no portable way to select a UTF-8 locale. > > Then your script will have to deal with the intricacies of supporting > several platforms when selecting the UTF-8 locale. For most platforms, > "export LC_CTYPE=en_US.UTF-8" should work fine. Not all. Thus this is bad. > Well, you can use en_US.UTF-8 to force the output to English. Wrong. There's no guarantee to work. And too often it doesn't work. > > And I think that "Do not use svn for scripts, reimplement > > everything using bindings." would not be a wise answer. > > Scripts written against bindings won't break when we change the > command line output (which happens every once in a while). It is certainly a better solution, but requires too much work in practice. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)
