[daisy] [JIRA] Closed: (DSY-417) Labels in Navigation Tree for Multi-Language Sites

[Bruno Dumon (JIRA)]

     [ http://issues.cocoondev.org//browse/DSY-417?page=all ]
     
Bruno Dumon closed DSY-417:
---------------------------

    Resolution: Won't Fix

Closing this issue, please use the mailing list for further discussion on this topic, if needed.

> Labels in Navigation Tree for Multi-Language Sites
> --------------------------------------------------
>
>          Key: DSY-417
>          URL: http://issues.cocoondev.org//browse/DSY-417
>      Project: Daisy
>         Type: Bug
>   Components: Navigation
>     Versions: public - 1.5
>     Reporter: Rolf Sigg
>     Priority: Minor

>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira