[haiku-doc] Re: User Guide: Choosing a language

Vincent Duvert wrote:
Question is, how on earth is that possible without compromising our lean&mean HTML with JavaScript or CSS magic? 

Making hover menus in CSS is possible, and relatively easy :
http://haiku.pastebin.com/m5c21b037
This is basic CSS2, so I'm expecting it to work with almost every browser, but this should be tested first ;) 

Hmmm. That isn't bad at all.
I guess the actually available translations in those menus can be inserted when exporting the pages from the db to HTML?
Now another question arises: What do we do when not all pages of the user guide are yet translated? 
Do we just wait until all are? Or do we fall back to English if there isn't a 
{LANGUAGE} page?

We already have a related problem: What about images?
Right now, since there isn't any localization, every language-dependent image is under /en/images/ and therefore /{LANGUAGE}/images/ for translated pages. Do we just copy all images into the {LANGUAGE} hierarchy? Feels a bit bloaty. Is it possible to have links to the /en/images/* instead and just replace those piece by piece once localized versions appear? Can SVN handle this?
If so, we could deal with the actual HTML pages likewise: link to each of the /en/* pages which are replaced as the translations are rolling in. 

Regards,
Humdinger

--
--=-=--=-=--=-=--=-=--=-=--=-=--=-=--=-=--=-=--=-
Deutsche Haiku News @ http://www.haiku-gazette.de

Other related posts: