Ticket #417 (closed Bug)
Labels in Navigation Tree for Multi-Language Sites
| Reported by: | rolf.sigg@… | Owned by: | somebody |
|---|---|---|---|
| Priority: | Minor | Milestone: | |
| Component: | Ext - navigation trees | Version: | 1.5 |
| Keywords: | Cc: |
Description
[jira2trac import : issue created on March 6, 2007 7:19:29 AM CET http://issues.cocoondev.org/browse/DSY-417 ]
Use Case: A site with every document available in multiple languages (for all documents the same set of languages).
The navigation tree seems always to be generated from the document variant that is configured in siteconf.xml (id, branch, language). Even if a document in a different branch/language is shown, the navigation tree is generated from the site variant.
For our use case this alone would not be a problem, since the site structure for all languages of the site should be identical. But the navigation document additionally contains labels. If a document with a different language is shown, the navigation tree still shows the labels in the site default language. Therefore, navigation tree and document language do not match any more.
I see the following solutions:
1. Don't use labels in multilanguage sites :-(
2. Create a different site for each desired language, each with it's own navigation document. In the skin, hide the variant chooser and display a language chooser instead. The language chooser switches to the corresponding site.
3. Modify daisy such that the navigation tree is generated by the navigation document variant for the same branch/language as the document, with fallback to the site branch/language if this variant does not exist.
4. ... I am sure there are other possibilities...
From our current point of view, the 3rd solution would be best for our use case.
Change History
comment:2 Changed 3 years ago by paul
[jira2trac import : comment created by bruno on March 6, 2007 7:46:18 AM CET]
Option 2 is currently the recommended way.
You don't necessarily need to hide the variant chooser, Daisy will automatically switch to the most appropriate site (this auto-switching is described somewhere in the documentation).
BTW, this is more a topic to discuss on the mailing list.
[jira2trac import : comment created by rsigg on March 6, 2007 7:22:29 AM CET]
Another solution: