Rails - Mar 2006 - Translate to one language: Globalize is overkill?

Hi,
I am developing a Rails application which should be in ONE language (not 
English).

Globalize seems overkill for this purpose (do you agree?).

So I''m trying some of the approaches on the wiki. In particular:
http://wiki.rubyonrails.org/rails/pages/OverridingRailsMessagesInAnotherLanguage

This *does* override the month names, but does *not* override the error 
messages.
I''m wondering:
- is the code correct?
- should errors.rb be located in overrides/active_record/errors.rb, or 
can it also be in overrides/errors.rb. I.e. does the location matter?

The override method described in
http://wiki.rubyonrails.org/rails/pages/HowToLocalizeActiveRecordErrors
*does* work for ActiveRecord errors.

Or perhaps I should forget all this and look at Globalize?

Thanks,
Mike

-- 
Posted via http://www.ruby-forum.com/.

Try checking out http://rutils.rubyforge.org/ as a russian language 
translation. You can get the idea.

Mike D wrote:
> Hi,
> I am developing a Rails application which should be in ONE language (not 
> English).
> 
> Globalize seems overkill for this purpose (do you agree?).
> 
> So I''m trying some of the approaches on the wiki. In particular:
>
http://wiki.rubyonrails.org/rails/pages/OverridingRailsMessagesInAnotherLanguage
> 
> This *does* override the month names, but does *not* override the error 
> messages.
> I''m wondering:
> - is the code correct?
> - should errors.rb be located in overrides/active_record/errors.rb, or 
> can it also be in overrides/errors.rb. I.e. does the location matter?
> 
> The override method described in
> http://wiki.rubyonrails.org/rails/pages/HowToLocalizeActiveRecordErrors
> *does* work for ActiveRecord errors.
> 
> Or perhaps I should forget all this and look at Globalize?
> 
> Thanks,
> Mike
>

Yaroslav Markin wrote:
> Try checking out http://rutils.rubyforge.org/ as a russian language
> translation. You can get the idea.
I''m sorry, but I don''t understand a thing from this site.

-- 
Posted via http://www.ruby-forum.com/.

Found the problem. Apparently Rails now has separate validations for
:blank
:empty
as well as a few new ones (since the Wiki entries were made).
I''ll update the Wiki.

Thanks,
Mike



-- 
Posted via http://www.ruby-forum.com/.