# HG changeset patch
# User zas_
# Date 1262730363 0
# Node ID 357666e13b48c56c24ed53549d817b65d6c97bb4
# Parent  d8e9d0cc640e6305b43459dd87472f0b9e51873a
Update README about translations.

diff -r d8e9d0cc640e -r 357666e13b48 po/README
--- a/po/README	Tue Jan 05 17:49:50 2010 +0000
+++ b/po/README	Tue Jan 05 22:26:03 2010 +0000
@@ -1,11 +1,16 @@
 Translators create a translation by creating the appropriate .po file in the /po
-directory. Please see the gettext info pages for an overview and instructions.
-Basically: Add your language code to the   ALL_LINGUAS=   line in configure.in,
-then get started translating the strings in your ??.po file. Note: The strings
-for debug output is intentionally not marked for translation.
+directory.
+
+Please see the gettext info pages for an overview and instructions.
 
-To update a specific translation, one may use intltool-update [lang]  (ie. 
-intltool-update fr).
+Basically:
+- Add your language code to the LINGUAS file
+- then get started translating the strings in your ??.po file.
+
+Note: The strings for debug output is intentionally not marked for translation.
+
+To update a specific translation:
+- intltool-update [lang] (ie. intltool-update fr).
 
 To update all translation files, use make update-po. You should only use it when
 needed (before a release or when there were many changes in source code).