I18n YAML files not parsable with psych yaml library (Bug #346)

While moving the 1.9.2 test from unstable_experimental to unstable on ci.cp.o, I was running into an issue, that I faced regularly when setting up tests for 1.9.2. I do not know, why it does not occur everytime, but only under certain conditions, I could not identify yet. The error looks like the following:

/var/lib/jenkins/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/psych.rb:148:in `parse': couldn't parse YAML at line 25 column 14 (Psych::SyntaxError)
    from /var/lib/jenkins/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/psych.rb:148:in `parse_stream'
    from /var/lib/jenkins/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/psych.rb:119:in `parse'
    from /var/lib/jenkins/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/psych.rb:106:in `load'
    from /var/lib/jenkins/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/1.9.1/psych.rb:205:in `load_file'
    from /var/lib/jenkins/.rvm/gems/ruby-1.9.2-p180@122111e57d93198a0f313f0a05f86083/gems/i18n-0.4.2/lib/i18n/backend/base.rb:205:in `load_yml'
    from /var/lib/jenkins/.rvm/gems/ruby-1.9.2-p180@122111e57d93198a0f313f0a05f86083/gems/i18n-0.4.2/lib/i18n/backend/base.rb:191:in `load_file'
    from /var/lib/jenkins/.rvm/gems/ruby-1.9.2-p180@122111e57d93198a0f313f0a05f86083/gems/i18n-0.4.2/lib/i18n/backend/base.rb:20:in `block in load_translations'
    from /var/lib/jenkins/.rvm/gems/ruby-1.9.2-p180@122111e57d93198a0f313f0a05f86083/gems/i18n-0.4.2/lib/i18n/backend/base.rb:20:in `each'
    from /var/lib/jenkins/.rvm/gems/ruby-1.9.2-p180@122111e57d93198a0f313f0a05f86083/gems/i18n-0.4.2/lib/i18n/backend/base.rb:20:in `load_translations'
    from /var/lib/jenkins/.rvm/gems/ruby-1.9.2-p180@122111e57d93198a0f313f0a05f86083/gems/i18n-0.4.2/lib/i18n/backend/simple.rb:57:in `init_translations'
    from /var/lib/jenkins/.rvm/gems/ruby-1.9.2-p180@122111e57d93198a0f313f0a05f86083/gems/i18n-0.4.2/lib/i18n/backend/simple.rb:40:in `available_locales'
    from /var/lib/jenkins/.rvm/gems/ruby-1.9.2-p180@122111e57d93198a0f313f0a05f86083/gems/i18n-0.4.2/lib/i18n/config.rb:39:in `available_locales'
    from /var/lib/jenkins/.rvm/gems/ruby-1.9.2-p180@122111e57d93198a0f313f0a05f86083/gems/i18n-0.4.2/lib/i18n.rb:36:in `available_locales'
    from /var/lib/jenkins/.rvm/gems/ruby-1.9.2-p180@122111e57d93198a0f313f0a05f86083/gems/actionpack-2.3.11/lib/action_view/template.rb:226:in `valid_locale?'

...

Anyways, I think there is a rather simple underlying problem, that can be easily fixed. Here is the background:

There are currently multiple libraries for parsing YAML files. While 1.8.x is using syck (made by _why) 1.9.2 seems to also ship with an alternative named psych. It seems, syck is still used as default unless configured differently. On the other hand, some sources claim, that RubyGems 1.5 explicitly loads psych if it is available. [1] JRuby's 1.9 mode seems to only support psych.[2]

Anyways, syck seems to be rather forgiving when parsing YAML files and also works with files, that are actually invalid YAML. This seems to be the case for all locale files in ChiliProject.

Proposed fix

The line

order: [ :year, :month, :day ]

is invalid YAML and needs to be replaced with

order:
    - :day
    - :month
    - :year

This was done in Rails' I18n in https://github.com/svenfuchs/rails-i18n/pull/78

By changing these lines in ChiliProject's i18n files, the files would be parsable by both syck and psych and whatever library might win in the future or on the local system, we will be safe. Also, this seems to be the only valid way write them in the first place.

A pull request including the proposed changes will be attached shortly.

[1]: http://blog.segment7.net/2011/01/31/rubygems-1-5#comment-615
[2]: http://jira.codehaus.org/browse/JRUBY-5549