Quoting Frank Habermann (email@example.com): > one file for each translation. > So what is the best way to give translators the information for translation? I > could create a po file from the php-array. After translation i will transform > it back to a php-array. PO files make translators happy. Other translation methods make them sad (except XLIFF probably). So, well, if you can work on a model that builds your PHP stuff from the PO files at build time and refreshes the PO files from the PHP stuff, that'd be perfect. Maybe a po4a module ? PO4A wizards ?
Description: Digital signature