This issue is for tracking progress and problems with the German screenshots.

Tasks and their status (unmarked tasks are assumed not to be done yet):

  1. Ensure that most of the current version's user interface has been translated into German, so that the screenshots will show very little if any English on them.
  2. Translate the "scenario text" into German. The text to be translated is the "Scenario Text" section of the scripts/TermsToTranslate.fods spreadsheet. What is needed is a 3-column sheet with these columns:
    • Context (the column called Context in the TermsTo Translate sheet)
    • English text
    • Your language text
  3. Make initial automated screenshots. Procedure: See auto_screenshots/README.txt.
  4. Make initial non-automated screenshots. See the source/en/images/README.txt file for details of which images need to be made.
  5. Check each screenshot to make sure it is all in the target language and is readable. The German language team will do this as they translate each topic. If problems are found, add tasks here so that the screenshots can be updated. Leave this issue open until all the topics have been translated and the screenshots checked and/or updated.

Comments

michaellenahan created an issue. See original summary.

jhodgdon’s picture

The first two steps are for the DE group to take care of:
- Make sure the UI is mostly translated.
- Translate the "scenario text".

Once those two steps are done, attach the scenario text translation to this issue, and step 3 (making automated screenshots) is for me, and the DE team can make the non-automated screenshots (see step 4 -- you will also need steps 1 and 2 to be done).

jhodgdon’s picture

Assigned: Unassigned » joachim namyslo

Ping! We should really take care of this sometime. Currently all the screenshots for German in the User Guide that are automatically generated are in English, even though most of the Guide has been translated into German.

joachim namyslo’s picture

The last time I investigate this one there was a problem with some stuff like the content View. Views are configuration and get never translated even if translations are existing. So I am not sure what is the best way to report parts of Drupal 9 ui with errors or untranslateable core UI strings.

If we are ready with the translation. The review is ongoing. We will build the farmer's market site from scratch to review the guide against Link texts and so. That will be the best time to do screenshots. At that point, I'll try to run the screenshot script.

Maybe it is better to run it ones to get an overview of what strings are currently untranslated. Any opinions on that?

jhodgdon’s picture

All I need to make the screenshots is translations of the farmer's market-specific text in the "Scenario Text" section of the file scripts/TermsToTranslate.fods. You cannot really run the "screenshot script". I need to set up the new test class in the user_guide_tests project, and then run it on DrupalCI and download the output.

I know about the problem with configuration being updated. That is a known Core bug:
#2905295: Configuration language being overwritten during module install
There is a work-around patch on that issue, and we have the DrupalCI on user_guide_tests set up to apply that patch so that we can make the screenshots. I suggest you apply it on any test site you use:
https://www.drupal.org/files/issues/2019-02-26/2905295-work-around.patch

Another bug I know about is that currently, the region names in themes are not being pulled into localize.drupal.org. That issue:
#3043258: Region names are not extracted from theme info files
There is no work-around for that one right now -- that screenshot will show some English. Take a look at source/ca/images/block-regions-bartik.png for an example (that is Catalan).

If you find other errors in the Drupal 9 UI, you should report them with Core bug reports. Also link them here. Or discuss in Slack before creating issues. Thanks!

joachim namyslo’s picture

Status: Active » Needs work

Still to much English because installing modules overwrites configuration translation. Have to find the bug report in the core issue queue and reference it here.

eojthebrave’s picture

I'm happy to help with settings things up to generate screenshots. It looks like we still need to translate the text in the scripts/TermsToTranslate.fods spreadsheet. It's primarily text that's used as user input in the tests that generate the screenshot. Things like content used for a custom block etc.

Once that's done I can create the test case for German and run it and we can see how it does at creating screenshots and go from there.

joachim namyslo’s picture

OK got it. Since I reached 38000 approved German translations yesterday, I need a break. But I'll update this, when I translated the file. I think I can start on Friday.

joachim namyslo’s picture

StatusFileSize
new123.28 KB

Added *.fods file contains translations into German now.

@eojthebrave Let me know if you need something else to produce the screenshots.

Thank you for helping out with screenshot creation

The glossary is finished and reviewed thoroughly, so the only screenshots in German are missing. If we have them, we can start adopting D10 Changes as soon as a new branch gets created.

joachim namyslo’s picture

odras’s picture

Screenshots for configuration(modules, theme, user registration ... ) created and attached.

