[WG: I18N & L10N] I18N support for Role name and Site type

[Jean-Francois Leveque]

Hi Steve,

I also think the displayed value should be internationalized, not the 
internal value. What made you think one of us thought something else?

J-F

On 19/03/2014 11:32, Steve Swinsburg wrote:
> IMO these primary identifiers should not be internationalised. The
> reason for this is that many parts of the code expect this to be a
> certain value, some even hardcode it. Making this value a moving target
> *will* cause difficulties. And how will it be handled in multiple
> locales? What will the code be looking for? This is trouble waiting to
> happen.
>
> In a perfect world these would not be an English string, but would be a
> number or some other language agnostic identifier. Labels for roles
> should be translated though so that anything user facing is i18n'ised.
>
> cheers,
> Steve
>
>
> On Wed, Mar 19, 2014 at 9:20 PM, Jean-Francois Leveque
> <jean-francois.leveque at upmc.fr <mailto:jean-francois.leveque at upmc.fr>>
> wrote:
>
>     Hi Jun,
>
>     You could check https://jira.sakaiproject.org/browse/SAK-12397 and
>     https://jira.sakaiproject.org/browse/SAK-22344 which might be the latest
>     on both i18n of role names and site type labels.
>
>     I think lots of us here would like this to be solved.
>
>     If the names/labels are internationalized, they could be updated from
>     database with https://jira.sakaiproject.org/browse/SAK-18678 and
>     https://source.sakaiproject.org/contrib/rsmart/messagebundle/
>     (https://jira.sakaiproject.org/browse/SAK-18984).
>
>     Do you mean altering names on a site basis?
>
>     Cheers,
>
>     --
>     Jean-François
>     UPMC, Paris
>
>     On 19/03/2014 09:34, Gao Jun wrote:
>      > Hi all,
>      >
>      > I'm now working on I18N support for Role name (instructor, student,
>      > maintain, etc.) and site type(course, project).
>      > Since many tools use these names with string stored in DB, so a
>     lot of
>      > work need to be done.
>      >
>      > Up to now, I made I18N support for Role worked under site-manage and
>      > authz tool, and the todo list is still long.
>      >
>      > I wonder if anyone has tried work on this before or any JIRA issue
>      > already exists.
>      > If there is no JIRA issue on this, I'll create a new one.
>      >
>      > Here is my solution(Role name for example)
>      > Use a strategy like tool menu, which has default L10N message and
>     user
>      > can alter it.
>      >
>      > Add a new properties file under folder config/localization
>      > Add a method getName to Role which use the way like get name of a
>     tool.
>      > Modify the corresponding tools to add I18N support.
>      >
>      > Is anyone interested in this?
>      >
>      >
>      > --
>      > Gao Jun
>      > Fudan University