This library does exactly what you're talking about here: 
https://github.com/fnando/i18n-js

It's a small library to provide the I18n translations on the Javascript. It 
comes with Rails support. 

It is for sure worth to take a look.

-- 
At.
Carlos Antonio


On Wednesday, April 4, 2012 at 5:05 PM, Ryan Bigg wrote:

> That's quite an interesting twist on it. I never thought of doing it that 
> way, but now it would make sense to be able to have these made available to 
> client-side applications which can then use them to translate... but what are 
> the translation libraries like on the client-side these days? 
> 
> On Wednesday, 4 April 2012 at 3:00 PM, Johnneylee Rollins wrote:
> 
> > This sounds like it could be more of a feature request than a complaint.
> > 
> > Compiling yaml files for translation (Or whatever store) down to maybe json 
> > for use might lend towards the more pro client-side views crowd. I haven't 
> > even thought out the implications of such a thing, but it might be really 
> > cool to do that. 
> > 
> > ~Johnneylee
> > 
> > On Wed, Apr 4, 2012 at 3:57 PM, Ryan Bigg <[email protected] 
> > (mailto:[email protected])> wrote:
> > > How are these files assets? They're not served to the end user, but are 
> > > rather used by the backend to display information in different languages 
> > > to the end-user, thereby making them configuration. 
> > > 
> > > On Wednesday, 4 April 2012 at 2:54 PM, Alexey wrote:
> > > 
> > > > Why in a standard rails application locales are in config directory
> > > > and not in assets?
> > > > 
> > > > -- 
> > > > You received this message because you are subscribed to the Google 
> > > > Groups "Ruby on Rails: Core" group.
> > > > To post to this group, send email to [email protected] 
> > > > (mailto:[email protected]).
> > > > To unsubscribe from this group, send email to 
> > > > [email protected] 
> > > > (mailto:[email protected]).
> > > > For more options, visit this group at 
> > > > http://groups.google.com/group/rubyonrails-core?hl=en.
> > > > 
> > > > 
> > > > 
> > > 
> > > 
> > > -- 
> > > You received this message because you are subscribed to the Google Groups 
> > > "Ruby on Rails: Core" group.
> > > To post to this group, send email to [email protected] 
> > > (mailto:[email protected]).
> > > To unsubscribe from this group, send email to 
> > > [email protected] 
> > > (mailto:rubyonrails-core%[email protected]).
> > > For more options, visit this group at 
> > > http://groups.google.com/group/rubyonrails-core?hl=en.
> > 
> > -- 
> > You received this message because you are subscribed to the Google Groups 
> > "Ruby on Rails: Core" group.
> > To post to this group, send email to [email protected] 
> > (mailto:[email protected]).
> > To unsubscribe from this group, send email to 
> > [email protected] 
> > (mailto:[email protected]).
> > For more options, visit this group at 
> > http://groups.google.com/group/rubyonrails-core?hl=en.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby on Rails: Core" group.
> To post to this group, send email to [email protected] 
> (mailto:[email protected]).
> To unsubscribe from this group, send email to 
> [email protected] 
> (mailto:[email protected]).
> For more options, visit this group at 
> http://groups.google.com/group/rubyonrails-core?hl=en.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" 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/rubyonrails-core?hl=en.

Reply via email to