Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.This issue is to track progress on setting up for translations into Catalan.
Tasks:
- [DONE] Add a new issue component for translations into this new language, by editing the Project page. The component should be called "CA translation".
- [DONE] Make a new source/ca directory. Copy all of the source (English) files, including the images subdirectory, into the new directory. Keep the file names and IDs the same as they were in English.
- [DONE] Add a new section to the _attributions.txt_ file for the translation team management for this language. Template:
==== Translation into LANGUAGE_NAME The LANGUAGE_NAME translation of this guide was coordinated by: * https://www.drupal.org/u/person1[Person One] * https://www.drupal.org/u/person2[Person Two] of http://example.com[Company] - [DONE] Make a separate issue for the screenshots. See Guidelines document for issue template.
#2798681: [CA] Catalan screenshots - [DONE] Grant issue maintainer and VCS commit permissions to the manager or managers of the language team for the new language, by editing the _Maintainers_ page for the project.
- [DONE] Make issues for translating each topic into the target language. There is a spreadsheet file scripts/bookmarks.fods that will aid in doing this.
- [DONE] Add ca to the build scripts in scripts/languages.txt, and verify that it builds without errors.
- Optional but recommended steps:
- [DONE] Make a translation glossary for this language. File scripts/TermsToTranslate.fods is a good starting point. This should be located in a place that the language team normally uses for communication, such as on localize.drupal.org.
- Make a shared spreadsheet (for example, using Google Sheets) to track translation progress. File scripts/bare_topic_names.csv is a good starting point; you can add columns for the issue URLs, and status of each issue.
- Start translating!
Comments
Comment #2
jhodgdonUpdating summary, since VCS commit permissions have been done, and the translation glossary is also done.
Comment #3
jhodgdonLooks like @rvilar has added issues for all the Catalan translations, so updating summary. Did the spreadsheet work well for that? Hopefully! (If so, send thanks to Balu of the Hungarian team -- https://www.drupal.org/u/balu-ertl ).
When is the sprint you are having to start actually translating? I will be away from Drupal-land for 3 weeks starting October 5, but I am around until then... The Hungarian team is already translating -- it looks like they had a big sprint yesterday, so you can ask Balu how that is going.
YEAH!!! This is very exciting.
And I will get started on those CA screenshots soon. I have been working out a number of bugs with the Hungarian screenshots first... see #2798661: [HU] Hungarian screenshots. (Found some Core bugs and/or localize.drupal.org bugs, ugh.) Hopefully by the time I get to the end of Hungarian, CA will be quite easy. :)
Comment #7
jhodgdonThe automated CA screenshots are done. Manual images, such as the cover image and Installing screenshots, have not been done yet... see #2798681: [CA] Catalan screenshots.
Meanwhile, I have added Catalan to the build scripts, and put the Catalan version of the User Guide up on the development site:
https://userguide_new-drupal.dev.devdrupal.org/d8guide/ca/index.html
Of course, at the moment it is mostly in English, but with mostly Catalan screenshots.
Anyway, you can instruct your translators to use that site, with its editor and preview capabilities, for translating. On the "Edit source" pages, you can see both the English and Catalan source, as well as a preview of what the Catalan will look like as you edit (if you click the Preview button, which looks like a green checkmark).
Example: From that Catalan landing page, click on the "Editing a content item" topic, which will take you to:
https://userguide_new-drupal.dev.devdrupal.org/d8guide/ca/content-edit.html
with its English text and Catalan screenshots.
From there, in the sidebar, click "Edit source file content-edit.txt", which will take you to:
https://userguide_new-drupal.dev.devdrupal.org/edit/d8guide/hu/content-e...
Enjoy!
ps: I think that everything in the issue summary here has been done, so I am marking this as Fixed.
Comment #9
jhodgdonComment #10
jhodgdonNote to the Catalan team and/or eojthebrave: I am going to be out of town for several weeks in October. If the Catalan translation has some commits and you want to see them on the Development site linked in #10, you will need to run the site build job.
To do that, or rather to request that this be done, log in to the #drupal-infrastructure IRC channel, and ask someone there to run the "build-userguide_new-drupal.dev.devdrupal.org" job on the Development site Jenkins. (They should know what this means.) That will update the development site to the latest from the Git repository.
Comment #11
rvilarThank you very much @jhodgdon for all the huge effort you put on fixing this.
Yes, I used the spreadsheet from Bart and it worked very well (I'll send an email to him only to thanks for that tool).
We are trying to find a weekend in october to start sprinting on that (and in localize too). Meanwhile, I will start translating some pages to test all the platform and the process.
One question abou tusing the site to translate all the content: if we use the editor directly, when we finish this translation, we have to export the file and put it on the git repository, nor? If not, next time that someone run the script to rebuild the documentation we will lose changes done directly on the site, nor?
Comment #12
jhodgdonRight. The editor is just a tool to use so you can see what the formatting does. You can also edit the files in a text editor.
When you're done editing, you click the "Download new file" button and save it as a text file. Then it has to be added to the Git repository.