updated for version 7.0001v7.0001

34 files changed, 159736 insertions, 0 deletions

diff --git a/src/po/Make_ming.mak b/src/po/Make_ming.mak
new file mode 100644
index 0000000000..810efb036d
--- /dev/null
+++ b/src/po/Make_ming.mak
@@ -0,0 +1,67 @@
+# Makefile for the Vim message translations for mingw32
+#
+# Eduardo F. Amatria <eferna1@platea.pntic.mec.es>
+#
+# Read the README_ming.txt file before using it.
+#
+# Use at your own risk but with care, it could even kill your canary.
+#
+# Previous to all you must have the environment variable LANGUAGE set to your
+# language (xx) and add it to the next three lines.
+#
+
+LANGUAGES =	af ca cs de en_GB es fr it ja ko no pl ru sk sv uk zh_TW \
+		zh_TW.UTF-8 zh_CN zh_CN.UTF-8
+MOFILES =	af.mo ca.mo cs.mo de.mo en_GB.mo es.mo fr.mo it.mo ja.mo \
+		ko.mo no.mo pl.mo ru.mo sk.mo sv.mo uk.mo \
+		zh_TW.mo zh_TW.UTF-8.mo zh_CN.mo zh_CN.UTF-8.mo
+
+PACKAGE = vim
+
+# Uncomment one of the lines below or modify it to put the path to your
+# gettex binaries; I use the first
+#GETTEXT_PATH = C:/gettext.win32/bin/
+#GETTEXT_PATH = C:/gettext-0.10.35-w32/win32/Release/
+#GETTEXT_PATH = C:/cygwin/bin/
+
+MSGFMT = $(GETTEXT_PATH)msgfmt
+XGETTEXT = $(GETTEXT_PATH)xgettext
+MSGMERGE = $(GETTEXT_PATH)msgmerge
+
+MV = move
+CP = copy
+RM = del
+MKD = mkdir
+
+.SUFFIXES:
+.SUFFIXES: .po .mo .pot
+.PHONY: first_time all install clean $(LANGUAGES)
+
+.po.mo:
+	$(MSGFMT) -o $@ $<
+
+all: $(MOFILES)
+
+first_time:
+	$(XGETTEXT) --default-domain=$(LANGUAGE) \
+		--add-comments --keyword=_ --keyword=N_ $(wildcard ../*.c) ../if_perl.xs $(wildcard ../globals.h)
+
+$(LANGUAGES):
+	$(XGETTEXT) --default-domain=$(PACKAGE) \
+		--add-comments --keyword=_ --keyword=N_ $(wildcard ../*.c) ../if_perl.xs $(wildcard ../globals.h)
+	$(MV) $(PACKAGE).po $(PACKAGE).pot
+	$(CP) $@.po $@.po.orig
+	$(MV) $@.po $@.po.old
+	$(MSGMERGE) $@.po.old $(PACKAGE).pot -o $@.po
+	$(RM) $@.po.old
+
+install:
+	$(MKD) $(VIMRUNTIME)\lang\$(LANGUAGE)
+	$(MKD) $(VIMRUNTIME)\lang\$(LANGUAGE)\LC_MESSAGES
+	$(CP) $(LANGUAGE).mo $(VIMRUNTIME)\lang\$(LANGUAGE)\LC_MESSAGES\$(PACKAGE).mo
+
+clean:
+	$(RM) *.mo
+	$(RM) *.pot
+
+
diff --git a/src/po/Make_mvc.mak b/src/po/Make_mvc.mak
new file mode 100644
index 0000000000..b69b5abc59
--- /dev/null
+++ b/src/po/Make_mvc.mak
@@ -0,0 +1,62 @@
+# Makefile for the Vim message translations for MSVC
+# (based on make_ming.mak)
+#
+# Mike Williams <mrw@eandem.co.uk>
+#
+# Please read README_mvc.txt before using this file.
+#
+
+LANGUAGES =	af ca cs de en_GB es fr it ja ko no pl ru sk sv uk zh_TW \
+		zh_TW.UTF-8 zh_CN zh_CN.UTF-8
+MOFILES =	af.mo ca.mo cs.mo de.mo en_GB.mo es.mo fr.mo it.mo ja.mo \
+		ko.mo no.mo pl.mo ru.mo sk.mo sv.mo uk.mo \
+		zh_TW.mo zh_TW.UTF-8.mo zh_CN.mo zh_CN.UTF-8.mo
+
+PACKAGE = vim
+
+# Correct the following line for the installation directory of gettext
+GETTEXT_PATH = H:\gettext.win32.msvcrt\bin
+
+MSGFMT = $(GETTEXT_PATH)\msgfmt
+XGETTEXT = $(GETTEXT_PATH)\xgettext
+MSGMERGE = $(GETTEXT_PATH)\msgmerge
+
+MV = move
+CP = copy
+RM = del
+MKD = mkdir
+LS = dir
+
+LSFLAGS = /b /on /l /s
+
+INSTALLDIR = $(VIMRUNTIME)\lang\$(LANGUAGE)\LC_MESSAGES
+
+.SUFFIXES:
+.SUFFIXES: .po .mo .pot
+
+.po.mo:
+	$(MSGFMT) -o $@ $<
+
+all: $(MOFILES)
+
+files:
+	$(LS) $(LSFLAGS) ..\*.c ..\if_perl.xs ..\globals.h > .\files
+
+first_time: files
+	$(XGETTEXT) --default-domain=$(LANGUAGE) --add-comments --keyword=_ --keyword=N_ --files-from=.\files
+
+$(LANGUAGES): files
+	$(XGETTEXT) --default-domain=$(PACKAGE) --add-comments --keyword=_ --keyword=N_ --files-from=.\files
+	$(MV) $(PACKAGE).po $(PACKAGE).pot
+	$(CP) $@.po $@.po.orig
+	$(MV) $@.po $@.po.old
+	$(MSGMERGE) $@.po.old $(PACKAGE).pot -o $@.po
+	$(RM) $@.po.old
+
+install:
+	if not exist $(INSTALLDIR) $(MKD) $(INSTALLDIR)
+	$(CP) $(LANGUAGE).mo $(INSTALLDIR)\$(PACKAGE).mo
+
+clean:
+	$(RM) *.mo
+	$(RM) *.pot
diff --git a/src/po/Makefile b/src/po/Makefile
new file mode 100644
index 0000000000..d54913062b
--- /dev/null
+++ b/src/po/Makefile
@@ -0,0 +1,135 @@
+# Makefile for the Vim message translations.
+
+# TODO make this configurable
+# Note: ja.sjis, *.cp1250 and zh_CN.cp936 are only for MS-Windows, they are
+# not installed on Unix
+
+LANGUAGES =	af ca cs de en_GB es fr it ja ko no pl ru sk sv uk zh_TW \
+		zh_TW.UTF-8 zh_CN zh_CN.UTF-8
+MOFILES =	af.mo ca.mo cs.mo de.mo en_GB.mo es.mo fr.mo it.mo ja.mo \
+		ko.mo no.mo pl.mo ru.mo sk.mo sv.mo uk.mo \
+		zh_TW.mo zh_TW.UTF-8.mo zh_CN.mo zh_CN.UTF-8.mo
+
+PACKAGE = vim
+SHELL = /bin/sh
+
+# The OLD_PO_FILE_INPUT and OLD_PO_FILE_OUTPUT are for the new GNU gettext
+# tools 0.10.37, which use a slightly different .po file format that is not
+# compatible with Solaris (and old gettext implementations) unless these are
+# set.  gettext 0.10.36 will not work!
+MSGFMT = OLD_PO_FILE_INPUT=yes msgfmt -v
+XGETTEXT = OLD_PO_FILE_INPUT=yes OLD_PO_FILE_OUTPUT=yes xgettext
+MSGMERGE = OLD_PO_FILE_INPUT=yes OLD_PO_FILE_OUTPUT=yes msgmerge
+
+.SUFFIXES:
+.SUFFIXES: .po .mo .pot
+.PHONY: all install uninstall check clean distclean $(LANGUAGES)
+
+.po.mo:
+	$(MSGFMT) -o $@ $<
+
+all: $(MOFILES)
+
+install: $(MOFILES)
+	@$(MAKE) check
+	for lang in $(LANGUAGES); do \
+	  dir=$(LOCALEDIR)/$$lang/; \
+	  if test ! -x "$$dir"; then \
+	    mkdir $$dir; chmod 755 $$dir; \
+	  fi; \
+	  dir=$(LOCALEDIR)/$$lang/LC_MESSAGES; \
+	  if test ! -x "$$dir"; then \
+	    mkdir $$dir; chmod 755 $$dir; \
+	  fi; \
+	  if test -r $$lang.mo; then \
+	    $(INSTALL_DATA) $$lang.mo $$dir/$(PACKAGE).mo; \
+	    chmod $(FILEMOD) $$dir/$(PACKAGE).mo; \
+	  fi; \
+	done
+
+uninstall:
+	@$(MAKE) check
+	for cat in $(MOFILES); do \
+	  cat=`basename $$cat`; \
+	  lang=`echo $$cat | sed 's/\$(CATOBJEXT)$$//'`; \
+	  rm -f $(LOCALEDIR)/$$lang/LC_MESSAGES/$(PACKAGE).mo; \
+	done
+
+converted: ja.sjis.mo cs.cp1250.mo pl.cp1250.mo sk.cp1250.mo zh_CN.cp936.mo \
+		ru.cp1251.mo
+
+# Convert ja.po to create ja.sjis.po.  Requires doubling backslashes in the
+# second byte.  Don't depend on sjiscorr, it should only be compiled when
+# ja.sjis.po is outdated.
+ja.sjis.po: ja.po
+	@$(MAKE) sjiscorr
+	rm -f ja.sjis.po
+	iconv -f euc-jp -t cp932 ja.po | ./sjiscorr > ja.sjis.po
+
+sjiscorr: sjiscorr.c
+	$(CC) -o sjiscorr sjiscorr.c
+
+# Convert cs.po to create cs.cp1250.po.
+cs.cp1250.po: cs.po
+	rm -f cs.cp1250.po
+	iconv -f iso-8859-2 -t cp1250 cs.po | \
+		sed -e 's/charset=ISO-8859-2/charset=cp1250/' -e 's/# Original translations/# Generated from cs.po, DO NOT EDIT/' > cs.cp1250.po
+
+# Convert pl.po to create pl.cp1250.po.
+pl.cp1250.po: pl.po
+	rm -f pl.cp1250.po
+	iconv -f iso-8859-2 -t cp1250 pl.po | \
+		sed -e 's/charset=ISO-8859-2/charset=cp1250/' -e 's/# Original translations/# Generated from pl.po, DO NOT EDIT/' > pl.cp1250.po
+
+# Convert sk.po to create sk.cp1250.po.
+sk.cp1250.po: sk.po
+	rm -f sk.cp1250.po
+	iconv -f iso-8859-2 -t cp1250 sk.po | \
+		sed -e 's/charset=ISO-8859-2/charset=cp1250/' -e 's/# Original translations/# Generated from sk.po, DO NOT EDIT/' > sk.cp1250.po
+
+# Convert zh_CN.po to create zh_CN.cp936.po.
+# set 'charset' to gbk to avoid that msfmt generates a warning
+zh_CN.cp936.po: zh_CN.po
+	rm -f zh_CN.cp936.po
+	iconv -f gb2312 -t cp936 zh_CN.po | \
+		sed -e 's/charset=gb2312/charset=gbk/' -e 's/# Original translations/# Generated from zh_CN.po, DO NOT EDIT/' > zh_CN.cp936.po
+
+# Convert ru.po to create ru.cp1251.po.
+ru.cp1251.po: ru.po
+	rm -f ru.cp1251.po
+	iconv -f koi8-r -t cp1251 ru.po | \
+		sed -e 's/charset=koi8-r/charset=cp1251/' -e 's/# Original translations/# Generated from ru.po, DO NOT EDIT/' > ru.cp1251.po
+
+check:
+	@if test "x" = "x$(prefix)"; then \
+	  echo "******************************************"; \
+	  echo "  please use make from the src directory  "; \
+	  echo "******************************************"; \
+	  exit 1; \
+	fi
+
+clean:
+	rm -f core core.* *.old.po *.mo *.pot sjiscorr
+
+distclean: clean
+
+#
+# NOTE: If you get an error for gvimext.cpp not found, you need to unpack the
+# extra archive.
+#
+$(PACKAGE).pot: ../*.c ../if_perl.xs ../GvimExt/gvimext.cpp ../globals.h
+	cd ..; $(XGETTEXT) --default-domain=$(PACKAGE) \
+		--add-comments --keyword=_ --keyword=N_ \
+		*.c if_perl.xs GvimExt/gvimext.cpp globals.h
+	mv -f ../$(PACKAGE).po $(PACKAGE).pot
+
+# Don't add a dependency here, we only want to update the .po files manually
+$(LANGUAGES):
+	@$(MAKE) $(PACKAGE).pot
+	if test ! -f $@.po.orig; then cp $@.po $@.po.orig; fi
+	mv $@.po $@.po.old
+	if $(MSGMERGE) $@.po.old $(PACKAGE).pot -o $@.po; then \
+	    rm -f $@.po.old; \
+	else \
+	    echo "msgmerge for $@.po failed!"; mv $@.po.old $@.po; \
+	fi
diff --git a/src/po/README.txt b/src/po/README.txt
new file mode 100644
index 0000000000..b023ef3648
--- /dev/null
+++ b/src/po/README.txt
@@ -0,0 +1,104 @@
+TRANSLATING VIM MESSAGES
+
+In this directory you will find xx.po files, where "xx" is a language code.
+Each file contains the translation of English Vim messages for one language.
+The files are in "po" format, used by the gettext package.  Please refer to
+the gettext documentation for more information.
+
+The GNU gettext library, starting with version 0.10.37, supports converting
+messages from one encoding to another.  This requires that it was compiled
+with HAVE_ICONV.  The result is that the messages may be in any encoding
+supported by iconv and will be automatically converted to the currently used
+encoding.
+
+The GNU gettext library, starting with version 0.10.36, uses a new format for
+some encodings.  This folows the C99 standard for strings.  It means that when
+a multi-byte character includes the 0x5c byte, this is not recognized as a
+backslash.  Since this format is incompatible with Solaris, Vim uses the old
+format.  This is done by setting the OLD_PO_FILE_OUTPUT and OLD_PO_FILE_INPUT
+environment variables.  When you use the Makefile in this directory that will
+be done for you.  This does NOT work with gettext 0.10.36.  Don't use it, get
+0.10.37.
+
+
+ON MS-WINDOWS
+
+The distributed files are generated on Unix, but this should also be possible
+on MS-Windows.  Download the gettext packages, for example from:
+
+	http://sourceforge.net/projects/gettext
+
+You might have to do the commands manually.  Example:
+
+   cd c:\vim\vim60
+   mkdir runtime\lang\ja\LC_MESSAGES
+   msgfmt -o runtime\lang\ja\LC_MESSAGES\vim.mo src\po\ja.po
+
+
+WHEN THERE IS A MISTAKE
+
+If you find there is a mistake in one of the translations, please report this
+to the maintainer of the translation.  His/her E-mail address is in the
+comments at the start of the file.  You can also see this with the ":messages"
+command in Vim when the translation is being used.
+
+
+CREATING A NEW PO FILE
+
+We will use "xx.po" as an example here, replace "xx" with the name of your
+language.
+
+- Edit Makefile to add xx to LANGUAGES and xx.mo to MOFILES.
+- Copy the header of an existing file, e.g., de.po, to xx.po.  Do not copy any
+  of the translated messages, delete everything after the "msgstr".
+- The remaining work is like updating, see the next section.
+
+
+UPDATING A PO FILE
+
+If you are the maintainer of a .po file, this is how you update the file.  We
+will use "xx.po" as an example here, replace "xx" with the name of your
+language.
+
+(1) Add new and changed messages from the Vim sources:
+
+	make xx
+
+    This will extract all the strings from Vim and merge them in with the
+    existing translations.  Requires the GNU gettext utilities.  Also requires
+    unpacking the extra archive.
+    Your original xx.po file will be copied to xx.po.orig
+
+    -- After you do this, you MUST do the next three steps! --
+
+(2) Translate
+    See the gettext documentation on how to do this.  You can also find
+    examples in the other po files.
+    Search the po file for items that require translation:
+
+	/fuzzy\|^msgstr ""\(\n"\)\@!
+
+    Remove the "#, fuzzy" line after adding the translation.
+
+    There is one special message:
+	msgid "Messages maintainer: Bram Moolenaar <Bram@vim.org>"
+    You should include your name and E-mail address instead, for example:
+	msgstr "Berichten übersetzt bei: John Doe <john@doe.org>"
+
+(3) Clean up
+    This is very important to make sure the translation works on all systems.
+    Comment-out all non-translated strings.  There are two types:
+    - items marked with "#, fuzzy"
+    - items with an empty msgstr
+    You can do this with the cleanup.vim script:
+
+	:source cleanup.vim
+
+    Background: on Solaris an empty msgstr results in an empty message; GNU
+    gettext ignores empty strings and items marked with "#, fuzzy".
+
+(4) Check:
+
+	make xx.mo
+
+    Look out for syntax errors and fix them.
diff --git a/src/po/README_mingw.txt b/src/po/README_mingw.txt
new file mode 100644
index 0000000000..7ba98e6078
--- /dev/null
+++ b/src/po/README_mingw.txt
@@ -0,0 +1,101 @@
+TRANSLATING VIM MESSAGES
+
+This file explains how to create and maintain po files using
+gnu-gettext.win32, a MINGW32 Windows port of gettext by Franco Bez
+<franco.bez@gmx.de>.  You can find it at:
+
+	http://home.a-city.de/franco.bez/gettext/gettext_win32_en.html
+
+First read the README.txt file for the general remarks
+
+
+The file that does the work is Make_ming.mak in the po directory. It is an
+adaptation of the Unix Makefile, but it does NOT test the presence of any po,
+pot, or mo files, so use it at your own risk but with care: it could even kill
+your canary. It has been tested by me several times (and with different
+languages) with success.
+
+The make utility must be run from the po directory.
+
+First of all you must set the enviroment variable LANGUAGE to xx, where xx is
+the name of your language. You can do it from the command line or adding a
+line to your autoexec.bat file: set LANGUAGE=xx. You must also add your
+language to the Make_ming.mak file in the lines LANGUAGES, MOFILES, AND
+POFILES.
+
+If you don't have a xx.po file, you must create it with the command:
+
+	make -f Make_ming.mak first_time
+
+This will produce a new brand xx.po file with all the messages in Vim ready
+for translation. Then you must source the cleanup.vim script from inside Vim;
+it will comment the untranslated messages (now, all). I recommend to use
+syntax highlighting so you can identify the untranslated messages easily.
+You also must remove the '..\' that prepends the name of the source files.
+(I don't no why, but make is unable to change the directory from po to src and
+back to po, so all the work must be done from the po dir, hence the '..\')
+
+Then you must go step (2) below.
+
+If you are updating a po file you must follow the next steps (they are nearly
+the same as in the Unix case, only the commands change):
+
+(1) Add new and changed messages from the Vim sources:
+
+	make -f Make_ming.mak xx
+
+    This will extract all the strings from Vim and merge them in with the
+    existing translations.  Requires the GNU gettext utilities.  Also requires
+    unpacking the extra archive.
+    Your original xx.po file will be copied to xx.po.orig
+
+    -- After you do this, you MUST do the next three steps! --
+
+(2) Translate
+    See the gettext documentation on how to do this.  You can also find
+    examples in the other po files.
+    Search the po file for items that require translation:
+	/\#\~   and also the fuzzy translations, /\#, fuzzy
+    Remove "#~" and "#, fuzzy" after adding the translation.
+
+    There is one special message:
+	msgid "Messages maintainer: Bram Moolenaar <Bram@vim.org>"
+    You should include your name and E-mail address instead, for example:
+	msgstr "Berichten übersetzt bei: John Doe <john@doe.org>"
+
+(3) Clean up
+    This is very important to make sure the translation works on all systems.
+    Comment-out all non-translated strings.  There are two types:
+    - items marked with "#, fuzzy"
+    - items with an empty msgstr
+    You can do this with the cleanup.vim script:
+
+	:source cleanup.vim
+
+(4) Check:
+
+	make -f Make_ming.mak xx.mo
+
+    Look out for syntax errors and fix them.
+
+(5) This is an extra step, ;-). If you want the vim.mo file installed in your
+    system you must run:
+
+	make -f Make_ming.mak install
+
+    This will create the xx\LC_MESSAGES directory (if it does not exist) and
+    will copy vim.po to it.
+
+(6) Another extra step ;-)). The command:
+
+	make -f Make_ming.mak clean
+
+    will delete the temp files created during the process.
+
+Suggestions will be welcomed.
+
+Eduardo F. Amatria <eferna1@platea.pntic.mec.es>
+
+Happy Vimming with NLS!!
+
+vim:tw=78:
diff --git a/src/po/README_mvc.txt b/src/po/README_mvc.txt
new file mode 100644
index 0000000000..cd107debf4
--- /dev/null
+++ b/src/po/README_mvc.txt
@@ -0,0 +1,94 @@
+TRANSLATING VIM MESSAGES
+
+This file explains how to create and maintain po files using
+gnu-gettext.win32, a Windows port of gettext by Franco Bez
+<franco.bez@gmx.de>.  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
+
+The LANGUAGE environment variable can be set from the command line, by adding
+a line to your autoexec.bat file, or by defining a user variable from the
+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
+
+When creating a new translation you must add your language code to the
+Make_mvc.mak file in the lines defining LANGUAGES and MOFILES.  To create the
+initial .po file for your language you must use the command:
+
+	make -f make_mvc.mak first_time
+
+Note: You need to be in the po directory when using this makefile.
+
+Once you have your new .po file load it into Vim and source cleanup.vim, this
+will convert untranslated messages to comments.  If you have syntax
+highlighting turned on then untranslated messages will stand out more easily.
+
+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
+
+
+UPDATING A TRANSLATION
+
+If there are new or changed messages in Vim that need translating, then the
+first thing to do is merge them into the existing translations.  This is done
+with the following command:
+
+	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.
+
+
+DOING THE TRANSLATION
+
+Now that you have a .po file you can do the translations for all messages that
+need it.  See README.txt for specific instructions.
+
+Once you have finished translating the messages you should make sure all
+non-translated strings are commented out.  This can be done by sourcing
+cleanup.vim once again.
+
+
+CHECKING THE TRANSLATION
+
+Check the translation with the following command:
+
+	nmake -f make_mvc.mak xx.mo
+
+Correct any syntax errors reported.  When there are no more errors, the
+translation is ready to be installed.
+
+
+INSTALLING THE TRANSLATION
+
+Install your translation with the following command:
+
+	nmake -f make_mvc.mak install
+
+This will create the xx\LC_MESSAGES directory in runtime\lang if it does not
+already exist.
+
+
+vim:tw=78:
diff --git a/src/po/af.po b/src/po/af.po
new file mode 100644
index 0000000000..3828481f1f
--- /dev/null
+++ b/src/po/af.po
@@ -0,0 +1,6244 @@
+# Afrikaans translation for Vim
+# Do ":help uganda"  in Vim to read copying and usage conditions.
+# Do ":help credits" in Vim to see a list of people who contributed.
+# Danie Roux <droux@tuks.co.za>, 2001
+# Edited: Jean Jordaan (njj) <jean@upfrontsystems.co.za>, 10/01/2001
+# Edited by Danie on 10/31/2001
+#
+# njj: Save == Stoor. Write == Skryf.
+# njj: "deleted" == "geskrap"; "remove" == "verwyder"
+# njj: "source" == "uitvoer", want "sourced" lêers word uitgevoer
+# njj: "abort" == "staak"
+# close == sluit
+# Onseker:
+# X Display - vertoonskerm? (njj: ek dink dis reg.)
+# open vim in another GTK Widget - het vertaal as element (njj: OK, maar
+# 'n element is algemener as 'n widget: mens kry byvoorbeeld HTML
+# en XML elemente. Maar ek kan nie nou aan 'n spesifieker woord dink
+# nie.)
+# Printing aborted - drukkery gestaak? (njj: ek dink dis reg.)
+
+msgid ""
+msgstr ""
+"Project-Id-Version: Vim 6.0\n"
+"POT-Creation-Date: 2001-10-31 12:43+0200\n"
+"PO-Revision-Date: Wed Oct 31 13:41 SAST 2001\n"
+"Last-Translator: Danie Roux <droux@tuks.co.za>\n"
+"Language-Team: Danie Roux <droux@tuks.co.za>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=ISO_8859-1\n"
+"Content-Transfer-Encoding: 8-bit\n"
+
+#: buffer.c:97
+msgid "E82: Cannot allocate any buffer, exiting..."
+msgstr "E82: Kan nie buffer toeken nie, program sluit..."
+
+#: buffer.c:100
+msgid "E83: Cannot allocate buffer, using other one..."
+msgstr "E83: Kan nie buffer toeken nie, gaan ander een gebruik..."
+
+#: buffer.c:698
+msgid "No buffers were unloaded"
+msgstr "Geen buffers is uitgelaai nie"
+
+#: buffer.c:700
+msgid "No buffers were deleted"
+msgstr "Geen buffers is geskrap nie"
+
+#: buffer.c:702
+msgid "No buffers were wiped out"
+msgstr "Geen buffers is geskrap nie"
+
+#: buffer.c:710
+msgid "1 buffer unloaded"
+msgstr "1 buffer uitgelaai"
+
+#: buffer.c:712
+#, c-format
+msgid "%d buffers unloaded"
+msgstr "%d buffers uitgelaai"
+
+#: buffer.c:717
+msgid "1 buffer deleted"
+msgstr "1 buffer geskrap"
+
+#: buffer.c:719
+#, c-format
+msgid "%d buffers deleted"
+msgstr "%d buffers geskrap"
+
+#: buffer.c:724
+msgid "1 buffer wiped out"
+msgstr "1 buffer geskrap"
+
+#: buffer.c:726
+#, c-format
+msgid "%d buffers wiped out"
+msgstr "%d buffers geskrap"
+
+#: buffer.c:783
+msgid "E84: No modified buffer found"
+msgstr "E84: Geen veranderde buffer gevind nie"
+
+#. back where we started, didn't find anything.
+#: buffer.c:822
+msgid "E85: There is no listed buffer"
+msgstr "E85: Daar is geen gelyste buffer nie"
+
+#: buffer.c:834
+#, c-format
+msgid "E86: Cannot go to buffer %ld"
+msgstr "E86: Kan nie na buffer %ld gaan nie"
+
+#: buffer.c:837
+msgid "E87: Cannot go beyond last buffer"
+msgstr "E87: Kan nie verby laaste buffer gaan nie"
+
+#: buffer.c:839
+msgid "E88: Cannot go before first buffer"
+msgstr "E88: Kan nie vóór eerste buffer gaan nie"
+
+#: buffer.c:863
+#, c-format
+msgid "E89: No write since last change for buffer %ld (use ! to override)"
+msgstr ""
+"E89: Buffer %ld nog ongestoor sedert vorige wysiging (gebruik ! om te dwing)"
+
+#: buffer.c:879
+msgid "E90: Cannot unload last buffer"
+msgstr "E90: Kan nie laaste buffer uitlaai nie"
+
+#: buffer.c:1314
+msgid "W14: Warning: List of file names overflow"
+msgstr "W14: Waarskuwing: Lêerlys loop oor"
+
+#: buffer.c:1480
+#, c-format
+msgid "E92: Buffer %ld not found"
+msgstr "E92: buffer %ld kon nie gevind word nie"
+
+#: buffer.c:1700
+#, c-format
+msgid "E93: More than one match for %s"
+msgstr "E93: Meer as een treffer vir %s"
+
+#: buffer.c:1702
+#, c-format
+msgid "E94: No matching buffer for %s"
+msgstr "E94: Geen buffer wat by %s pas nie"
+
+#: buffer.c:2105 ex_docmd.c:6065
+#, c-format
+msgid "line %ld"
+msgstr "reël %ld"
+
+#: buffer.c:2188
+msgid "E95: Buffer with this name already exists"
+msgstr "E95: Buffer met hierdie naam bestaan alreeds"
+
+#: buffer.c:2481
+msgid " [Modified]"
+msgstr " [Gewysig]"
+
+#: buffer.c:2486
+msgid "[Not edited]"
+msgstr "[Ongewysig]"
+
+#: buffer.c:2491
+msgid "[New file]"
+msgstr "[Nuwe lêer]"
+
+#: buffer.c:2492
+msgid "[Read errors]"
+msgstr "[Leesfoute]"
+
+#: buffer.c:2494 fileio.c:1754
+msgid "[readonly]"
+msgstr "[lees alleen]"
+
+#: buffer.c:2510
+#, c-format
+msgid "1 line --%d%%--"
+msgstr "1 reël --%d%%--"
+
+#: buffer.c:2510
+#, c-format
+msgid "%ld lines --%d%%--"
+msgstr "%ld reëls --%d%%--"
+
+#: buffer.c:2518
+#, c-format
+msgid "line %ld of %ld --%d%%-- col "
+msgstr "reël %ld van %ld --%d%%-- kolom "
+
+#: buffer.c:2606
+msgid "[No file]"
+msgstr "[Geen lêer]"
+
+#. must be a help buffer
+#: buffer.c:2646
+msgid "help"
+msgstr "help"
+
+#: buffer.c:3151 screen.c:4671
+msgid "[help]"
+msgstr "[help]"
+
+#: buffer.c:3183 screen.c:4677
+msgid "[Preview]"
+msgstr "[Voorskou]"
+
+#: buffer.c:3389
+msgid "All"
+msgstr "Alles"
+
+#: buffer.c:3389
+msgid "Bot"
+msgstr "Ond"
+
+#: buffer.c:3391
+msgid "Top"
+msgstr "Bo"
+
+#: buffer.c:4127
+msgid ""
+"\n"
+"# Buffer list:\n"
+msgstr ""
+"\n"
+"# Buffer lys:\n"
+
+#: buffer.c:4160
+msgid "[Error List]"
+msgstr "[Foutlys]"
+
+#: buffer.c:4173 memline.c:1513
+msgid "[No File]"
+msgstr "[Geen lêer]"
+
+#: buffer.c:4393
+msgid ""
+"\n"
+"--- Signs ---"
+msgstr ""
+"\n"
+"--- Tekens ---"
+
+#: buffer.c:4403
+#, c-format
+msgid "Signs for %s:"
+msgstr "Tekens vir %s:"
+
+#: buffer.c:4409
+#, c-format
+msgid "    line=%ld  id=%d  name=%s"
+msgstr "    reël=%ld  id=%d  naam=%s"
+
+#: diff.c:133
+#, c-format
+msgid "E96: Can not diff more than %ld buffers"
+msgstr "E96: Kan nie meer as %ld buffers 'diff' nie"
+
+#: diff.c:648
+msgid "E97: Cannot create diffs"
+msgstr "E97: Kan nie 'diffs' skep nie "
+
+#: diff.c:747
+msgid "Patch file"
+msgstr "Laslap lêer"
+
+#: diff.c:991
+msgid "E98: Cannot read diff output"
+msgstr "E98: Kan nie 'diff' afvoer lees nie"
+
+#: diff.c:1704
+msgid "E99: Current buffer is not in diff mode"
+msgstr "E99: Huidige buffer is nie in 'diff' modus nie"
+
+#: diff.c:1716
+msgid "E100: No other buffer in diff mode"
+msgstr "E100: Geen ander buffer in 'diff' modus nie"
+
+#: diff.c:1724
+msgid "E101: More than two buffers in diff mode, don't know which one to use"
+msgstr ""
+"E101: Meer as twee buffers in 'diff' modus, weet nie watter een om te "
+"gebruik nie"
+
+#: diff.c:1747
+#, c-format
+msgid "E102: Can't find buffer \"%s\""
+msgstr "E102: Kan buffer %s nie vind nie"
+
+#: diff.c:1753
+#, c-format
+msgid "E103: Buffer \"%s\" is not in diff mode"
+msgstr "E103: Buffer \"%s\" is nie in 'diff' modus nie"
+
+#: digraph.c:2168
+msgid "E104: Escape not allowed in digraph"
+msgstr "E104: 'Escape' nie toegelaat in digraaf nie"
+
+#: digraph.c:2340
+msgid "Keymap file not found"
+msgstr "Sleutelbindinglêer nie gevind nie"
+
+#: digraph.c:2367
+msgid "E105: Using :loadkeymap not in a sourced file"
+msgstr "E105: :loadkeymap word buite 'n uitvoerlêer