Hi Gaëtan! > Doesn't TurboGears include some translation framework?
Yes, but for in-line strings in templates/code. > Have you seen the "localized" patch > athttp://groups.google.com/group/sqlelixir/files? Thanks for the link, I'll get in touch with the author! > IMO, the translations for all entities should be stored in a single > table and not in one table per translated entity. The difference with > the versioned plugin is that for versioning, you don't know in advance > the type of columns, whereas in a translation framework, you do know > those are going to be strings. We are translating not strings, but entities. Keeping the strings in one table makes it difficult to 1) construct the translated entity 2) keep in mind the context of a translated string. My approach will return the default entity if there's no translation of the whole entity in required language. > You might want to cache the "base" instance when accessing one > "ignored" attribute on the translated version, because in your current > code you'll trigger a query for each attribute. How do I accomplish this? > Also, you could remove all the code related to "revert" as it's > probably useless. Yes, the code needs lots of cleanup/refactoring ;-) -- Sergei --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SQLElixir" 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/sqlelixir?hl=en -~----------~----~----~----~------~----~------~--~---
