Re: problems matching umlauts in env vars

Your problem is IMHO, that you locale is already in utf8. This means that your env var is in utf8 but your $testString is in latin1. If this is the case you need to use Encode;. And update the bytes from your environment to utf.

$fileAsked = Encode::decode(utf8 => $ENV{'aa'});
[download]

Boris

Comment on Re: problems matching umlauts in env vars Select or Download Code

Replies are listed 'Best First'.
Re^2: problems matching umlauts in env vars by december (Pilgrim) on Jul 23, 2004 at 04:31 UTC
It's not in utf. When I encode it like you told me, it can't find the file anymore (the ë now changed to an utf sequence when I print the variable, and the filesystem doesn't like utf filenames). Both strings seem to be iso-8859-1, probably just plain 8bit. When I update it to utf, though, it's the DOT it doesn't want to match on - not the umlaut. `/^([\w\s.]+)$/ # unescaped /^([\w\s\.]+)$/ # or escaped` [download] Is there something wrong with the dot in the regex?	[reply] [d/l]
Re^3: problems matching umlauts in env vars by borisz (Canon) on Jul 23, 2004 at 08:08 UTC
No, inside the `[]` a . is the same as \. Boris	[reply] [d/l]
Re^4: problems matching umlauts in env vars by beable (Friar) on Jul 23, 2004 at 08:20 UTC
I believe Boris means: "No, inside the `[]` a . is the same as \.", but his square brackets got eaten by ~~a moose and a squirrel~~ not using code tags.	[reply] [d/l]
Re^5: problems matching umlauts in env vars by borisz (Canon) on Jul 23, 2004 at 08:26 UTC