Problem: No Problem! Only some documentation is out dated. I hope this is the correct way how I communicate changes from which I think they could be helpful not only to me. If not, please show me the correct way. Thanks! Solution: This unofficial context patch. Files: src/po/README_mvc.txt
*** ..\vim-7.0.000\src\po\README_mvc.txt 2004-06-07 16:32:21.000000000 +0200 --- src\po\README_mvc.txt 2006-06-20 12:05:49.898793600 +0200 *************** *** 4,19 **** gnu-gettext.win32, a Windows port of gettext by Franco Bez <[EMAIL PROTECTED]>. You can find it at: ! http://home.a-city.de/franco.bez/gettext/gettext_win32_en.html First read the README.txt file in this directory for general remarks on translating Vim messages. SETUP ! Set the enviroment variable LANGUAGE to the language code for the language you ! are translating Vim messages to. Languagde codes are typically two characters and you can find a list of them at: http://www.geocities.com/click2speak/languages.html --- 4,33 ---- gnu-gettext.win32, a Windows port of gettext by Franco Bez <[EMAIL PROTECTED]>. You can find it at: ! http://people.freenet.de/franco.bez/gettext/gettext_win32_en.html First read the README.txt file in this directory for general remarks on translating Vim messages. + Another possibility is to use the gnuwin32 port of gettext. This is + recommended especially if you use already gnuwin32 tools to gunzip, bunzip, + patch etc. these files. You find the gnuwin32 version of gettext here: + + http://gnuwin32.sourceforge.net/packages/gettext.htm + + Yet another very strait forward way is to get the sources of gettext from + + http://www.gnu.org/software/gettext/gettext.html + + and build your own version of these tools. The documentation states that this + should be possible with MSVC4.0, MSVC5.0, MSVC6.0 or MSVC7.0, but you can + build it even successfully with MSVC8.0. + SETUP ! Set the environment variable LANGUAGE to the language code for the language you ! are translating Vim messages to. Language codes are typically two characters and you can find a list of them at: http://www.geocities.com/click2speak/languages.html *************** *** 23,29 **** Advanced tab in the System control panel. Next, edit Make_mvc.mak so that GETTEXT_PATH points the binary directory of ! the intallation. CREATING A NEW TRANSLATION --- 37,43 ---- Advanced tab in the System control panel. Next, edit Make_mvc.mak so that GETTEXT_PATH points the binary directory of ! the installation. CREATING A NEW TRANSLATION *************** *** 43,49 **** You will also need to edit the file names in the comments in the .po file. You need to remove the absolute directory specification (which has the form c:\vim61\src\). You can do this in Vim with the following command with the ! appropriate directory specfication for where you have installed the Vim source: %s/c:\\vim61\\src\\//g --- 57,63 ---- You will also need to edit the file names in the comments in the .po file. You need to remove the absolute directory specification (which has the form c:\vim61\src\). You can do this in Vim with the following command with the ! appropriate directory specification for where you have installed the Vim source: %s/c:\\vim61\\src\\//g *************** *** 57,63 **** nmake -f Make_mvc.mak xx.po ! where xx is the langauge code for the language needing translations. The original .po file is copied to xx.po.orig. --- 71,77 ---- nmake -f Make_mvc.mak xx.po ! where xx is the language code for the language needing translations. The original .po file is copied to xx.po.orig. -- Thanks a lot for the VIM Editor! Greetings Mathias