Re: New class in PEAR: Translation

Am Tue, 01 Oct 2002 13:30:44 +0200 schrieb Markus Wolff <wolff@21st.de>: > > The base should be something more abstract like "mail_error" and also it > > would make sense to group the texts into something like general and > > modul specific. So you can say $t->get('mail_error', 'contact'); > > ommitting 'contact' would mean you want the general translation. [...] > However, this is a behaviour that could be easily configured through > such a class as the database model can be almost the same for both > approaches. Thinking more about it, our approaches are more compatible than I thought... cause you can always store an abbreviation in "BASE" and set the DE,EN,FR,etc. columns to whatever you want. If you want module specific translations, add another column "module" that is only used if a second parameter is passed to get(). Piece of cake. Regards, Markus -- *21st Media* | Consulting, Konzeption, Produktion für die Bereiche: Markus Wolff | Internet, Intranet, eCommerce, Content Management, Hamburg,Germany | Softwareentwicklung, 3D-Animation, Videostreaming http://21st.de | Tel. [+49](0)40/6887949-0, Fax: [+49](0)40/6887949-1