Re: Templates & Languages
| From: | Mehdi Achour | Date: | Sat, 16 Oct 2004 16:43:19 +0000 |
| Subject: | Re: Templates & Languages | ||
| References: | 1 2 3 4 | Groups: | php.doc.web |
| Request: | Send a blank email to doc-web+get-350@lists.php.net to get a copy of this message | ||
Vincent Gevers wrote:
On Wednesday 29 September 2004 05:31, Curt Zirzow wrote:I'm +1 for gettext (if my voice still count). Using PHP and gettext sounds easier for the translators then editing PHP files. All you need is the gettext package (version > 0.12.1). Translators would simply use the POedit tool (http://poedit.sf.net) and sends updated docweb.po files. Using a templating system for translations seems like reinventing the wheel imho. I'd be able and happy to help with its integration if it's chosen, I'm quiet familiar with it. Regards, Mehdi* Thus wrote Sean Coates:I'm not sure about gettext.. It will require a howto for the utils to make it work. The translation teams are used to replace english with there own language. even a simple str_replace() will work.Vincent Gevers wrote: | For some reason I'm not sure about adding all html in the templates. | | If we want the pages to be translated we should allow the doc teams to | create/edit them. This means they can also edit the html code or even break | the site. [...] | Comments welcome Well, in my experience, it's often not as simple as replacing pieces of text, when translating sites.I'm not entire familiar with the code on docweb yet, but what would the option of using a gettext approach? And go with the a more traditional locale method?