[daisy] BUG(s)? two different links to edit navigation document

[A Rocha Webmaster]

Thanks for your reply, Karel -- so it wasn't a bug, but a feature:

Seg, 2008-06-23 às 09:41 +0200, Karel Vervaeke escreveu:
> A site always uses the same variant for the navigation document, which
> is in the default branch and language specified in the siteconf.xml.

May I ask -- why?

In Daisy, translations are variants of pages; even navigation documents
can be translated. And yet, one site cannot have language variants. I
can't use the translation of a navigation document unless I define
'another site.'

> Normally when you have two sites (say one English and one
> Portuguese), site switching takes place

I didn't have site switching in place because I had one site per each
thing which *I* call a site. My mistake; I was indeed missing something,
not obvious due to the way languages work: I was naturally extending the
way Daisy works with pages, to whole sites.

We have one main site (arocha.org) for twenty national organisations. I
realised early on that I needed one site per national organisation,
because we need to allow for different skins, and Daisy forces all pages
in a site to share the same skin.

We have information on each organisation in ten languages.

Are you telling me that I need to define 20 x 10 = *two*hundred* 'sites'
for my content?

With unfriendly names like
/portugal-ar
/portugal-cs
/portugal-fi
/portugal-fr
/portugal-en
/portugal-es
/portugal-nl
/portugal-pt
/portugal-zh-Hans
/portugal-zh-Hant 
and so on for each country? And when we add a new country, we have to
add as many sites as languages there are at the time? And if we add a
language, that means another 20 sites?

What does that sound to you? I hope there's a way around this issue.

I have been trying to find the place in the Daisy chain where the
navigation is inserted, to match the navigation language to the document
language. I couldn't find such place in layout.xsl, or in
documentlayout.xsl, or in document-to-html.xsl -- will I have to change
the publisherRequest? Has anyone done this? Or is there some other kind
of solution?

My Daisy knowledge won't clearly be enough in the next few months to do
something which should be in place already, so I appreciate any help you
can offer.

Thanks
Júlio.