Actions

Difference between revisions of "Developer Area/Core Subsystems/Form API (Pieforms)/Form API i18n"

From Mahara Wiki

< Developer Area‎ | Core Subsystems‎ | Form API (Pieforms)
(Created page with "Form rules can be internationalised to different languages. This is still a work in progress, but basically either a rule can export a function named <code>form_rule_$rulename_i1…")
 
 
Line 1: Line 1:
 
Form rules can be internationalised to different languages. This is still a work in progress, but basically either a rule can export a function named <code>form_rule_$rulename_i18n</code> that returns a language string, or they can mash it into the Form class itself. Nigel still has to add support for getting strings from elsewhere, if necessary.
 
Form rules can be internationalised to different languages. This is still a work in progress, but basically either a rule can export a function named <code>form_rule_$rulename_i18n</code> that returns a language string, or they can mash it into the Form class itself. Nigel still has to add support for getting strings from elsewhere, if necessary.
 +
[[Category:Developer Area]][[Category:Pieforms]]

Latest revision as of 13:28, 17 May 2011

Form rules can be internationalised to different languages. This is still a work in progress, but basically either a rule can export a function named form_rule_$rulename_i18n that returns a language string, or they can mash it into the Form class itself. Nigel still has to add support for getting strings from elsewhere, if necessary.