[Ruvim-devel] ruvim 0.5 release

hello,
here is an outline of what's gonna be in ruvim 0.5:
Release date: 20-ies of May -- as soon as all the issues will be resolved
Up to date with 6.2.5??/6.3 -- not yet fixed
Message translations
Menu
Man pages
new files translated:
pattern.txt, map.txt, tagsrch.txt, quickfix.txt, windows.txt, diff.txt,
autocmd.txt, filetype.txt, fold.txt.
This keeps bringing us really close to our goal of having everything in Vim
translated into Russian.
very new extra file:
russian.txt/russian.rux -- needs to include hints on working with russian.
draft already done (will put to rep this weekend), and I have updated it
also with info on how to get
support for russian l18n specific problems.
suggest Bram if he wants to include it on the main Vim tree, to use koi8-r
version of it there,
instead of utf-8 (more platform reach)
Issues to be resolved:
- Repository will be transformed to utf-8
- Release build script
- Finish windows.txt, diff.txt, autocmd.txt, filetype.txt, fold.txt
- Manpages need to be finished (Steve?)
- Final testing on how latest patches for Vim work with russian help/l18n
(will do that this weekend on win32)
- Not clear what can be done with win32 console direct output/inside vim aka
:version/--version problem. Bruno Haible (gettext developer) doesn't
seem to be enthusiastic about changing the way gettext works, blaming
microsoft for all the obstacles. However, user experience is obviously
harmed.
Bram needs help, as he doesn't know how to set up console codepage in his
Dutch win32 environment, since chcp seems only to be working for input.
- ruvim releases starting with 0.5 are packaged in the form of "Language
Pack",
ready to unpack into $VIMRUNTIME directory to be useful
- Releases to be available in koi8-r (gzipped tarball) and utf-8 and cp1251
(zip).
ps: Bram, I'm cc:ing this to you so that you can correct things or maybe
give
us more information about your plans. For example, if 6.3 is May reality, it
makes
sense to release ruvim 0.5 language pack together with or very soon after
with 6.3.
resourcefully yours,
vassily
mailto:vr[at]vrgraphics.ru
pgp key id 0x92B4A97C

Thread view

hello,
here is an outline of what's gonna be in ruvim 0.5:
Release date: 20-ies of May -- as soon as all the issues will be resolved
Up to date with 6.2.5??/6.3 -- not yet fixed
Message translations
Menu
Man pages
new files translated:
pattern.txt, map.txt, tagsrch.txt, quickfix.txt, windows.txt, diff.txt,
autocmd.txt, filetype.txt, fold.txt.
This keeps bringing us really close to our goal of having everything in Vim
translated into Russian.
very new extra file:
russian.txt/russian.rux -- needs to include hints on working with russian.
draft already done (will put to rep this weekend), and I have updated it
also with info on how to get
support for russian l18n specific problems.
suggest Bram if he wants to include it on the main Vim tree, to use koi8-r
version of it there,
instead of utf-8 (more platform reach)
Issues to be resolved:
- Repository will be transformed to utf-8
- Release build script
- Finish windows.txt, diff.txt, autocmd.txt, filetype.txt, fold.txt
- Manpages need to be finished (Steve?)
- Final testing on how latest patches for Vim work with russian help/l18n
(will do that this weekend on win32)
- Not clear what can be done with win32 console direct output/inside vim aka
:version/--version problem. Bruno Haible (gettext developer) doesn't
seem to be enthusiastic about changing the way gettext works, blaming
microsoft for all the obstacles. However, user experience is obviously
harmed.
Bram needs help, as he doesn't know how to set up console codepage in his
Dutch win32 environment, since chcp seems only to be working for input.
- ruvim releases starting with 0.5 are packaged in the form of "Language
Pack",
ready to unpack into $VIMRUNTIME directory to be useful
- Releases to be available in koi8-r (gzipped tarball) and utf-8 and cp1251
(zip).
ps: Bram, I'm cc:ing this to you so that you can correct things or maybe
give
us more information about your plans. For example, if 6.3 is May reality, it
makes
sense to release ruvim 0.5 language pack together with or very soon after
with 6.3.
resourcefully yours,
vassily
mailto:vr[at]vrgraphics.ru
pgp key id 0x92B4A97C

Vassily Ragosin wrote:
> suggest Bram if he wants to include it on the main Vim tree, to use
> koi8-r version of it there, instead of utf-8 (more platform reach)
For the help files only latin1 and utf-8 are supported. Conversion of
Russian text from utf-8 to your current 'encoding' should not be a
problem. On MS-Windows it should now always work, on Unix you need the
iconv library, which is a good thing anyway if your 'encoding' is not
latin1.
> ps: Bram, I'm cc:ing this to you so that you can correct things or
> maybe give us more information about your plans. For example, if 6.3
> is May reality, it makes sense to release ruvim 0.5 language pack
> together with or very soon after with 6.3.
I am getting much closer to a 6.3 beta test. It appears I have already
included all the changes to support the Russian help files. Only the
russian.txt needs to be added. Your Russian language pack can be made a
bit later.
What bothers me most is that you report that some characters disappear
in the console, using cp866. I still don't have enough information to
guess what the problem is. If this only happens with messages that were
handled with gettext, the problem could be that gettext produces cp1251
messages, while Vim expects cp866. Did you try ":lang mess ru_ru.cp866"
or ":lang mess Russian_Russia.cp866"?
--
hundred-and-one symptoms of being an internet addict:
72. Somebody at IRC just mentioned a way to obtain full motion video without
a PC using a wireless protocol called NTSC, you wonder how you never
heard about it
/// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
/// Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ Project leader for A-A-P -- http://www.A-A-P.org ///
\\\ Buy at Amazon and help AIDS victims -- http://ICCF.nl/click1.html ///