Hi Iain, > I would imagine two types of i18n aware applications: > > Applications in a single language, not being able to switch between > languages, but do use some of the i18n features. And fully fledged > applications that support multiple languages.
I think, most applications which only use one language won't use I18n#translate at all, except if they already prepare to support multiple languages in future. > Besides these I think one might separate between 'backend-independent' > and SimpleBackend dependent plugins. Yes, on the one hand that'd be nice, on the other hand that'd produce two plugins instead of one, and my initial intention was to have a single plugin that provides a bunch of useful stuff for people to start with (like you could formerly install ruby-gettext, put one or two lines into your app and it simply worked using the defaults). regards, Andreas Neuhaus http://zargony.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "rails-i18n" 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/rails-i18n?hl=en -~----------~----~----~----~------~----~------~--~---