eojthebrave’s picture

Hi @odras, thank you for working on making screenshots. But before you do anymore I wanted to give you a heads up that most of these we can generate automatically using the https://www.drupal.org/project/user_guide_tests project. I just haven't been able to do that yet as I've been focused on getting that updated for Drupal 10. However, with the updated .fods sheet from @Joachim Namyslo above I should be able to work on that this week.

So while your help is super awesome, you don't need to manually create all these screenshots.

eojthebrave’s picture

Version: 8.x-2.x-dev » 9.1.x-dev

eojthebrave’s picture

I added the automatically generated Drupal 10 screenshots to the 10.0.x branch of the User Guide project. You can see them here https://git.drupalcode.org/project/user_guide/-/commit/244eb98e3090cb651...

The goal is to get the content on Drupal.org updated for Drupal 10. And in #3327235: Update User Guide content for Drupal 10.0.x/9.5.x I updated all the English text, and the screenshots for all the versions. So I think it probably makes the most sense to focus on getting the German content ready for Drupal 10 as well since in the (hopefully) near future that's what will be displayed on Drupal.org.

joachim namyslo’s picture

Superbe. Thank you very much.

Is it possible to get the pdf output of the guides version containing theese Screenshots?

If so reviewing the guide as it is, would be a, chram. So in case there is, something wrong, we can fix it before the updated chapters arrive.

I bet we'll find some people willing to review, this again, now that they do not have to trabslate a but, anymore.

joachim namyslo’s picture

eojthebrave’s picture

Sure, here's a link to the PDF generated from the files currently in the 10.0.x branch. https://www.dropbox.com/s/y1lx4iwd9z446vd/guide-de.pdf?dl=0

------------

Additionally, while the automated screenshot tool generates most of the images, there are a few that it can't do. Here's what I found in the source/en/images/README.txt file about this:

A few images could not be generated by automatic screen capture. Here is a list
of the manually-generated images (in order by topic appearance in the guide):

Cover image: coverimg.png -- the SVG source for this image is in the "assets"
directory of this project and is called coverimage.svg. You will need to edit
that file, translate the text "User Guide", then export to PNG.

Running the installer (topic install-run.txt): You will need to run the standard
installer, choosing your language, entering values for the Farmers Market web
site, and take a screenshot of each step. Images:
- install-run-1.png -- Select language
- install-run-2.png -- Select profile (Standard)
- install-run-3.png -- Database
- install-run-4.png -- Installation in progress
- install-run-5.png -- Site configuration
- install-run-6.png -- Site installed configuration

------------

So it looks like someone will need to create those 6 install-run images manually.

joachim namyslo’s picture

The cover text is printed magically in to the cover svg when the compiling bash-script is running.

This morning I've done another review of the 9.1 branch and found out tgat there are some misspellings in the preface section. But the rest of the guide seems to be ok.

I'll check the files for the 10.x branch as well. As soon as that is done I'll create the missing screenshots you named above.

I am not sure about the dimensions right now, but i'll take a look at the 9.1 branch to find out what dimensions where used for these screenshots.

joachim namyslo’s picture

eojthebrave’s picture

I am not sure about the dimensions right now, but i'll take a look at the 9.1 branch to find out what dimensions where used for these screenshots.

You can look at the images already in the source/de/images/ directory for an example. They're currently in English, and need to be replaced with German versions. The dimensions don't need to be exact, just close enough. More important is that the screenshots capture the same content.

joachim namyslo’s picture

Hmmm, I just did that screenshots today and replaced them but it seems there are still the old ones shown in gitlab on drupal.org. I am not sure if it is just a caching problem. Can someone take a look at the image directory in sources/de, please?

If I open the image I got the old 8.x screenshot in English If I use the download button top right at the page I got the translated image. You can test this with install-run-5.png for example.

eojthebrave’s picture

I'm guessing it's a caching issue as they look fine to me. I'm seeing the updated Drupal 10 screenshots like this one https://git.drupalcode.org/project/user_guide/-/blob/10.0.x/source/de/im...

joachim namyslo’s picture

Version: 9.1.x-dev » 10.0.x-dev
Status: Needs work » Fixed

Good So tey are all in in 10.x finally. Great! Thank you all. Guess we can set this one to fixed then.

eojthebrave’s picture

🎉 Thanks for all of your hard work on this.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.