Rather than trying to come up with explanations for why get what you get... let me just recommend that, when debugging encoding problems, you start by looking at the raw data1 with as few tools in between as possible. Every tool (terminal, putty, grep, vi, browser, whatever) or processing step might have it's own problems or automagic-isms with one or the other encoding, so what you see may not necessarily be what you really have.
My preferred tool in cases like these is a classical hexdump, or as ikegami suggested, a Devel::Peek dump (when in Perl). Together with some knowledge of how the various encodings represent data, this usually allows you to figure out what's going wrong, eventually.
In this particular case, I would start by looking at a hexdump of the CSV file (e.g. with the command line tool hexdump, which is installed/available on most distros). Then we would reliably know what the "Déjà" is represented as in the CSV file.
___
1 though Juerd might disagree, saying that you shouldn't, unless you're an expert already...
In reply to Re^7: encoding problem om Ubuntu Linux
by almut
in thread encoding problem om Ubuntu Linux
by j.goor
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |