Hey everyone, Since I need to support user input in multiple languages in my current project, I felt the need to wrap things up in a plugin. It's still under development, but it's reasonably specced (100% coverage for whatever that means) and should be quite functional. I'd be glad about any suggestions how to make it useable in real life scenarios (I'll start integrating it in my app tomorrow, but my usecases may differ)
Get it at http://github.com/snusnu/dm-is-localizable/tree/master >From the README ... dm-is-localizable Datamapper support for localization of (user entered) content in multilanguage applications Schema * one xxx_translations table for every translatable resource * xxx_translations belongs_to the resource to translate * xxx_translations belongs_to a language * properties to be translated are defined in xxx_translations Advantages * Proper normalization and referential integrity * Ease in adding a new language (add row to xxx_translations) * Easy to query * Columns keep their names Disadvantages (not really if you think about it) * One table for every resource that needs translations Let me know what you think! Any kind of feedback is very welcome! cheers snusnu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
