Multi language portal

Question

Hello All,
I have a requirement from our customer to create a custom WebCenter portal application (version PS3). He needs support for Hindi language as well.
Now, I am able to show hindi language for adf component labels/values using standard Java localization/resource bundle.
I have the following two queries
1) For the labels that are part of the "Portal Administration Console" such as "Create Page","Set Default Access" and "Look and Layout" etc. is there any way to provide localized translations? I know that OOTB there are about 28 languages that portal supports. For these languages the translations are available out of the box. But what about a new language such as hindi? Can we provide our own resource bundle which the admin console application can then pick up?
2) Page titles are defined using "pages.xml" (in JDev) and these get stored into the respective pageDef file. Is it not possible to use localized labels here? Even if my page content appears in hindi, my page title (in navigation model) always appears in English. Is there any way to localize this?
Any pointers around this?
Thanks,
Prashant

Answer 1

prashant82 wrote:
Well, it turns out I was making a fundamental mistake!
Conceptually, pages.xml (Page Hierarchy) should be treated as a place to maintain page security. Navigation Model is the place where we define site structure and labels. It is not a good practice to add page hierarchy directly into the navigation model. However, if you add just page links to the navigation model, you won't be able to manage pages at runtime - show/hide page, reorder them, add new page. So you have to answer the question wether you need runtime page management or not.
I overcame problem with non-localized pages.xml manually, with sollution Yannick Ongena once provided. Because you propably render navigation on your own in page template, you can set PropertiesBundle keys as lables in page titles and then display properties values instead of keys. For example:
<c:forEach var="node" varStatus=" items="#{navigationContext.navigationModel['modelId=default-navigation-model'].listModel['startNode=/, includeStartNode=false']}">
<LI-tag>
<af:commandLink id="gLink" actionListener="#{navigationContext.processAction}">
<f:attribute name="node" value="#{node.children[0]}" />
<strong>
<af:outputText value="#{not empty portalBundle[node.title] ? portalBundle[node.title] : node.title}" id="pt_ot4"/>
</strong>
</af:commandLink>
</LI-tag>
</c:forEach>
It however does not overcome problems with addind pages on runtime, but it's at least partial sollution.
Edited by: Maciej Nowicki on 2012-03-15 04:44