X-Git-Url: https://diplodocus.org/git/nmh/blobdiff_plain/eee44c467bf31f198c73a51cab2f7e9d5a2ad47c..f0beecb5ab89a3e2e2913919f304b1dcdee53a66:/test/scan/test-scan-multibyte diff --git a/test/scan/test-scan-multibyte b/test/scan/test-scan-multibyte index 92900a90..3ce5df76 100755 --- a/test/scan/test-scan-multibyte +++ b/test/scan/test-scan-multibyte @@ -26,6 +26,7 @@ if test "${MULTIBYTE_ENABLED}" -ne 1; then test_skip "configure did not detect multibyte support" fi +require_locale en_US.utf-8 en_US.utf8 LC_ALL=en_US.UTF-8; export LC_ALL # @@ -37,17 +38,24 @@ LC_ALL=en_US.UTF-8; export LC_ALL # We use a test program to determine what the output width of U+0308 is # and adjust our test output appropriately. # +# True Spın̈al Tap fans will note that David st Hubbins was born in Squatney, +# London, England, and thus having his name language-tagged with "cy" is almost +# certainly incorrect. But in his own words: "Here lies David st Hubbins, +# and why not?". +# +# The second "* in the To line is just to exercise the parser a bit. +# cat > "${MH_TEST_DIR}/Mail/inbox/11" < -To: Sir Denis =?utf-8?q?Eton=E2=80=93Hogg? +From: David =?utf-8*cy?q?=EF=AC=86?= Hubbins +To: Sir Denis =?utf-8*?q?Eton=E2=80=93Hogg? Date: Friday, 2 Mar 1984 00:00:00 Subject: =?utf-8?q?Sp=C4=B1n=CC=88al_Tap_=E2=86=92_Tap_into_America!?= Things are looking great! EOF -width=`${MH_OBJ_DIR}/test/getcwidth "st→n̈"` +width=`${MH_OBJ_DIR}/test/getcwidth "→n̈"` if test $? -ne 0; then echo "getcwidth failed to run" exit 1 @@ -56,20 +64,20 @@ fi expected="$MH_TEST_DIR/$$.expected" actual="$MH_TEST_DIR/$$.actual" -if test "$width" -eq 4; then +if test "$width" -eq 3; then cat > "$expected" < "$expected" < $actual || exit 1 +run_prog scan -width 80 +inbox 11 > $actual || exit 1 check "$expected" "$actual" # @@ -87,26 +95,69 @@ Message-Id: 12@test.nmh Subject: =?UTF-8?B?MjAxMyBOZXcgWWVhcuKAmXMgRGVhbHMhIFN0YXJ0IHRoZSB5ZWFy?= =?UTF-8?B?IHJpZ2h0IHdpdGggYmlnIHNhdmluZ3M=?= -This message has an encoded Subject with an invalid character for the -ISO-8859-1 character set, but it (U+2019) is valid UTF-8. +This message has an encoded Subject with an invalid character for +single-byte character sets, but it (U+2019) is valid UTF-8. EOF -cat >"$expected" <"$expected" <"$actual" + # Don't use run_prog here because it loses the environment setting. + LC_ALL=C scan -width 74 last >"$actual" check "$expected" "$actual" fi +# +# Find out the width of our Unicode apostrophe (U+2019). Some implementations +# say it has a width of 2, but that seems totally bizarre to me. +# + +width=`${MH_OBJ_DIR}/test/getcwidth U+2019` +if test $? -ne 0; then + echo "getcwidth failed to run" + exit 1 +fi + # check scan width with a valid multibyte sequence -cat >"$expected" <"$expected" <"$expected" <"$actual" +run_prog scan -width 74 last >"$actual" check "$expected" "$actual" +if test "$ICONV_ENABLED" -eq 1; then + cat >"$expected" <"${MH_TEST_DIR}/Mail/inbox/13" < +Subject: =?iso-8859-1?B?kgo=?= +Date: Mon, 13 Jan 2014 14:18:33 -0600 + +The Subject: is an encoded single quote, 0x92. cpstripped() didn't +properly count it when decoding, which could be seen with: + + scan -format '%(decode{subject})%{body}' + +The scan listing was two characters too long. +EOF + + run_prog scan -width 80 last >"$actual" + check "$expected" "$actual" +fi + + exit $failed