Mechanism to do screenshots for locale languages independantly #66212

New Issue

Hoang Duy Tran · 2019-06-28T13:39:46+02:00

Hoang Duy Tran commented

2019-06-28 13:39:46 +02:00

Hoang Duy Tran (hoangduytran) added a subscriber: Hoang Duy Tran (hoangduytran).Edited · Tue, Jun 25, 3:11 PM
Comment Actions

Will the locale languages be able to capture their own set of screen images if GUI texts are translated and how this could be done and store?

Brecht Van Lommel (brecht) added a comment.Wed, Jun 26, 2:20 AM
Comment Actions

There is no mechanism to do screenshots for each language separately, and there will be none for the 2.80 manual.

Hoang Duy Tran (hoangduytran) added a comment.Wed, Jun 26, 12:38 PM
Comment Actions

  In T65710#707048, @Brecht Van Lommel (brecht) wrote:

  There is no mechanism to do screenshots for each language separately, and there will be none for the 2.80 manual.

Hi Brencht,
I think Blender documentation should allow this option. As far as I know, many people in my country (Vietnam) have a need to use Blender and yet their English capability is not yet up to par. That's why I learned from the Russian's documentation team to leave the English references on titles and section titles, allowing readers to reference the original document if needed. There are situations where translation needs clarifications from the original texts. I think Blender needs to close the loop on this front. It's only the '_images' needed to add, and of course the amount of space needed to be allocated, and then

http://www.sphinx-doc.org/en/master/usage/configuration.html#confval-figure_language_filename

Aaron Carlisle (Blendify) added a subscriber: Aaron Carlisle (Blendify).Wed, Jun 26, 8:46 PM
Comment Actions

  In T65710#707048, @Brecht Van Lommel (brecht) wrote:

  There is no mechanism to do screenshots for each language separately, and there will be none for the 2.80 manual.

@Hoang Duy Tran (hoangduytran) is right here, there is a mechanism to do this however the only problem with this is the amount of work required to implement this. Having to make a dozen screenshots in different languages is very tedious. So unless there is an automated way for us to make UI screenshots and correctly link this to the manual. I would rather us not spend our time on this. If we are going to continue this discussion lets please open a separate task.

I have copied all reference info of this thread to create a new task, for which I think is an important one. I think Aaron Carlisle (Blendify) is correct.

There should be an automatic methods for capturing portions of screen during the documentation. This would be TOO MUCH works for the time being, since
there must be an add-on for document team to use.
I personally suggest that the bulk of cutting images in the locale language should be the task for translators and we
all should start from the English set, just like the PO files, and
editing of images can be done by translator at their own time of convenience and choices.
At times, in obscure languages, such as Vietnamese, there would be necessities to include further graphical indicators to explain images further for clarity purposes, and this of course CANNOT be done by, or rely on, the English documenters.
As long as there are mechanism for the html code referring to locale dependant images, and a set of English images by default, translators of languages should be able to amend them to fit their own needs.
The 'make update_po' SHOULD NOT update the image directories for locale languages, translators must do this themselves, ie. by opening the directories in file browsers and copy over images they need. There should be a provision for a blank images with a text on it such as "SCREENSHOT TO BE PROVIDED", and a tooltip indicating the name of the target image, so reader and translator knows what's missing.
I think everyone touching this technically challenged task should be able to do RIGHT CLICK and choose 'View Page Source' to find out what's written behind the HTML page (or F12 on Firefox, on Google Chrome).

That said, all the files and material used to capture screens (ie. examples) for the English version should be made available publicly, best if the file was saved at the point of screen captured, so translators will only have to perform their own screen captures upon/immediately after blend file's loading. I don't know how this is done at the documenter's end so I cannot comment on.

I could volunteer to investigate the first part of the mechanism, that is to insert necessary configuration for sphinx-build but I need help on how to make the html for all languages in my local machine so I can test the solutions.

