Nope that is not it... :(

pkn@precious:~/scripts/perl/csv$ ./parse.pl
1.36

$VAR1 = [];
[download]

did manage to get the "detect_bom => 1" into it with the new version. But as a result it no longer parses the file (correctly).

pkn@precious:~/scripts/perl/csv$ ./parse.pl
1.36

$VAR1 = [
          {
            'Naam' => 'Peter',
            'Adres' => "Li\x{eb}r",
            'Woonplaats' => "\x{f4}lsten"
          }
        ];
[download]

withoud bom detection it parses the test file but the encoding is still screwed.

Got some more reading to do. One thing I came across was:

my $aoh = csv(
               in => $FH,
               headers => 'auto'
             );
[download]

I thought having "headers => 'auto' in there would trigger an automagic detection of encoding. According to something I read in a man page this is not the case. Now if I could only remember what man page I was reading Text::CSV or Text::CSV_XS :S. Should not be to hard to find again.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.