L10n-simplified-0.9 died in Ruby 1.9.1 / Rails 2.3.3

Ruby
1

As lot of people, I suposse, I’m trying to move my Rails 2.1.2 app to
the newer versions of Ruby and Rails. And my first serious trouble is
that l10n-simplified-0.9 doesn’t work, and there isn’t a newer version.
That’s important for me, because my application is Spanish!!

¿Someone has a solution for this?

2

Fernando C. wrote:

As lot of people, I suposse, I’m trying to move my Rails 2.1.2 app to
the newer versions of Ruby and Rails. And my first serious trouble is
that l10n-simplified-0.9 doesn’t work, and there isn’t a newer version.
That’s important for me, because my application is Spanish!!

¿Someone has a solution for this?

Solved!!

First line of file must be

encoding: UTF-8

That allows you to use strings like ‘no es un número’ (with ú,
non-US-ASCII character)

3

Fernando C. wrote:

Fernando C. wrote:

As lot of people, I suposse, I’m trying to move my Rails 2.1.2 app to
the newer versions of Ruby and Rails. And my first serious trouble is
that l10n-simplified-0.9 doesn’t work, and there isn’t a newer version.
That’s important for me, because my application is Spanish!!

¿Someone has a solution for this?

¡Hola Fernando!
I’m the original author of L10n Simplified. I stopped maintaining it
because Rails 2.2 has this functionality natively built in.

However, feel free to send patches, and I will happily apply them.

Did you consider using the native I18N stuff in Rails when you move to
2.3?

Kind regards,
Jesper Rønn-Jensen
http://justaddwater.dk/

4

Jesper Rønn-jensen wrote:

Fernando C. wrote:

Fernando C. wrote:

As lot of people, I suposse, I’m trying to move my Rails 2.1.2 app to
the newer versions of Ruby and Rails. And my first serious trouble is
that l10n-simplified-0.9 doesn’t work, and there isn’t a newer version.
That’s important for me, because my application is Spanish!!

¿Someone has a solution for this?

¡Hola Fernando!
I’m the original author of L10n Simplified. I stopped maintaining it
because Rails 2.2 has this functionality natively built in.

However, feel free to send patches, and I will happily apply them.

Did you consider using the native I18N stuff in Rails when you move to
2.3?

Kind regards,
Jesper Rønn-Jensen
http://justaddwater.dk/

I’m a little afraid of moving to newer versions, because if every file
with non-US characters must be marked with # encoding: UTF-8 , it will
be very messy!! Probably I’ll wait until someone realises that we need
some default encoding option in config.sys…

About your patches, it’s easy: you must begin the lang_es.rb file (and
probably most of the lang_xx.rb) with the line:

encoding: UTF-8

Thank you!!