Traduction, manuals and QET internationalization. (Page 1 of 2)

El 07/06/2019 a las 13:45, laurent Trinques escribió:

El 07/06/2019 a las 15:21, laurent Trinques escribió:

El 12/06/2019 a las 0:05, Julio Marín escribió:

Hello,
I think no if I remenber well, you could perhaps create it.

  Great ! it's the case. ;-)

svn checkout svn://svn.tuxfamily.org/svnroot/qet/qet/trunk qelectrotech_trunk

https://svnweb.tuxfamily.org/listing.ph … me=qet/qet

License is GPL V2 or later.

Nice, thanks Julio. 

I synced Fernando dropbox on QET download area, I have started a manual branch on QET subversion, but isn't uptodate.

https://svnweb.tuxfamily.org/listing.ph … 8425807cb4 

Julio, I will see to synced Fernando work on Subversion documentation branch.
Is dificult for Fernando to commit changes on Subversion because is on MS Windows.

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.

Fernando and Laurent.
I am only thinking, not sure if it is possible, the workflow could be:

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

Hi,

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.

Hi, 

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

Fernando, I think you could ask Arun for helping.
Arun's a very nice guy, and he know well Sphinx.

No Julio I can add you.