Forum Discussion
You have to create a similar structure for every locale, on the base of that you have to create a custom navigation. See screenshot https://prnt.sc/h5jo1w and can also apply those different variations of nav in a single component on the bases of language.
Here is a discussion might be helpful.
- JeffT8 years agoAce
Thanks VikasB. The issue with those scenarios (if I'm reading them correctly) is that these would work with categories/boards that are language-specific. Our community is set up for real-time translation, so users who speak different languages can communicate with each other in the same board.
The solution looks to be creating a custom nav with the embedded custom text references.
- VikasB8 years agoBoss
Option 1: Locale-Specific category structure: Real-time translation would not be required here. As you set the language-specific redirection in page init. i.e. users who are coming from the US will be redirected to English category, if coming from JA they will be redirected to Japan category.
Option 2: One structure for all the locale: You already using this one. In this case, you really need to use real-time translation. But I know you are facing the problem here with the board/category name translation. As you can not use text keys here.
A workaround can be used here. You can show the self-created board/category name instead of Lithium's OOTB. You can create the text key on the bases of board/category id as id will be unique. i.e. a board having id "HealthTips" can be replaced by the key ${text.format(coreNode.id)}
in text keys, you can set the value of HealthTips = 健康のヒント
Related Content
- 6 months ago
- 11 months ago
- 3 years ago