Thanks, that seems to be a nice and comprehensive approach. Actualy I am looking for something 'leaner' where I can build a customer specific dictionary file, with wich I can switch to customer terminology similar to the i18n mechanism. With other words: I dont want to build complete new template sets.
best wishes, Martin On 4/12/07, Andreas Hucks <[EMAIL PROTECTED]> wrote: > > > Take a look at the sfDimensionsPlugin: > > http://trac.symfony-project.com/trac/wiki/sfDimensionsPlugin > > Cheers, > Andreas > > > Martin Groh schrieb: > > Hi, > > > > on my site I come to a point, where I need translation in a more > > 'functional/operative' way rather than language translation. > > I'm thinking of different customers using the same site and content. > > Each of them has a different mindset and vocabulary describing the same > > things. So there is a different "customer language" although they all > > speak german or french or english. > > > > I really like the I18N concept of symfony but it wont help me here. (or > > would it?) > > Has anybody got an idea other than creating complete different template > > sets? > > Main issue is to "translate" the front end. Not the database content. > > > > Thanx a lot, > > Martin > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [EMAIL PROTECTED] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
