Changes between Version 11 and Version 12 of DynamicFieldsPlugin

Timestamp:

Sep 28, 2010, 6:21:17 PM (14 years ago)

Author:

Steffen Hoffmann

Comment:

corrected and hopefully clearified i18n-related explanations

DynamicFieldsPlugin

@@ -143 +143 @@
 Kindly provided by [[Image(http://sw.transifex.net/2/static/charts/images/tx-logo-micro.png, link=http://www.transifex.net/, title=the open translation platform, valign=bottom)]]
 
-Preparing the plugin from source requires the additional step of compiling message catalog files. This will be done automatically by invoking a suitable Babel install. Walk through:
+Preparing the plugin from source now requires the additional step of compiling message catalog files. As long as you stick to the message catalogs served with this plugin directly, there is still nothing special to be done. Just package your plugin from source the standard way:
+{{{
+cd dynamicfieldsplugin
+python ./setup.py bdist_egg
+}}} 
+and the proper helper function calls to a suitable Babel install will be issued automatically for you.
+
+Only if you encounter message catalogs with translations marked 'fuzzy', including them would require special treatment, since automatic compilation trashes them by default. Walk through:
 {{{
 cd dynamicfieldsplugin
 python ./setup.py compile_catalog -f
-python ./setup.py compile_catalog_js -f
 python ./setup.py bdist_egg
 }}} 
-Step 2 and 3 are almost obsolete, and only needed to include translations marked as `# fuzzy` by the translator, since
-the compilation before packaging will do message catalog compilation compile only without the extra `-f` argument.
-Again, for more details see the [t:wiki:CookBook/PluginL10N#Compileanduseit l10n cookbook page for Trac plugins].
+Again, this is almost obsolete, and only needed to include translations marked as `#, fuzzy` by the translator.
+For more details see the [t:wiki:CookBook/PluginL10N#Compileanduseit l10n cookbook page for Trac plugins].
 
 == Recent Changes ==