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

[Karel Vervaeke]

I forgot to mention that with a multi-lingual setup,
it is likely that you will find the Daisy 2.2 translation management
useful.

Translation management (try introduction)
http://cocoondev.org/daisydocs-2_2/537-cd/544-cd.html

Guided tour (screenshot galore, skip the daisy-wiki-add-site stuff)
http://cocoondev.org/daisydocs-2_2/537-cd/557-cd.html

HTH,
Karel

On Tue, 2008-06-24 at 09:58 +0200, Karel Vervaeke wrote:
> >From your current setup I think two hundred sites is a possibility
> (of course creating the sites by hand would be a chore, you probably
> would like to script this), however, read on...
> 
> In our setups, we have always used one site per language. I don't know
> if this is a possibility for you, but consider 1 site per language, so
> that the navigation document has countries below the root node:
> 
> en/portugal/...
> en/germany/...
> de/portugal/...
> de/germany/... (or even de/deutschland/...)
> 
> It does not limit the number of documents,
> but it does limit the number of sites.
> 
> On Mon, 2008-06-23 at 19:56 +0100, A Rocha Webmaster wrote:
> > 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?
> 
> That's just the way sites work: they have a default language and a
> default branch (i.e. a default variant space). In short, each site
> operates in a particular variant space.
> 
> >
> > 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.'
> 
> Ah.  I just realised it should be possible to make the navigation tree
> match the language of the active document using publisher requests:
> 
> http://cocoondev.org/daisydocs-2_2/373-cd/194-cd/424-cd.html
> 
> (I have never done or tried this approach, let us know about your
> experience if you end up doing things like this).
> 
> Regards,
> Karel
> 
> > 
> > > 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.
> > 
> > _______________________________________________
> > daisy community mailing list
> > Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
> > mail to: daisy at lists.cocoondev.org
> > list information: http://lists.cocoondev.org/mailman/listinfo/daisy
> _______________________________________________
> daisy community mailing list
> Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
> mail to: daisy at lists.cocoondev.org
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy