UI translations - Order to chaos

For MidCOM 3 the work of implementing gettext support is almost done. Most of the translation requests come from TAL templating. Some may come directly from the PHP - code and that requires some nice i18n API function.

A quick bus trip thinking about the flow of the translation spawned a requirement of a new helper component for MidCOM 3 that is midcom.helper.translator. If fact it's functionality is quite simple. It provides three key functionalities

1. Collector that goes through every component's all PHP and TAL files and looks for certain function calls. It also reads translations that are already made. Then it writes the results to database in order to provide easier access for the translation UI itself
2. The very UI for translations that makes it easy to browse and input translation entries. Especially strings that are not translated should be easily accessible
3. Exporter functionality is required for writing .po files to corresponding component's locales folder and running msgfmt command to that translation file in order to generate the gettext binary

This should provide nice Web based UI for translations management. Of course when doing things in right way this functionality can also be exposed via Neutron, WebDAV, Samba or other coming possible UI - interfaces