Testing recent versions of vim on Solaris, I get the following error:
From test_writefile.vim:
Found errors in Test_writefile_fails_conversion():
function RunTheTest[24]..Test_writefile_fails_conversion line 10: command did not fail: write ++enc=cp932
function RunTheTest[24]..Test_writefile_fails_conversion line 11: Expected ['line one', 'line two'] but got ['first line', 'cannot convert ?', 'third line']
The test was introduced in 8.0.0685 (e6bf655). From our i18n experts, it appears that Linux and Solaris took different paths when implementing the POSIX iconv spec; namely, that
the results of encountering invalid characters in the input stream (either those that are not characters in the codeset of the input file or that have no corresponding character in the codeset of the output file) shall be specified in the system documentation
Thus the assertions are based on bad assumptions.
I don't know the problem well enough to suggest a more universal test, or to judge whether the fix itself works on Solaris (though I'm guessing it doesn't). Solaris does support //REPLACE_HEX
and //RESTORE_HEX
modifiers to the arguments to iconv_open()
, which might prove useful here, and I've confirmed that the string in the test does get converted to and from a lossless hex representation appropriately when converted using the commandline iconv
tool.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
I get the same message.
—
On Solaris 'uname' returns:
SunOS
I don't have any other Unices around.
I've confirmed that this happens on 11.3 as well as the development builds of the next release. I don't have easy access to older versions.
It's easy enough to skip the test on Solaris, but I'd rather have a functioning test. I'm just not sure how to write one. And I suspect that the functionality is broken (on Solaris, or any OS with a similar iconv behavior) as well.
—
—
Fixed by 8.1.0347
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Closed #1872.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.