kerinin schrieb: > I'm working on a project which requires information to be available in > multiple languages, but this information is provided by the users > (that is, it isn't part of the site design). How would I use i18n in > this case? I currently have a 'description' property, if i were to > create two properties (description_english and description_chinese), > could I associate these properties with the languages and have them > load based on the session data? Is there a 'correct' way to do this?
It depends on how you gather the i18n'zed texts. Are they static, or dynamic? If the former, I don't see why you can't send them a PO-file (or at least an excel-doc that you then need to convert to one). If they are dynamic, you might consider creating a widget that translates it's value based on the get_locale()-function of TG. Diez --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
