How should we treat translatable text in APM parameters? I have gone
through all parameters in dotLRN and propose the following:Site wide translatable text parameters to remove from APM and move
into a dotlrn message catalog:
departments_pretty_name,
departments_pretty_plural,
classes_pretty_name,
classes_pretty_plural,
class_instances_pretty_name
class_instances_pretty_plural,
clubs_pretty_name,
clubs_pretty_plural,
dotlrn_main_portlet_pretty_name,
subcommunities_pretty_name,
subcommunities_pretty_plural,
dotlrn_admin_pretty_name
non_member_page_name
admin_page_name
user_portal_pretty_name
class_instance_portal_pretty_name
Embedded translatable text in APM parameters, keep in APM, but replace
the translatable text parts with message keys with syntax #foo#:
class_instance_pages_csv
club_pages_csv
subcomm_pages_csv
user_portal_pages_csv
As an example, the default value of class_instance_pages_csv is currently:
Class Home,Simple 2-Column;Calendar,Simple 1-Column;File
Storage,Simple 1-Column
and the multilingual new version would become:
<span>#</span>dotlrn.class_home_page#,Simple 2-Column;<span>#</span>dotlrn.calendar_page#,Simple
1-Column;<span>#</span>dotlrn.file_storage_page#,Simple 1-Column
Comments?