On Tue, Jun 7, 2011 at 16:59, Yuri Chornoivan <[email protected]> wrote: > It can be done through po4a. Some website.config like this: > > [po4a_paths] po/website.pot > [type: xml] index.php > [type: xml] locale.php > [type: xml] for_you.php > [type: xml] release.php > > then > > po4a website.config > > then connect Tx.net to website.pot, translate, import, and (e.g. for > Ukrainian) > > for i in *.php > do > po4a-translate -f xml -m $i -M utf-8 -p po/uk.po -l uk/${i%.*}-uk.php > done
Interesting, thanks. > Is this the realistic way? We will see, it really depends on the type of the document: - large HTML document: full HTML edition is better (see our initial announce, what we will get to with annual reports, and how the blog is managed for instance) - mix of a document and small apps: gettext//lang file/array-like is better, with a twist (everything may not fall into the same module) - full apps: gettext/lang file/array-like is better but depending on how a page is built, its contents may be split into several modules. In the end, we'll need something that can manage several types of resources (from purely static documents, through partials/widgets, to pure apps). Romain
