[daisy] Default language considered harmful?

[A Rocha Webmaster]

Thanks for your explanation, it was very useful and I see the language
variants are also very handy. The fact that the variants are hidden
under friendly URLs for search engine optimisation is a big bonus, not a
drawback!

All of our content will ultimately be translated. The translation
improvements in Daisy 2.2 look very promising.

The reason I did not thank before was that I was busy moving the content
from "default" to "en"... my first document task :) That and deleting
the "default" versions was easy, the hard part now is to find out how to
tell Daisy that I was the "en" variant of the Navigation document in the
"en" documents... help, anyone?

Júlio.

Qua, 2008-01-23 às 17:25 +0100, Marc Portier escreveu:
> > Should I use the "default" language?
> I wouldn't do that for the content that you know will be translated 
> eventually.
> 
> And even if (you think now) it will never be translated: if your content 
> *has* a language then it just makes sense to share that info with Daisy 
> (and variants are then the most logical way imho)
> 
> Seriously, I think "default" in this respect has to be read as 
> "do-not-care", "not-applicable", "none" or even more pragmatically 
> "i-do-not-want-to-use-this-language-variants-feature-for-this-content"
> 
> > Would it be better for any future purposes to always create an "en"
> > variant for English pages, and so on, and leave the "default" unused? In
> 
> 1/ yes: I would always make an "en" (or whatever your site's language is)
> 
> 2/ but also: keep and use "default" since some content really doesn't 
> have language variants!
> 
> Admitted: the translated navigation docs introduce translated path-names 
> (for SEO purposes), and the language-switcher on top of the page brings 
> you to home-pages rather then to the selected variant of the current doc.
> 
> After upgrading to the upcoming 2.2 release the advanced translation 
> management features will allow even more control and inspection (e.g. of 
> updates on existing docs that are still waiting for translation updates).
> 
> See http://cocoondev.org/daisydocs-2_2/537-cd/557-cd.html
> 
> Based on the Veld & Duin the conclusion is clearly: "It has been a wise 
> decision to use the language variant features of Daisy". Even back then 
> on the 1.4 release.