vimcdoc-translate

[Vimcdoc-translate] 0.8.0-beta1

[Alecs K. <al...@pe...>]

Hi, all

ESR tells us, 'Release early, release often'.  But it's quite long since
our last release.  lang2's been busy these days.  So i'm just trying to
release our long-waited 0.8.0.  But before the formal public release is
out, i made out a beta for you guys to test.

You can download the tarball at:
http://vcd.gro.clinux.org/vimcdoc-0.8.0-beta1.tar.gz

I'm sorry but i've got no access to any M$s and i dunno how to make a
'windows setup.exe'...

I did rough tests on debian, crux, & fbsd. And it all worked fine.  I'd
like you to test it on your favorite platforms and do tell me if
something goes wrong.

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.

Attached are the changes since our last 0.7.0 release.


Thanks & Regards,

-- 
Alecs King

Re: [Vimcdoc-translate] 0.8.0-beta1

[Wenzhi L. <wen...@gm...>]

Hi wandys,

Thanks for covering my *ss and sorry about the absence. Still v busy
though.=20

>=20
> You can download the tarball at:
> http://vcd.gro.clinux.org/vimcdoc-0.8.0-beta1.tar.gz
I will test the tarball on Slackware and Hiweed (debian base)
and maybe Mandrake as well.

>=20
> I'm sorry but i've got no access to any M$s and i dunno how to make a
> 'windows setup.exe'...
You only need the nsis compiler  (http://nsis.sourceforge.net/), the latest=
 will
do. Or I can make it when I find a bit of free time. It can be done using w=
ine
under Linux/BSD, which is what I do.

>=20
> I did rough tests on debian, crux, & fbsd. And it all worked fine.  I'd
> like you to test it on your favorite platforms and do tell me if
> something goes wrong.
>=20
> 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?

Thanks again.

lang2