Maybe we should look at hoboifying the internationalization... instead of doing a standard i18n implementation, make our own that takes the yaml file and defines a bunch of tags with tag names based on the hierarchy. The tags would pick up on the current locale settings and display appropriately.
Though multiple tags might get cluttered and confuse the name space... maybe a single tag with a target. Either way. >From what I've heard, there's a lot of english specific code in hobo and especially in rapid. On Aug 11, 7:55 am, Matt Jones <[email protected]> wrote: > This post got me thinking: > > http://robots.thoughtbot.com/post/160476423/international-clearance > > Has anybody on the list had much luck doing i18n with Hobo? The > thoughtbot post points out that, even if your app is English-only, > i18n allows all the strings used by a plugin to be configured in one > place. While most of that can be accomplished by overriding tags, > centralization could be nice too. > > Thoughts? > > --Matt Jones --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hobo 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/hobousers?hl=en -~----------~----~----~----~------~----~------~--~---
