Hello list,
I just wondered what you guys would consider as best practice if you had, for example, a bunch of more or less static views and had to provide translate functionality. Some of these views can be very - let's say - special, as they contain lots of markup and dissecting them and using the translate view helper and, for example, gettext, would be a real pain (as in PITA). I figured that one option would be to handle this as the action context helper handled it in ZF1: if for exampleAction() the json context was registered, the example.json.phtml view was rendered. As I read in one of Matthew's posts, though, it has been considered hackish (and that's why I guess the different view renderer strategies have been introduced), and that's why I'm wondering whether it would be just as hackish to render example.en.phtml for an exampleAction() if the currently selected locale's language was English and example.de.phtml if it was German. I'm curious to hear how you would handle this, especially if you haven't hooked up with a CMS as a content provider yet. This is a suggestion I have heard: use WordPress or another blog software to manage content, and then pull it into your layout using a service that does just that. Best regards, Andreas -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
