Am Samstag, 20. Dezember 2014, 10:28:53 schrieb Eli Zaretskii: > I've looked into the failing tests. Here's the list of failed tests > and my conclusions from looking at the logs and the test scripts: > > 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. Tim
signature.asc
Description: This is a digitally signed message part.
