Re: Problem with Cream/Vim installer
From: Albert Novick, Sun, September 09, 2007 11:38 pm
> > So the initial install is still wrong, but a re-install gets it
> > right?
> I only installed once. I started the installer a few times, but
> always aborted it before the install could begin because it was in
> the wrong language. The first time I went through with the install,
> I ended up with a normal Cream/Vim installation, all in English.
> Before doing that, I had removed the libintl.dll file from the Vim
> 7.0 folder that I already had installed. The immediate effect of
> doing that was that the Vim displays that had been in Japanese (as
> mentioned, my system is Japanese Windows XP) now were in English.
> The new Vim 7.1.2 and Cream installation were also in English.
> Just to see what would happen, I replaced the libintl.dll file in
> the new Vim installation and rebooted, but now there were no
> displays in Japanese, except for the ones that Windows generates.
I'm not sure how the libintl.dll works (:help win32-gettext). This is
something that the native Vim installers can install or that a user
can install from a separate distribution. But Cream does not include
it since our langauge support is basically non-existant.
> Finally, I tried starting cream-0-39-gvim-7-1-2.exe again. As ever,
> it said "Velcommen til setup-guiden....!" (Maybe that's Dutch and
> not German, but it isn't English or Japanese.)
The installer is completely separate software from Cream/Vim. Why
Vim's libintl.dll would affect it is beyond me, although the Nullsoft
Installer code may be checking loaded libraries.
> I often experience troubles with websites that I reach by following
> links in English that automatically redirect me to Japanese pages
> because the site can tell that my system is Japanese. I would rather
> be given the option to choose the language I want. Maybe it would be
> good if your installer gave a language setting option.
I'll have to research this, NSIS has had issues with languages for
quite some time. What Cream does now is only permit the ASCII ones,
but it has been a while since I've researched fixes for this.
> I hope this is helpful, and I'm hoping I will eventually be able to
> use Cream and/or Vim to edit html files.
Let's keep working on this, I'd like for language support to at least
be predictable, even if it means the less-than-ideal English-only.
Steve Hall [ digitect dancingpaper com ]
:: Cream... usability for Vim
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.