mambo dancer wrote:
Exciting, finally we will be able to put our hands on RC2!
Anybody knows if RC2 is compatible with the multilanguage component mambelfish?
regards
We have bad news and good news ..
The bad news:
Its not compatible in the sense that you cannot translate via the mamblefish backend - this is because the way mamblefish worked (upto now at least) depends on a default key name of 'id' for each component table to be translated. This problem exists with many existing components. The mamblefish developer is aware of this (I and many others have issued MR against this) and has mentioned that he is working on a solution.
That was the bad news.
The good news:
All CB 1.0 RC2 fields are language friendly. This means that all fixed field values (example radio field values, drop down field values, field descriptions, field help values, etc) can accept _UE_ language plugin string values. So if for example you have a Yes/No check box field, you can define _UE_YES and _UE_NO strings in your language file and mamblefish will take care of the translation. You can see this in action on my reference site
www.karpathiantree.com (see the registration screen).