> From: Tim Rühsen <[email protected]> > Date: Thu, 25 Dec 2014 15:43:27 +0100 > > > FAIL: Test-idn-headers.px > > FAIL: Test-idn-meta.px > > > > These use EUC_JP encoded file name, but do not state > > --local-encoding on the wget command line, so the non-ASCII > > characters get mangled by Windows (because Windows tries to convert > > non-Unicode non-ASCII strings to the current system codepage). > > Test-idn-* tests that do state --local-encoding do succeed. Is it > > possible that the tests assume something about the local encoding, > > like that it's UTF-8? > > Let's start with 'Test-idn-meta'. > No non-ASCII filename will be written to disk, the Content-type is stated > correctly. --local-encoding set the encoding for when reading a local file or > the command line. So it shouldn't influence this test. And i can't reproduce > the stated behavior. > > Please send me the --debug output of this test with and without --local- > encoding given.
The output is attached. I collected that by redirecting the test script's stderr to a file, I hope that's what you meant. I noticed that the output says: converted 'http://<bunch of octal escapes>/' (CP1255) -> 'http://<another bunch of octal escapes/' (UTF-8) So I tried to use --local-encoding=EUC-JP, and that made the test succeed. The third attachment below is from that successful run.
Test-idn-meta.stderr
Description: Binary data
Test-idn-meta2.stderr
Description: Binary data
Test-idn-meta3.stderr
Description: Binary data
