> Ouch, this is what I feared. That's going to hurt.
>
> Sorry for the noob question, but is it correct that Globalize2’s Sta
> tic backend works with yaml/rb files only, and does not store transl
> ations in the database? In which case I would have to unload the vie
> wtranslations from the db and store them in .yml files?
>
> Since I don't need any model translations at this point (and I can  
> live with simple pluralization) would it be correct to assume I can  
> just use the built-in I18n module instead?
>
>
> Thanks again
>
> Op 23 nov 2008, om 00:55 heeft Sven Fuchs het volgende geschreven:
>
>> Hi Joost,
>>
>> there's none.
>>
>> Globalize2 uses the Rails I18n API which is not compatible with  
>> Globalize.
>>
>> That's the price we had to pay for "doing the right thing".
>>
>> That said, one could imagine a tool that helps converting existing  
>> views. If you're interested in trying something like that, you  
>> might want to register to the rails-i18n Google group and ask for  
>> ideas or help.
>>
>>
>> On 23.11.2008, at 00:10, joost wrote:
>>
>>> Hi all
>>>
>>> I'm a satisfied user of Globalize (version 1) but eager to upgrade  
>>> to Rails 2.2.
>>>
>>> What's the upgrade path from the old Globalize to Globalize2? I  
>>> have many view translations I wish to preserve.
>>>
>>> Thanks for any help
>>
>