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

Re: Testing with spaces in filenames/paths [was: Space in filename causes path not found on commit]

From: Philipp Marek <philipp.marek_at_linbit.com>
Date: Fri, 2 Jul 2010 12:54:24 +0200

Hello Julian,

On Friday 02 July 2010, Julian Foad wrote:
> Then we can work on extending the principle in one or more different
> ways, which, I'm sure, will detect a bunch of bugs:
>
> * space in some of the within-WC paths;
>
> * other ASCII pathnames that require URI-escaping, or in any other way
> have the potential to be mis-handled by Subversion;
>
> * non-ASCII characters (but the ability to do this would depend on
> what locales the test platform supports, and so would require
> configuration magic to enable it);
>
> * similar things for repository-side paths.
I just want to mention that I'm doing something like this in the FSVS tests.

I've got a test script that runs the tests for
 * the current locale,
 * an UTF8 locale, and
 * a non-UTF8 locale (these are found via "locale -a | grep").

My Makefile defines an UTF8-string, and a localized string (via "$(shell
date +%b -d2001-01-27)", which, for german locales, conveniently returns
"Jän").
These strings are then used for directory and filenames, contents, and in
lots of other places where something might go wrong.

If you want to take a look - here's the Makefile:
  http://fsvs.tigris.org/source/browse/fsvs/branches/fsvs-1.2.x/fsvs/tests/Makefile.in?revision=2387&view=markup

Regards,

Phil
Received on 2010-07-02 12:55:28 CEST

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