The latest iconv dll from gnuwin32 is named libiconv2.dll. Should vim also try to load this dll instead of the old libiconv.dll? For the time being I was able to solve the problem by copying libiconv2.dll to libiconv.dll.
—
Reply to this email directly or view it on GitHub.
The latest iconv dll from gnuwin32 is named libiconv2.dll. Should vim also try to load this dll instead of the old libiconv.dll? For the time being I was able to solve the problem by copying libiconv2.dll to libiconv.dll
Yes it works fine. I just want to point out that users with newer windows machines will most probably download the gnuwin32 version of libiconv (libiconv2.dll) and find that vim will fail to convert their file encoding (euc-jp in my case).
dll names are hard-coded in mbyte.c. but it seems that there are more names. for example msys2 provide libiconv-2.dll not libiconv2.dll.
Closed #440.
@brammool But -2
will be changed if the version of libtool will be changed.
@mattn No, it will be changed when libiconv changes its API and if compatibility is lost. Not when libtool is changed.
Ah, I did missunderstand. @brammool so it' possible to add libiconv-2.dll
.