Xliff dictionaries are cached as php arrays, pretty hard to beat that. On Jan 31, 2011 12:23 AM, "Pau Peris" <[email protected]> wrote: > hi, to handle web page text content translation (i18n) on a web page > is it always recommended to use xliff dictionaries or ddbb storage? To > handle i18n on a web page i18n tables are used, but to handle page > content text translation depending on the client language shouldn't > ddbb storage be faster than xliff dictionaries? I'm thinking how to do > it but all the examples i can find use xliff dictionaries. > PD: I'm not asking for i18n ddbb storage but how to properly handle > web page text content translation on a wide site, i've read about > xliff dictionaries but i'm wondering if there is any better method. > > -- > If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com > > 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]<symfony-users%[email protected]> > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en
-- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com 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
