[daisy] Multi-language: solved with 2.2?

[A Rocha Webmaster]

Hello all,

I don't know if I should laugh or if I should cry.

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.

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:

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

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
let a user create a variant without write access to the original doc.)

Is there a release date for 2.3?

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

Júlio.