Check the i18n docs here:
http://weblog.rubyonrails.org/2008/11/18/new-rails-2-2-i18n-defaults
http://api.rubyonrails.org/classes/I18n.html

You should be created a language file in your app folder, not in the Rails
gem folder. Then you just need to set the local in application.yml.


On Tue, Jan 20, 2009 at 2:04 AM, MW <[email protected]> wrote:

>
> Any help would be really great!
>
> Thank you!!!
>
> Matz
>
> On 19 Jan., 14:10, MW <[email protected]> wrote:
> > Hi Bruno,
> >
> > I am a little bit confused, if I create a de.yml file in ruby/gems/1.8/
> > gems/activerecord-2.2.2/lib/active_record/locale, where can I say
> > ActiveRecord "Ok, now do not load the en.yml file any longer, please
> > take the de.yml file with my german translatuions"...?
> > Or do I have to create the translations in the /lang/ui folder at my
> > app?
> >
> > THX a lot
> >
> > Matz
> >
> > On 16 Jan., 00:39, "Bruno Bornsztein" <[email protected]>
> > wrote:
> >
> > > PS - the Globalite plugin has many of these translations done already:
> >
> > >http://github.com/mattetti/globalite/tree/3525504a30645b6234361bc6c92.
> ..
> >
> > > and
> >
> > >http://github.com/mattetti/globalite/blob/3525504a30645b6234361bc6c92.
> ..
> >
> > > The yaml files are in a slightly different format though.
> >
> > > On Thu, Jan 15, 2009 at 5:37 PM, Bruno Bornsztein <
> >
> > > [email protected]> wrote:
> > > > Yeah, looks like the french localization file is far from complete.
> Those
> > > > error mean you're missing the localizations for ActiveRecord's
> default error
> > > > messages. As you can see here<
> http://github.com/rails/rails/tree/7a0e7c7270548138a333bc39aab5aec805...>,
> > > > Rails doesn't ship with error messages in any language beside
> english.
> > > > You'll need to translate the tokens in this file<
> http://github.com/rails/rails/tree/7a0e7c7270548138a333bc39aab5aec805...>and
> add the translations to your own language file.
> >
> > > > On Thu, Jan 15, 2009 at 11:07 AM, Wormsy <[email protected]>
> wrote:
> >
> > > >> I am using Community Engine in french and since the update of the
> > > >> project I have these translations errors on the users page during
> the
> > > >> registration process.
> >
> > > >> translation missing: fr, activerecord, errors, template, header
> >
> > > >> translation missing: fr, activerecord, errors, template, body
> >
> > > >>    * Password confirmation translation missing: fr, activerecord,
> > > >> errors, models, user, attributes, password_confirmation, blank
> > > >>    * Password translation missing: fr, activerecord, errors, models,
> > > >> user, attributes, password, blank
> > > >>    * Password translation missing: fr, activerecord, errors, models,
> > > >> user, attributes, password, too_short
> > > >>    * Login translation missing: fr, activerecord, errors, models,
> > > >> user, attributes, login, blank
> > > >>    * Login translation missing: fr, activerecord, errors, models,
> > > >> user, attributes, login, too_short
> > > >>    * Login translation missing: fr, activerecord, errors, models,
> > > >> user, attributes, login, invalid
> > > >>    * Email translation missing: fr, activerecord, errors, models,
> > > >> user, attributes, email, blank
> > > >>    * Email translation missing: fr, activerecord, errors, models,
> > > >> user, attributes, email, too_short
> > > >>    * Email translation missing: fr, activerecord, errors, models,
> > > >> user, attributes, email, invalid
> >
> > > >> These errors appear when I validate an empty registration form. With
> > > >> the previous Community engine version the problem did not exist. Is
> > > >> someone has an idea about this problem ?
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"CommunityEngine" 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/communityengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to