Explain why the msgexec-4 test fails on mingw.

diff --git a/gettext-tools/tests/ChangeLog b/gettext-tools/tests/ChangeLog
index e113d78f73c28e08da5e71a88318403c654c403e..268ceeaa45c0e4d82d5e0ade0304b8adb1f1ef3d 100644 (file)
--- a/gettext-tools/tests/ChangeLog
+++ b/gettext-tools/tests/ChangeLog
@@ -2,7 +2,7 @@
 
        * msgexec-1: Filter out msgexec's warning about locale charset.
        * msgexec-2: Likewise.
-       * msgexec-4: Likewise.
+       * msgexec-4: Likewise. Explain why this test fails on mingw.
 
 2009-08-10  Bruno Haible  <bruno@clisp.org>
 

diff --git a/gettext-tools/tests/msgexec-4 b/gettext-tools/tests/msgexec-4
index e80bcbe24fa2d22e723df9befa327d09b2a73304..9683b406792b7c620b8b3f2cd5b114bb4e6f55e9 100755 (executable)
--- a/gettext-tools/tests/msgexec-4
+++ b/gettext-tools/tests/msgexec-4
@@ -2,6 +2,19 @@
 
 # Test msgexec on a PO file with contexts.
 
+# This test fails on mingw (in a Cygwin environment), due to the combination
+# of two reasons:
+# 1. The value of the environment variable MSGEXEC_MSGCTXT is stored
+#    in UTF-8 encoding (i.e. the PO file's encoding); it should be stored
+#    in the GetACP() encoding instead. This problem is inherent in msgexec,
+#    and msgexec warns about it - but in this test, we filter the warnings
+#    away.
+# 2. The child process is Cygwin's sh.exe, and is affected by a Cygwin bug:
+#    the values returned by getenv() in the child process, when the parent
+#    process is a mingw program, are in the GetOEMCP() encoding (should be
+#    in the GetACP() encoding). This has been reported at
+#    <http://cygwin.com/ml/cygwin/2009-08/msg00430.html>.
+
 tmpfiles=""
 trap 'rm -fr $tmpfiles' 1 2 3 15