On 9 February 2015 at 18:22, Bert Huijben <b...@qqmail.nl> wrote: > > >> -----Original Message----- >> From: Branko Čibej [mailto:br...@wandisco.com] >> Sent: maandag 9 februari 2015 16:04 >> To: dev@subversion.apache.org >> Subject: Re: svn commit: r1654810 - >> /subversion/trunk/subversion/tests/cmdline/prop_tests.py >> >> On 09.02.2015 14:40, Philip Martin wrote: >> > Ivan Zhakov <i...@visualsvn.com> writes: >> > >> >> On 9 February 2015 at 16:22, Philip Martin <philip.mar...@wandisco.com> >> wrote: >> >>> "Bert Huijben" <b...@qqmail.nl> writes: >> >>> >> >>>> A few years ago we added code to the test suite that should force the >> >>>> locale to the expected locale and that works for me... >> >>> build/run_tests.py >> >>> >> >>> # Ensure the compiled C tests use a known locale (Python tests set the >> locale >> >>> # explicitly). >> >>> os.environ['LC_ALL'] = 'C' >> >>> >> >>> subversion/tests/cmdline/svntest/main.py >> >>> >> >>> # Set C locale for command line programs >> >>> os.environ['LC_ALL'] = 'C' >> >>> >> >> It seems this code doesn't work if Windows is configured to use non-US >> >> locale as *system* locale. >> > Does setting LANGUAGE work? Or perhaps LANG? >> >> No; Windows doesn't have the concept of per-process locales, only >> per-window input methods. > > Why does this then change the output of my dates from English to Dutch? > Changing LC_ALL environment variable doesn't affect 'svn ls -v' output on my Windows 7 machine: $ set LC_ALL=en_US $ svn ls -v D:\Ivan\SVN\trunk>svn ls -v CHANGES 1681897 breser 309451 май 27 04:10 CHANGES
> Windows itself doesn't support this, but the C runtime library certainly does > support this. > I've looked through VS2013 C runtime source code and didn't find code that access LC_ALL environment variable. I'm going to tweak this test to use xml mode to have locale independent output: test failures are bad. -- Ivan Zhakov
