Login page is not localized - problems with dialect support.

Description of problem:

Visit for example:
http://localhost:8080/business-central/login?locale=ja_JP
and the page is not translated.

http://localhost:8080/business-central/login?locale=ja
and the page is translated.

+++ This bug was initially created as a clone of Bug #1070083 +++

Description of problem:
Visit for example http://localhost:8080/business-central/org.kie.workbench.KIEWebapp/KIEWebapp.html?locale=ja_JP and you will see that the page is not translated. It still contains words 'Username', 'Password' and 'Sign In'. This applies for any available locale.

See attached screenshot which shows the issue for the Japan locale.

— Additional comment from Marek Baluch on 2014-02-26 03:33:43 EST —

The same applies for BRMS.

— Additional comment from Neus Miras on 2014-02-28 06:44:06 EST —

Those translation are been done at community kie-wb-distributions. It's necessary apply the changes at branding branch, we wait to do that after the tag.

— Additional comment from Neus Miras on 2014-03-06 11:56:04 EST —

kie-wb-distributions
Master
https://github.com/droolsjbpm/kie-wb-distributions/commit/f64caed007cd49c0601ea8f48a977991f7733945
https://github.com/droolsjbpm/kie-wb-distributions/commit/1d7874fb090deb87cfb407c32ce7be1fada204ec

6.0.x
https://github.com/droolsjbpm/kie-wb-distributions/commit/14ca4a75af6aa2512300393b7a63fc66ab4c0380
https://github.com/droolsjbpm/kie-wb-distributions/commit/6a47a3193e46d2c39d9e5516da659b1e9929bc8c

branding:
https://github.com/jboss-integration/kie-wb-distributions/commit/309bc4b9cd0d1d95142cc7b2132e824a8e8370eb

— Additional comment from Neus Miras on 2014-03-07 04:34:59 EST —

6.0.x
https://github.com/droolsjbpm/kie-wb-distributions/commit/01504d2d61201444cc58bbfea7cbacf7159baf21

— Additional comment from Pavel Kralik on 2014-04-29 10:22:55 EDT —

The login page is not localized, but still in English for ja_JP, zh_CN, etc.

— Additional comment from Kris Verlaenen on 2014-11-27 19:29:27 EST —

Neus, any chance you could continue where you left off? Note that branding is now also done in the community branch.

— Additional comment from Neus Miras on 2014-11-28 13:11:52 EST —

The problem was related to the message encoding.
For the releases is needed execute the mvn plugin to do the properly encoding(mvn native2ascii:native2ascii after the zanata update)
I have pushed it at master at commit:

Master
https://github.com/droolsjbpm/kie-wb-distributions/commit/a0a14250f2de10062c5f972bea2fadcd9d182c43

I told Michael the steps to avoid this kind of problem at release process.
I'll ask him if it is needed to cherry pick this commit at 6.0.2 branch or if it is considered as the i18n update at release.

— Additional comment from Neus Miras on 2014-12-02 08:17:55 EST —

I had commited a change in pom.xml to avoid do the replacer al Login literals

Master
https://github.com/droolsjbpm/kie-wb-distributions/commit/3381f6a519e89f98b5e689385df6e3cc22128699

— Additional comment from Pavel Kralik on 2015-01-07 11:00:23 EST —

Login page is not localized in BPMS 6.1.0.ER3.

— Additional comment from Pavel Kralik on 2015-01-22 11:05:43 EST —

Still only in english. BPMS 6.1.0.ER4

— Additional comment from Neus Miras on 2015-01-27 11:03:51 EST —

The zanata update before the release must contain a native2ascii plugin execution. This action has been added to the release process notes and it will be included in next releases.

— Additional comment from Pavel Kralik on 2015-02-13 08:41:22 EST —

Login page is not translated in BPMS 6.1.0.ER5
?locale=de_DE ja_JP zh_CN fr_FR

— Additional comment from Kris Verlaenen on 2015-02-13 08:44:57 EST —

Neus, could you double-check this? Note to also check the productized profile, which is different from the (default) community build.

— Additional comment from Neus Miras on 2015-02-16 04:53:51 EST —

At the community release the i18n is ok. This issue must be related with the productization process and the profile used. It seems the product release isn't generated with -Dfull.

— Additional comment from Marek Baluch on 2015-03-06 06:36:52 EST —

Still an issue with the product, 6.1.0.ER6 will display the same as on the attached screenshot for:

http://localhost:8080/business-central/login?locale=ja_JP

— Additional comment from Neus Miras on 2015-03-06 07:14:33 EST —

At the community release the i18n is ok. This issue must be related with the productization process. I commented this with Michael Biarnes, who runs the community release process, and he gave me the release guide: https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/README.md

The question is: if the productizacion process updates zanata literals,then it has to involve all the zanata and encoding plugins as descrives the release guide. If it doesn't, then it could be something related with the used profile.
I'm a bit lost because I don't know how the productization release process is done. Perhaps Ryan Zhang knows better what may be happening

— Additional comment from Kris Verlaenen on 2015-03-06 09:14:57 EST —

It seems to only have issues if you specify "ja_JP" as locale, using "ja" seems to work:
http://localhost:8080/business-central/login?locale=ja

Marek, could you verify this?

I would recommend to close this as verified if this works and open another BZ to improve dialect support for a future version, wdyt?

— Additional comment from Pavel Kralik on 2015-03-06 12:28:23 EST —

BPMS 6.1.0.ER6: specifying "ja" on login page works and "ja_JP" does not show localized page.