I have been searching for the best option for internationalization of the documentation, I have discovered how to define the file name from the figures of the project at conf.py file.

I have defined and tested the following configuration for filename variable:

figure_languge_filename = "{path}{language}/{basename}{ext}"

I will re-structurate the documentation for a final test and once it is made and I see the result, I will inform you to discuss the update of the documentation.

I have seen some small modifications at the release version, I will also use the re-structuration to update the changes.

What is the decision about the future version 0.8? I would like to know what will be changed to do not spend too much effors on those issues.

If you need I can transfer ownership to you.

https://github.com/fdomateu

English
https://download.qelectrotech.org/qet/j … ET_ru.html

Russian
https://download.qelectrotech.org/qet/j … l/QET.html

https://download.qelectrotech.org/qet/joshua/html/

I think Github is a better choice for Windows users they can participate easily on documentation translation than QET SVN.

In reference on how to proceed on the documentation, using my short experinece on sphinx I would like to expose my opinion.

Option 1: Using function gettext from sphinx (.pot files)

This option I like when a manual is ready and should be tanslated. Today QElectroTech documentation is not ready, the documentation is in continuous development.

This function collects all translatable strings except the text from the screenshots of QElectroTech. For the user would be nice if the screeshots from the different menus and messages are also on the language form the manual.

Option 2: Using one sphinx "project" for all languages (.rst files)

Sphinx can generate problems if the tree is too long. After some language we may have some problems when we build the manual.

This option allows dividing the screenshots in two different ways to reduce the documentation size, icons and images which will be common for all languages and menu screenshots which will be different for each language.

Option 3: Using a different sphinx "project" for each language (.rst files)

This option means one project for each language, all of them with the same structure. The size of the documentation will be bigger than the rest of options. The management of this propose will may not be easy if the team is big, each language may will be develloped different without a master.

At this option, the php code from the QET web which is in development will manage the project language which should be displayed.

Regarding to the platform which should be used for the documentation, is there any repository platform where the modification of files can be made using only the Internet navigator? On person is responsible of managing the build source but all the rest of the team can modify the source fiels locally or using the navigator. I know github as option.

If Max can convert it to Github QElectroTech.

1. I put all files or only /Documentation, in a repository on GitHub.

2. Sincyn GitHub with ReadtheDocs.

3. Sincyn ReadtheDocs with Transiex.

4. Translate _es, _de and _fr at Transiex with a team.

5. ...

6. ...

What do you think about

svn checkout svn://svn.tuxfamily.org/svnroot/qet/qet/branches/documentation

Enjoy ! 

Edit: you can now, I can't merged files, because a lot of changes, also I prefer to delete all and added news source folder, build folder isn't useful on Subversion, I think.