[daisy] Multi-language: solved with 2.2?

[Karel Vervaeke]

On Tue, 2008-07-01 at 10:59 +0100, A Rocha Webmaster wrote:
> Hello all,
> 
> I don't know if I should laugh or if I should cry.

I prefer laughing, but these sort of questions should probably be
treated on other mailing lists.

> 
> My hack to Daisy to allow for several language variants in a single site
> is NOT working. Basically, Daisy ignores the language indicated in the
> navigation if the current document is in the same language. Say the
> current doc is in Afrikaans and the default site language is English.
> With my hack I am able to use the Afrikaans navdoc variant instead of
> the English one, BUT if in the navdoc I refer to doc 1028 then Daisy
> will try and give me the doc in the DEFAULT language, ENGLISH. Even if I
> specify the language code, for instance the Afrikaans navdoc is this:
> 
> <d:navigationTree>
>   <d:doc id="1028-DSY" language="af"/>
> </d:navigationTree>
> 
> --but Daisy gives me the DEFAULT ENGLISH document even if I am
> specifically asking for the Afrikaans. Apparently when the navigation is
> requested Daisy cuts a few corners and omits the language code if it
> matches the current language code. Duh.

I am not following you, but I suggest you have a deep look at the source
code if you want to understand the mysterious behaviour.
If the problem is caused by the documentpage_pubreq hack, I can't say I
am very surprised, I'm glad though that 2.2 will work for you

> So now I am back to reading the documentation... and guess what, Daisy
> 2.2 SOLVES ALL THE PROBLEMS. Sorry for shouting, but there have been
> some serious communication issues here. So please confirm the following:

Yes, I do find the shouting annoying, try to avoid it.

> 
> Multi-language support: ONE collection, several sites, one per language.
> Is this true? (About the 20 sites x 10 language, I had said that my
> problem wasn't having 200 sites, but having 200 document collections.)

The multi-site setup with one collection, multiple language-specific
sites has been supported in Daisy since long before 2.2.  The only thing
that was not there was the automated multi-language site setup CLI.  All
this does is prepare a repository and some sites.

> 
> According to http://cocoondev.org/daisydocs-2_2/13-cd/504-cd.html --
> under 'Relaxation of variant creation right': I can have an Afrikaans
> editor which could create an Afrikaans variant of an English document,
> without actually being able to change the base English doc? (In the
> current 2.1 setup I've created such a role and tested it but it won't

That is indeed new since 2.2.

> let a user create a variant without write access to the original doc.)
> 
> Is there a release date for 2.3?

There is a biannual release cycle.  2.2 was in March IIRC.  We were
planning an early RC for 2.3 because some features need some testing by
a wider user base.

> 
> Is it possible to upgrade from 2.1 without losing data or my changes to
> skins (notably to xslt files)?

You will not lose the repository data: that is upgraded smoothly.
You certainly will not lose changes to skins if your skins are created
as per the documentation (i.e. you did not do your changes in the
default skin).
I can not guarantee that you will not need to change them, but
generally, xslt files can be reused between releases.

Regards,
Karel

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