I have resumed the different positions, please comments considering the following situation:
the initial page is written in EN with 2 snapshots : one for button ("button 2019 en.png") and one for the form ("form 2019 en.png") as displayed in the EN GUI , both files being referenced as 2019 in Commons.
Then this EN page has been updated with new contents to fit 2022 GUI aspect where the button is unchanged but the form contains more items and the author provides in Commons new files "button 2022 en.png" and "form 2022 en.png".
1. GUI unchanged -> keep old image
If the image is unchanged then keep the old existing reference; as "button 2022 en.png" duplicates "button 2019 en.png" you must delete "button 2022 en.png" and reference "button 2019 en.png" in the EN root page before translate. This is in charge of the person who modifies the EN root page to keep coherence between text contents and image.
2. GUI modified -> use new snapshot
Replace the 2019 reference by 2022 one; as the form has changed, transclude now "form 2022 en.png" instead of "form 2019 en.png" in the EN root page before translate.
The image name must be included into 'translate' tags to warn the translator that the image has changed.
a. if image has not changed: there is no warning for an obsolete message -> ok, as today, nothing to do.
b. if the image has changed, translator replaces "form 2019 en.png" by "form 2022 fr.png" (or other according to his own language). ThIs makes him conscient that such a snapshot should exists. Two cases :
b1. If file "form 2022 fr.png" exists on Commons -> ok, nothing to do.
b2. If file "form 2022 fr.png" doesnt exist on Commons, two cases :
b21. The translator creates the snapshot himself and uploads it on Commons; this is easy because GUI appears already in his own language
b22. If it is impossible because of certain cases (GUI admin, extensions not installed on MediaWiki...), then translator can request for internal help
4. Using template LM and fallback process
What we want is to use image "form 2022 fr.png" when it exists. If not, following fallback should apply: "form 2022 fr.png" > "form 2022 en.png" > "form 2022.png" . We stop there because we know that "form 2022 en.png" or "form 2022.png" exist due to the coherence of EN root file.
You should use template LM which already implements these functions.
Of course we can call directly "form 2022.png" in the root EN source to translate - which makes the process completly automatic - but the translator will not be warned that a snapshot "form 2022 fr.png" must be provided.
5. Problem referencing of the snapshot by year
Sure a reference of the image should exist and it is rather a reference of the version linked to the contents. Here we have chosen the year.It is discriminant enough if the GUI is not modified more often.
6. Translation via svg update
It is a good idea but is risky:
a. manual processing :
a1. I download file "form 2022 en.png" provided by the author
a2. I search and translate the corresponding strings
a3. I upload file "form 2022 fr.png"
a4. -> not reliable due to manual intervention
b.automatic process :
b1. update "form 2022 en.png" replacing the strings by their translated version (from translatewiki.net, wikidata .... ?)
b2. -> not reliable : manual correction should be possible to correct the gaps.
=> I would prefer the manual capture of screen which reflects direcly what the GUI displays.
Thanks for reading, please leave comments.
Christian 🇫🇷 FR (talk) 07:59, 10 June 2022 (UTC)