In Liferay portal, you can use your own language. Multilingual organizations get out-of-the-box support for up to 36 languages. Users can toggle among different language settings with just one click and produce/publish multilingual documents and web content. You can also easily add other languages in your public, private pages, or other organizations.

locales=ar_SA,eu_ES,bg_BG,ca_AD,ca_ES,zh_CN,zh_TW,cs_CZ,nl_NL,en_US,en_GB,et_EE,fi_FI,fr_FR,gl_ES,de_DE,el_GR,iw_IL,hi_IN,hu_HU,in_ID,it_IT,ja_JP,ko_KR,nb_NO,fa_IR,pl_PL,pt_BR,pt_PT,ru_RU,sk_SK,es_ES,sv_SE,tr_TR,uk_UA,vi_VN

As shown in above locale settings, multi-languages get supported as well in Web Content. That is, web content can be entered in as many languages as desired. As you can see, only content got localized. In addition, the name (article title) and the summary, that is, abstract description of web content, should be localizable, too. (Abstracted from the book: Liferay Portal 6 Enterprise Intranets).

Fortunately, knowledge base articles have fields: title, content, summary (description), etc. Multi-languages should get supported as well in knowledge base articles. That is, knowledge base articles (title, content and summary) can be entered in as many languages as desired. For more details, you can refer to the blogs post: Multiple-language support for Knowledge Base articles.

Currently (at revision 68460), users’ screen name and friendly URL must be characters between a-z and A-Z or digital number 0-9 plus special characters e.g.”-“,”.”,”_”.   That is, users’ screen name and friendly URL cannot be specified by multiple languages like Chinese, Japanese. 

For example, Asia-based users would like to have native user names and friendly URL like Chinese, Japanese, etc.

Use case A: set up native user screen name like “underwaterworld” as “海底世界” in Chinese, “アンダーウォーターワールド” in Japanese. Of course, it could be any locale as mentioned above.

Use case B: set up native friendly URLs like “liferay” as “生命之光” in Chinese, “生命の光” in Japanese. Sure, it could be any locale as mentioned above.

Use case C: set up native user email address like “underwaterworld@abc.com” as “海底世界@abc.com” in Chinese, “アンダーウォーターワールド@abc.com” in Japanese. Of course, it could be any locale as mentioned above.

This article will address how to add new feature (use case A, B and C) - support users’ screen name, email address and friendly URLs with 36 languages in liferay 5.2 and 6.

Solution Overview

In general, you should be able to create native user names and friendly URL with your own languages. As shown in following screen-shot, you should be able to see samples.

Setting up a group in Japanese, frienly URL as “生命の光”

Setting up a group in Chinese, friendly URL as “生命之光”

Creating a new user in Japanese, screen name as “アンダーウォーターワールド”, and password as “アンダーウォーターワールド”

Creating a new user in Chinese, screen name as “海底世界” and password as “海底世界”

Creating a new user in Japanese, native email address as “アンダーウォーターワールド@abc.com”, and password as “アンダーウォーターワールド”

Creating a new user in Chinese, screen name as “海底世界@abc.com” and password as “海底世界”

Results

Use case A: set up user native screen name like “Underwater World” as “海底世界” in Chinese, “アンダーウォーターワールド” in Japanese

Set: How do users authenticate?  - by screen name

sign in (as screen name / password: “アンダーウォーターワールド”/“アンダーウォーターワールド”) in Japanese

sign in (as screen name / password: “海底世界”/“海底世界”) in Chinese

Use case B: set up friendly URLs like “liferay” as “生命之光” in Chinese, “生命の光” in Japanese

Check friendly URL of the group “生命の光” in Japanese, after signed in.

Check friendly URL of the group “生命之光” in Chinese, after signed in.

Use case C: set up user native email address  like “Underwater World@abc.com” as “海底世界@abc.com” in Chinese, “アンダーウォーターワールド@abc.com” in Japanese

Set: How do users authenticate?  - by email address

sign in (as email / password: “アンダーウォーターワールド@abc.com”/“アンダーウォーターワールド”) in Japanese

After logged in

sign in (as screen name / password: “海底世界@abc.com”/“海底世界”) in Chinese

Summary

As you can see, this feature supports three use cases:

• Use case A: set up native user screen name like “underwaterworld” as “海底世界” in Chinese, “アンダーウォーターワールド” in Japanese.
• Use case B: set up native friendly URLs like “liferay” as “生命之光” in Chinese, “生命の光” in Japanese.
• Use case C: set up native user email address like “underwaterworld@abc.com” as “海底世界@abc.com” in Chinese, “アンダーウォーターワールド@abc.com” in Japanese.

That is, with this feature you would be able to set up users' native screen name, native email address and friendly URLs in your own languages (up to 36 languages). Refer to LPS-14436

Is this feature useful? Your comments / suggestions?