ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "F. Canan Pembe Muhtaroglu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-13139) Implement multi-language support for Ambari Web user interface
Date Fri, 18 Sep 2015 09:04:04 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-13139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

F. Canan Pembe Muhtaroglu updated AMBARI-13139:
-----------------------------------------------
    Description: 
Currently, externalized strings can be defined for English only (in messages.js). One should
be able to define those strings also for other languages to support internationalization.

As a solution, a small change in initialize.js (in ambari-web) is proposed. In this solution,
the language of the web user interface is selected according to the language setting of the
browser. This is an approach also used in some other web-based solutions. The default locale
is defined as English. This applies when there is no support for the current language of the
browser.

For this solution to work, a "locales" directory should be created in ambari-web (e.g. app/locales/)
and current messages.js file should be moved to app/locales/en/ where "en" stands for English.
When other languages will be added, only a new messages.js file needs to be added to the directory
for that language in "locales" directory.

  was:
Currently, externalized strings can be defined for English only (in messages.js). One should
be able to define those strings also for other languages to support internationalization.

As a solution, a small change in initialize.js (in ambari-web) is proposed. In this solution,
the language of the web user interface is selected according to the language setting of the
browser. This is an approach also used in some other web-based solutions. The default locale
is defined as English. This applies when there is no support for the current language of the
browser.

For this solution to work, a "locales" directory should be created in ambari-web (e.g. app/locales/)
and current messages.js file should be moved to app/locales/en/ where "en" stands for English.
When other languages will be added, only a new messages file needs to be added to the directory
for that language in "locales" directory.


> Implement multi-language support for Ambari Web user interface
> --------------------------------------------------------------
>
>                 Key: AMBARI-13139
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13139
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-web
>            Reporter: F. Canan Pembe Muhtaroglu
>            Priority: Minor
>         Attachments: AMBARI-13139.patch
>
>
> Currently, externalized strings can be defined for English only (in messages.js). One
should be able to define those strings also for other languages to support internationalization.
> As a solution, a small change in initialize.js (in ambari-web) is proposed. In this solution,
the language of the web user interface is selected according to the language setting of the
browser. This is an approach also used in some other web-based solutions. The default locale
is defined as English. This applies when there is no support for the current language of the
browser.
> For this solution to work, a "locales" directory should be created in ambari-web (e.g.
app/locales/) and current messages.js file should be moved to app/locales/en/ where "en" stands
for English. When other languages will be added, only a new messages.js file needs to be added
to the directory for that language in "locales" directory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message