Loading ...
Sorry, an error occurred while loading the content.

2307Re: Solution for the problem of gvimext in UTF-8 locale

Expand Messages
  • Rainux
    Jul 31, 2007
    • 0 Attachment
      Wonderful answer!

      Yes, I think the problem that Vim can not handle ucs-2le encoding file
      I've encoutered, is produced by the problem of native encoding
      conversion in Win32.

      On 7/31/07, MURAOKA Taro <KoRoN.KaoriYa@...> wrote:
      >
      > Hi Bram.
      >
      >
      > I see 3 items to think in your reply:
      > 1. Should vim continue to use iconv.dll?
      > 2. Is the newer libintl.dll portable?
      > 3. Can we modify gettext to use Windows native converter?
      > I'll answer one by one.
      >
      >
      > = 1. Should vim continue to use iconv.dll? =
      >
      > YES. Count of encodings which Windows support is different depends on
      > edition or installed other modules. Ex:Vista has large number of
      > encodings support, but 2000 has fewer. So it may become hard to
      > warrant
      > and provide enough number of encodings to real users who need encoding
      > conversion.
      >
      >
      > = 2. Is the newer libintl.dll portable? =
      >
      > YES. I have tried to compile a newer gettext (0.14.2) by MSVC 7.1.
      > And it have succeeded.
      >
      >
      > = 3. Can we modify gettext to use Windows native converter? =
      >
      > YES. It will be a work to implement another iconv implementation by
      > using Windows native encoding converter. And vim will become a
      > important example at the moment, to creating a patch.
      > BUT, I think it is not easy to be applied the patch by the gettext
      > maintainer. If it isn't applied, we must maintain and release
      > branched gettext codes.
      > --
      > MURAOKA Taro <KoRoN.KaoriYa@...>
      >
      >
      > On 7月31日, 午前5:11, Bram Moolenaar <B...@...> wrote:
      > > Taro Muraoka wrote:
      > > > Vim loads libintl.dll dynamically, so we can try multiple
      > > > implementations of libintl.dll easily.
      > >
      > > > In attached patch, it try to load libintl2.dll (which requres
      > > > libiconv.dll too) first, when it was failed, try to load libintl.dll
      > > > (not require libiconv.dll). After applied this patch, we would
      > > > distribute libintl2.dll and libiconv.dll separately from vim as an
      > > > "option".
      > >
      > > The libiconv.dll is big. I noticed one that is almost 1 Mbyte. While
      > > Win32 has native support for encoding conversions, thus mostly there is
      > > no reason to use libiconv.dll. Conversions not natively supported are
      > > likely to have problems anyway.
      > >
      > > The libintl.dll that's included with the big self-installing Vim is a
      > > bit old. I hesitate to replace it, because it should work with all
      > > different compilers.
      > >
      > > Is the problem that the ports of GNU gettext to Win32 have not been
      > > modified to use the Win32 API?
      > >
      > > --
      > > hundred-and-one symptoms of being an internet addict:
      > > 56. You leave the modem speaker on after connecting because you think it
      > > sounds like the ocean wind...the perfect soundtrack for "surfing the net".
      > >
      > > /// Bram Moolenaar -- B...@... --http://www.Moolenaar.net \\\
      > > /// sponsor Vim, vote for features --http://www.Vim.org/sponsor/\\\
      > > \\\ download, build and distribute --http://www.A-A-P.org ///
      > > \\\ help me help AIDS victims --http://ICCF-Holland.org ///
      >
      >
      > >
      >


      --
      Best Regards

      Rainux

      --~--~---------~--~----~------------~-------~--~----~
      You received this message from the "vim_multibyte" maillist.
      For more information, visit http://www.vim.org/maillist.php
      -~----------~----~----~----~------~----~------~--~---
    • Show all 9 messages in this topic