Am 13.10.2011 17:27, schrieb Cédric Krier:
So it's hard to acquirer volunteers who translate content on the
website. This should be more simple - without knowing how to
implement an other solution. In our CMS we have choosen this way: a
text without a marker is general (or untranslated), if there is a
translation fitting the browser language the system choose this
(like content negotiation). But this ist technical stuff again ;)
The po way is pretty comment and it works.
I don't understand your explaination.
I meant something similar to this:
http://httpd.apache.org/docs/2.0/content-negotiation.html
We chosed a way like this in our CMS (implemented a bit different) and
are using the po only for common sentences in the backend and some
frequently used widgets.
We have chosen this way, because its more easy for a translator if he
has the whole context in mind and right before his eyes. This only as a
explanation for what I meant.
--
[email protected] mailing list
