rails-i18n Google Group

Re: Changing :activerecord to :models in Rails yml files

2010-01-05T12:36:25Z

I've hacked together a small script to convert the current situation
to my proposed situation and tested it out on one of the bigger
projects I did recently. The results are:
Before: 899 lines, 33KB
After: 975 lines, 35KB
Not a big difference in verbosity.
The script is here: [link]

Re: Changing :activerecord to :models in Rails yml files

2010-01-04T22:12:50Z

Nice! We should also try work with a real yml file, to see if it will
get more verbose or not with Iain proposal.

Re: Changing :activerecord to :models in Rails yml files

2010-01-04T20:07:52Z

Forked the gist and added 3.yml, which is Clemens' proposal with some
more examples
[link]
Feedback please :)

Re: Changing :activerecord to :models in Rails yml files

2010-01-04T12:55:48Z

Yeah, we should definitely take this into account when working on this
new i18n yml format.

Re: [rails-i18n] Re: Changing :activerecord to :models in Rails yml files

2010-01-04T12:12:42Z

I think that feature is crucial. I can think of it being used with more
frequency than with a generic message.
Sven Fuchs escreveu:
...

Re: [rails-i18n] Re: Changing :activerecord to :models in Rails yml files

2010-01-04T11:32:53Z

also, what about full_messages per model or attribute? :)

Re: Changing :activerecord to :models in Rails yml files

2010-01-04T10:20:35Z

Good proposal Clemens! But would be odd to have "admin" and "errors"
sharing the same keys level:
en:
models:
admin:
name: Admin
attributes:
name: Name
errors:
messages:
blank: "can't be blank"
Unless we make errors a root key as well:
en:

Re: Changing :activerecord to :models in Rails yml files

2010-01-04T10:17:42Z

I find Clemens' solution the most elegant I've read so far. It keeps
all the translations of a model together, instead of splitting them
into two separate scopes. I do miss the global error message
translations.
About the transition, we could also make a configuration option,
making it possible to switch between old-style and new-style, but I

Re: Changing :activerecord to :models in Rails yml files

2010-01-04T09:13:28Z

Maybe use "names" instead of "models"? Or change the structure on a
larger scale? Like so:
en:
models:
admin:
name: Admin
attributes:
name: Name
etc.

Re: Changing :activerecord to :models in Rails yml files

2010-01-04T09:05:31Z

good idea! +1

Re: Changing :activerecord to :models in Rails yml files

2010-01-04T08:27:11Z

We could link, but since people have ActiveRecord stuff in their yml
the link would be overwriten anyway, like in the simple example below:
en:
activerecord:
errors:
blank: "cannot be blank"
That's why I think that we should just yell a warning if we find an
activerecord key.
By the way, Sam Ruby, pointed an issue, imagine the following

Re: [rails-i18n] Changing :activerecord to :models in Rails yml files

2010-01-04T08:05:57Z

+1 :)
regarding bc - can we just link?
en:
models:
errors:
messages:
blank: "can't be blank"
invalid: "invalid"
en:
activerecord:
errors: :"models.errors"
?

Re: [rails-i18n] Changing :activerecord to :models in Rails yml files

2010-01-04T08:00:52Z

On Mon, Jan 4, 2010 at 5:47 AM, Rodrigo Rosenfeld Rosas
Agreed, but we probably need a fallback anyway — look in :models, than in

Re: [rails-i18n] Changing :activerecord to :models in Rails yml files

2010-01-04T02:47:59Z

Jos� Valim escreveu:
I completely agree.
Rodrigo.

Changing :activerecord to :models in Rails yml files

2010-01-03T22:59:03Z

Hey folks,
I want to propose changing the namespace in I18n files
from :activerecord to :models. The reason is to be more agnostic since
with ActiveModel it will appear several plugins that are similar to
ActiveRecord and this would mean in a lot of duplication:
en:
activerecord:
errors: