On Tue, Sep 7, 2010 at 6:54 AM, Peter De Berdt <peter.de.be...@pandora.be> wrote:
> I'd like to know if anyone here is using a UI plugin/gem ( not unlike > django-rosetta on django ) to deal with multiple translators, some of > them unwilling or unable to mess with 100+ files in a repository, > working on language data. > > This seems to fit the bill: http://github.com/newsdesk/translate > I haven't used it yet though. Maybe someone else can share their experiences > or you can just try it out (doesn't look like that much work to implement > and just use a separate git branch to experiment on). > We're using a slightly modified version of it on the Kete application (http://github.com/kete/kete/ and our version of the plugin at http://github.com/kete/translate). It's good for a whole site's UI translation. We have some guides that we point our translators at here: http://kete.net.nz/documentation/topics/show/289-using-translate-plugin-to-translate-your-kete-installation http://kete.net.nz/documentation/topics/show/276-general-strategies-for-creating-a-localization-of-the-kete-ui-for-13 Note that we have added some other things so that one translation (say a common noun or verb in the UI) can be reused in other translations to make the process quicker for the "base" UI elements. You may also want to consider adding support for Right-to-Left languages (Arabic, Hebrew) in your CSS. See this branch for some commits that allow for that: http://github.com/kete/kete/tree/enhancement_285_add_non_left_to_right_layout_support Now, a thing to keep in mind is that this is only for the default "static" user interface text defined in your templates. It won't work with translating content (i.e. stuff that gets pulled from you database). Globalize2 is the longest running plugin for that sort of work. However with Kete, we found that the working assumptions weren't compatible with how we handling versioning of content so we decided to go our own way. We're working on a new gem called mongo_translatable (http://github.com/kete/mongo_translatable) that uses MongoDB as a backend for translation lookup. It's an engine and includes a built-in UI for translation that is centered around the piece of content being translated. It's basically done, but I need to bundle it up for release. Feel free to fork and contribute back to it. If you are writing an app that is going with MongoDB generally, you should check out the all MongoDB plugin for translation here: http://github.com/ahe/mongo_translation Cheers, Walter -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
