> I know that we want to add flexibility but when using databases > (especially mysql), the advantages are not little and i think we > should consider an internationalization system with db support. > > What do you think? > Thanks, Cristian
/signed Now I use both ways: - "system" strings like "Error", "Erreur", "Fehler" or "Ошибка" stored in .po files and used by __(). It easy to develope, but only specialist (me for example :) ) can change them. - "content" strings like "Description of photo in English", "Description de la photo en français", "Beschreibung des Fotos in deutscher Sprache" and "Описание фотографии на русском" stored in DB and used by my library. User (admin of site, not IT specialist) can change them in CMS, it easy. Sometime user want to change translation of system strings (some of them translated by Google Translate :-) ) and call me, but I don't like it. It would be good that he can change translation of system strings. Of course, I can change CMS for working with .po files too (not sure) or change my code for using DB only, but I think standard class of framework with transparent using both, db and .po files would be better for all :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
