Tested on Slackware last night and the installation went fine (as root). I =
see the problem you had tough, and on more files. Here is my list:
I think the actual encoding of the files are (probably) correct. We just
need to help Vim to detect it. Will look into it but it will take time.
For everyone else, if you are still on the lis and listening, please try
the tarball/exe file yourself and play around with it. The more problem
we found the better. Thanks,
On 6/27/05, Alecs King <alecs@...> wrote:
> > > FYI, there's a known glitch: some files worked by dasn (ie.
> > > if_ole.txt,
> > > gui_w32.txt, os_msdos.txt, etc.) couldnt be properly viewed under the
> > > GBK locale. I dunno how to fix it so far. It might have something
> > > to do with the (incorrect/corrupted) utf-8 conversion.
> > hmmm. Can you provide a full list of files? What is the symptom? Can
> > you read them at all?
> gui_w16.txt, gui_w32.txt, if_ole.txt, intro.txt, map.txt,
> os_dos.txt, os_msdos.txt, os_win32.txt, sponsor.txt,
> uganda.txt, windows.txt
> :h intro@... (under GBK locale, aka in vim, enc=3Deuc-cn) shows nothing
> but malformed characters.
> though ok when euc=3Dutf-8.
> other files like usr_*.txt dont have this problem.
> Alecs King
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclic=
> Vimcdoc-translate mailing list