On Saturday 07 August 2010 02:43:13 Roger Leigh wrote: > > Just some additional background info. When I was troubleshooting this > > issue I noticed some inconsistent behavior in the boost regex > > logic. Some of my session names were allowed, and some were not, and I > > was banging my head against the wall trying to figure out what was > > different. A friend of my suggested it may have to do with how the > > ranges are handled, such as "a-z". Testing confirmed that hypothesis, at > > least in my environment. Apparently, those ranges are not very reliable > > with regard to your locale setting. > > Could you possible let me know what the locale and name was so I can > reproduce this?
I can reproduce it with grep on my machine: $ LC_COLLATE="en_US.UTF-8" $ echo WbwvSLZqAf | egrep '^[a-z0-9][a-z0-9-]' <-- match! WbwvSLZqAf $ export LC_COLLATE=C $ echo WbwvSLZqAf | egrep '^[a-z0-9][a-z0-9-]' <-- no match $ Note, the first character is an uppercase W, which shouldn't match. The regex is taken from the is_valid_filename() function in the schroot code. On my fedora machine, if I unset LC_COLLATE (which is the default), I get the same behavior as if it were set to "en_US.UTF-8". thanks, -Zach -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
