What is the recommended procedure to translate Drupal Books? It's possible to translate the individual pages and it works one by one, but the translated page never carries the book outline with it. Do you have to create a separate book for each language and then?

Well I am exploring this of course but someone knows already it's always welcome with some help ;-)

Comments

vikingew’s picture

vikingew commented
Status: Active » Fixed

In fact, it does work! Although it didn't look like it to start with... I looked too much at the top level book page, where I couldn't find any outline and then when I looked at the translated page the translation of "Outline" in my own language didn't really reach out to me, but it's the Outline that is the key to get books translations working.

edinjapan’s picture

edinjapan commented

This depends on which release of Localizer you are using.
Somewhere in past versions of Localizer, when you clicked on a translation link for a certain language, the whole user interface would change. (In that case, the book outline would be in the "target" language as well.) I imagine having the UI change allowed all the "correct" variables and flags to line up correctly, with the downside being that the preferred language UI was discarded.

I am not sure when exactly it changed, but using the 5.x-1.x-dev version of mid-August 2007, when you click on a translation link for a book, the UI stays in your viewing language (which actually makes sense as this is your preferred working language), but this also brings the outline info in the viewing language rather than the target translation.
My own current workaround for this is to change the UI to the target language before I click on the translation link--that way the correct outline is brought over.

I don't know if it is possible, but personally I think it would be nice if the following would happen:
-----
When you click the translation link for a certain language, the UI stays in your current viewing language, and brings over the original language content (so it is easier to translate), but the language setting is automatically set to the target language, AND, the book outline showing is the one for the target language.
-----
Of the Drupal 5.x "standard" content types, this really only matters for books. However, if someone were to create other types (using CCK, etc.) I can see where it would be very hard for Localizer to do everything automatically in all cases. (In that sense, maybe leaving things alone is the best.)

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)