sync the wiki child page


Status message

You are not a member of this team. If you want to be part of this team, click on 'Subscribe to this team'.
Yes, I am looking for the answer for a user to be able to click on a certain page and be able to find the foreign translation. Since I'd like to be in sync with English as much as possible.

Jordi, do you have an answer for this? Thanks !


jordi's picture
Submitted by jordi on Sun, 07/12/2015 - 11:01

For all wiki pages, there is a link on the upper right column called "Other translations of this page". If you click on that link, it will take you to a page where you will find all the translations of the book associated with that wiki page.

Therefore, if you click on that link and you don't see the Chinese translation, it means that there is no translation for that language.

Another important point is that translations are done "per-book", not "per-page". So when you do a translation of a page, you need to select the option "It's a translation" and then select the "book" that the page belongs to.

It is important to understand that this is not an interface to make 1 to 1 mapping translations. The translations of a book into another book don't have to be exact translations. They can be, but not necessarily. This works in fact similarly to the standard wikipedia system, where articles in different languages are not translations but they are independent.

For instance, the wikipedia article about "Gravity" in English is and the article about Gravity in Spanish (Gravedad) is Notice that they are written by two different authors and they are 100% independent. They are not translations.

In Labdoo we provide a feature to link wiki books that are of the same scope and written in different languages together so that readers can travel from one language to another for a given book. But these wiki books don't need to be pure translations, they can be different. An example is the German books, in some cases they take a different structure than the English books.

Doing a pure translation is a valid option and it is encouraged so that there is a unified format, but some people have different views on how documentation should be written, so we allow that flexibility. The approach taken is up to the writer.

Here is another method to know if a book has a translation:

1. Go to the Wiki index:

2. Select the book you want to know if there is a translation for under "Original wiki book". For instance, let's say you select the "About Labdoo" book:

3. You can see here that this book has only been translated (as of right now) to Catalan and German.

You can repeat the above for all books.

If there is another feature missing, feel free to create a "task" under software development.

wendy's picture
Submitted by wendy on Mon, 07/13/2015 - 15:58

Hi Jordi, Thank for the answer. Yes, there's only a few books Labdoo has so far so I have no problem to find which book has been translated and which hasn't:)

Since I am dividing Chinese translations into mini-tasks, I am trying to find the best way to have different individuals translate English into Chinese and keep track of their progresses.

For other language, yes, I agree people may have the options to translate the hierarchy differently. For the Chinese translations, The page contain can be different, the page title is translated, but I'd like to keep the rest in sync with English as much as possible. Therefore, I'd like to see a "Other translations of this page" for all pages in a book together:) If it cannot be done, is there a way I can generate a list of all books with it's children pages in different languages? So I can put them into excel myself? Thanks!

jordi's picture
Submitted by jordi on Mon, 07/13/2015 - 19:28

Wendy i see your point and good observations. Unfortunately, i have been thinking about this, and the two approaches are not compatible. Either we do it per-book, or per-page, but both cannot coexist from an implementation perspective. The issue with per-page approach is that this will make it impossible for people to do their own free still translations based on their own structure. For instance, with per-page approach, Ralf would not be able to write his German documents following his free style.

But the per-book approach gives flexibility for both types of translators. Per-book allows free-style translators like Ralf to work well, and at the same time, it does not limit 1 to 1 mapping translators like you. We could try to implement this inside the system but it would be really complicated and it would make the interface more complex attempting to support both per-book and per-page.

I think it should not be that complicated to do one to one mapping.

For instance, let's say I want to translate the values and philosophy book to Catalan.

1. Here are all the current translations:

2. Here is the original in English:

3. And here is the current Catalan translation:

Looking at 2 and 3, i can see easily see which sections have not been translated yet to Catalan and assign sections to various translation persons. You can also create a spreadsheet to help you track that.

Does this help? i know it is not perfect, but keep in mind that for this one, if we want to implement a translation dashboard, it would require quite a bit of time to code and you would not have it soon.