changeset 914:980b83d9b823

i18n: updated README and CHANGES
author Thomas Waldmann <tw AT waldmann-edv DOT de>
date Sat, 08 Jul 2006 10:54:23 +0200
parents b7a4a59b4f41
children f3f38ecf4cf3
files MoinMoin/i18n/README docs/CHANGES
diffstat 2 files changed, 25 insertions(+), 18 deletions(-) [+]
line wrap: on
line diff
--- a/MoinMoin/i18n/README	Sat Jul 08 10:14:21 2006 +0200
+++ b/MoinMoin/i18n/README	Sat Jul 08 10:54:23 2006 +0200
@@ -1,27 +1,33 @@
 Translators and Developers,
-The data flow for i18n stuff has completely changed, so please read this.
 Translators need to deal with the *.po files ONLY - they should do this on<language-code>, please do not
 send po updates via email, the stuff from the moinmaster wiki gets processed
-In moin 1.3 we switched the i18n system to use wiki markup instead html - you
-should change the header of your *.po file after adapting to wiki markup,
-see de.po for a sample.
-Encoding: please use utf-8 ONLY for the po file you submit.
+The i18n system uses wiki markup in the msgid/msgstr strings, see also the
+the header of your *.po file (and see see de.po for a sample).
-If you don't like to edit using utf-8, see the section below about non-utf-8
-For using the i18n build system, one needs to have "gettext" (e.g. from Debian
-unstable) installed. For simply translating text, you do not need it, you can
-use a text editor.
+Encoding is utf-8 ONLY for the po file (the wiki page automatically uses
 Please search your translation for fuzzy and untranslated strings. If you
-have reviewed the fuzzy stuff, remove the "fuzzy" marker.
+have reviewed the fuzzy stuff, remove the "fuzzy" marker. If you do that
+online on the moinmaster wiki, here are some tips:
+ * If you look at MoinMaster:MoinI18n/cc (where cc is your language code),
+   you will see some statistics at the top, you should try to have no untrans-
+   lated strings and also no fuzzy strings.
+ * On normal page view of that page, untranslated stuff is marked with !!!
+   (3 exclamation marks, just use firefox Ctrl-f to find them). Just remember
+   the untranslated phrase (or at least some  non-common words in it).
+ * Now edit the page and use Ctrl-f again. Enter the words you remembered.
+   Then use the highlight function right of the search box to make those words
+   highlighted in yellow color and scroll through the text in the edit box to
+   find the yellow stuff (the search function without highlight won't help you).
+ * For finding fuzzy stuff, just use the same method with "fuzzy".
+For using the i18n build system, one needs to have "gettext" installed.
 In the source code, there is original english text marked with
 _("english string") - xgettext can extract these strings automatically from
@@ -38,14 +44,14 @@
 Makefile: a GNU-Makefile a list of files with translatable strings a list of files with translatable strings (automatically created
+             by "make POTFILES"). POTFILES is about the same thing, just in a
+             format suitable for inclusion into the Makefile.
 MoinMoin.pot: Master translation file.
 *.po: Translations (utf-8 encoding)
-mo/*.mo: Binary output files of msgfmt (this is the stuff moin reads at runtime).
 New Translation (no .po file exists yet)
@@ -66,7 +72,6 @@
 - run "make <langcode>.po"
 - change the translation
 - update the PO-Revision-Date and Last-Translator entries
-- run "make <langcode>.mo"
 Change of translatable strings
--- a/docs/CHANGES	Sat Jul 08 10:14:21 2006 +0200
+++ b/docs/CHANGES	Sat Jul 08 10:54:23 2006 +0200
@@ -159,6 +159,8 @@
     * @SIG@ etc. generate local time stamps now, no difference visible on page
     * Speeded up linkto search by avoiding read locks on the pagelinks file.
+    * The i18n system no loads *.po files directly (no *.py or *.mo any more)
+      and caches the results (farm wide cache/i18n/*).
     * on action "info" page, "revert" link will not be displayed for empty page