Hoang Duy Tran (hoangduytran) added a subscriber: Hoang Duy Tran (hoangduytran).Edited · Tue, Jun 25, 3:11 PM Comment Actions Will the locale languages be able to capture their own set of screen images if GUI texts are translated and how this could be done and store? ------------------------- Brecht Van Lommel (brecht) added a comment.Wed, Jun 26, 2:20 AM Comment Actions There is no mechanism to do screenshots for each language separately, and there will be none for the 2.80 manual. ------------------------- Hoang Duy Tran (hoangduytran) added a comment.Wed, Jun 26, 12:38 PM Comment Actions ``` In T65710#707048, @Brecht Van Lommel (brecht) wrote: ``` ``` There is no mechanism to do screenshots for each language separately, and there will be none for the 2.80 manual. ``` Hi Brencht, I think Blender documentation should allow this option. As far as I know, many people in my country (Vietnam) have a need to use Blender and yet their English capability is not yet up to par. That's why I learned from the Russian's documentation team to leave the English references on titles and section titles, allowing readers to reference the original document if needed. There are situations where translation needs clarifications from the original texts. I think Blender needs to close the loop on this front. It's only the '_images' needed to add, and of course the amount of space needed to be allocated, and then http://www.sphinx-doc.org/en/master/usage/configuration.html#confval-figure_language_filename ------------------------------ Aaron Carlisle (Blendify) added a subscriber: Aaron Carlisle (Blendify).Wed, Jun 26, 8:46 PM Comment Actions ``` In T65710#707048, @Brecht Van Lommel (brecht) wrote: ``` ``` There is no mechanism to do screenshots for each language separately, and there will be none for the 2.80 manual. ``` @Hoang Duy Tran (hoangduytran) is right here, there is a mechanism to do this however the only problem with this is the amount of work required to implement this. Having to make a dozen screenshots in different languages is very tedious. So unless there is an automated way for us to make UI screenshots and correctly link this to the manual. I would rather us not spend our time on this. If we are going to continue this discussion lets please open a separate task. ------------------------- I have copied all reference info of this thread to create a new task, for which I think is an important one. I think Aaron Carlisle (Blendify) is correct. - There should be an automatic methods for capturing portions of screen during the documentation. This would be TOO MUCH works for the time being, since - there must be an add-on for document team to use. - I personally suggest that the bulk of cutting images in the locale language should be the task for translators and we - all should start from the English set, just like the PO files, and - editing of images can be done by translator at their own time of convenience and choices. - At times, in obscure languages, such as Vietnamese, there would be necessities to include further graphical indicators to explain images further for clarity purposes, and this of course CANNOT be done by, or rely on, the English documenters. - As long as there are mechanism for the html code referring to locale dependant images, and a set of English images by default, translators of languages should be able to amend them to fit their own needs. - The 'make update_po' SHOULD NOT update the image directories for locale languages, translators must do this themselves, ie. by opening the directories in file browsers and copy over images they need. There should be a provision for a blank images with a text on it such as "SCREENSHOT TO BE PROVIDED", and a tooltip indicating the name of the target image, so reader and translator knows what's missing. - I think everyone touching this technically challenged task should be able to do RIGHT CLICK and choose 'View Page Source' to find out what's written behind the HTML page (or F12 on Firefox, on Google Chrome). That said, all the files and material used to capture screens (ie. examples) for the English version should be made available publicly, best if the file was saved at the point of screen captured, so translators will only have to perform their own screen captures upon/immediately after blend file's loading. I don't know how this is done at the documenter's end so I cannot comment on. I could volunteer to investigate the first part of the mechanism, that is to insert necessary configuration for sphinx-build but I need help on how to make the html for all languages in my local machine so I can test the solutions.

Hoang Duy Tran commented

2019-06-28 13:39:46 +02:00

Added subscriber: @hoanguk

Aaron Carlisle commented

2019-06-29 01:36:36 +02:00

Added subscribers: @ideasman42, @Blendify

Aaron Carlisle commented

2019-06-29 01:36:36 +02:00

In order for this to be possible to automate there needs to be a mechanism in Blender to automatically locate a UI Panel by its type i.e. RENDER_PT_eevee_hair, make sure it is expanded and make a screenshot. @ideasman42 would know best how feasible this would be to implement.

If we are able to use translated UI screenshots they will have to be implemented in the 2.8x release and not 2.8 due to how late 2.80 is already.

In order for this to be possible to automate there needs to be a mechanism in Blender to automatically locate a UI Panel by its type i.e. `RENDER_PT_eevee_hair`, make sure it is expanded and make a screenshot. @ideasman42 would know best how feasible this would be to implement. If we are able to use translated UI screenshots they will have to be implemented in the 2.8x release and not 2.8 due to how late 2.80 is already.

Aaron Carlisle referenced this issue

2024-01-14 19:55:46 +01:00

The inclusion of the command table makes a massive amount of data untransferable to another language #104678

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Mechanism to do screenshots for locale languages independantly #66212