I want to start the process for translating the User Guide to French

I've contact the FR association and translators, and they are happy that someone propose to help them coordinate. I've never commit something on this repo, but use git every day at work, just need to be a little drive on process for translating this guide.

This issue is to track progress on setting up for translations into French.

Tasks

  1. [DONE] Add a new issue component for translations into this new language, by editing the Project page. The component should be called "FR translation".
  2. [DONE] Make a new source/fr 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.
  3. [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]
    
  4. [DONE] Make a separate issue for the screenshots. See https://www.drupal.org/node/2837539.
  5. [DONE - SebCorbin and vanessakovalsky] 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. Note: Language team managers will need to re-clone their Git repositories using "Maintainer" mode after receiving this permission, in order to be able to commit to the repository.
  6. [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.
  7. [DONE - French translations inserted for Glossary and Preface; Index appears to be the same in French/English] Copy the English configuration file scripts/lang-en.conf to file name lang-lc.conf, where lc is the language code. Optionally, check https://github.com/asciidoc/asciidoc to see if there is an existing language configuration file for that language, and copy the three lines we need in our language configuration file from there, so that they are translated already.
  8. Add notes to the guide.txt and glossary.txt file translation issues, that if the headings for Index, Preface, and Glossary are changed from what they are in these files currently (they have already been translated into French), the scripts/lang-fr.conf file will need to be changed at the same time.
  9. [DONE] Add langcode to the build scripts in scripts/languages.txt, and verify that it builds without errors.
  10. Optional but recommended steps:
    • [DONE] Glossary is here : http://traduction.drupal.fr/ 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.
    • [DONE]https://www.drupal.org/node/2837749 Create an issue to track translation progress. It should list the individual translation issues, providing a place to look to see which are done and which still need to be done. You can make a list of the issues in the issue summary by following these steps:
      1. Open the Issues page for the project.
      2. Filter to the issue component for your translation. You'll see the first page of issues.
      3. Open a JavaScript console tool in your browser (usually by using the Inspect or Inspect Element context menu).
      4. Execute this JavaScript code to make a list of the issue numbers shown on this page:
        jQuery("tbody .views-field-title a").each(
          function(){
            console.log("[#" + jQuery(this).attr("href").replace("/node/", "") + "]");
              }
        );
        
      5. Copy and paste the output into the issue summary.
      6. Go to the next page of issues and repeat the JavaScript, until all issues have been found.
  11. Start translating!

Comments

vanessakovalsky created an issue. See original summary.

vanessakovalsky’s picture

StatusFileSize
new8.43 MB

Just create a patch with creating the directory in source, copying files from en version, and begin translating with guide.txt
I will create all issue for all files today or tomorrow and a shared spreedsheet to in order to help translators.

Please tell me if I can do something more than this.

jhodgdon’s picture

Hi there, and welcome to the User Guide project!

It's actually easier for me to do the setup for a new language without a patch. You can start translating after I get the English stuff copied in.

But before we start... A few questions:

a) Can you confirm that you are either one of the leaders of the localize.drupal.org French translation team, or are coordinating with them?

b) Who will need to have commit access to the Git repository -- and can you confirm that they have experience working with Git projects on Drupal.org?

c) Is the French Drupal UI mostly translated for Drupal 8.2.x? [OK, localize.drupal.org confirms it is mostly translated.]

Thanks!

Once I hear about (a) and (b), I will set up the French files, issue component, and maintainer access for French team managers. Then, your team can do steps 4, 6, and 8 in the issue summary (make the issue for screenshots, and make issues for translating each individual file in the project). And the optional steps.

Thanks!

vanessakovalsky’s picture

Hi @jhodgdon

thanks for your quick answer
a) Yes I confirm that I'm coordinating with translations teams leaders and they are ok for helping but none of them have time to coordinate user guide's translation, so they are very happy that I can do that
b) For now, I'm the only one who need access to git, and yes I know how git project's on DO are handle. I let you know if other people need access to the git
c) Most translation is done, remaining string are system string, and we try to find time to organize a sprint to validate all remaining strings

Thanks for your time again

simon georges’s picture

Hi,

If it helps, I have one of the leaders of the localize.drupal.org French translation team, and I can confirm everything vanessakovalsky is saying (and her motivation as well ;-)).
I'd be happy to have git access as well, but Vanessa is clearly the main motivated localizer for now.

As a side note: the user guide project is a really great idea, thanks for that!

SebCorbin’s picture

As one of the french team manager, I can confirm Vanessa is up to the task, and I'd like to have Git access as well.

jhodgdon’s picture

Great! I'll set up SebCorbin and vanessakovalsky as Maintainers this morning... will update issue summary when my tasks are done. Welcome all of you to the project!

  • jhodgdon committed 1a46527 on 8.x-2.x
    Issue #2835131 by jhodgdon: Set Up FR translation
    
jhodgdon’s picture

Issue summary: View changes

I've taken care of my tasks... also updated the Issue Summary to the latest version from
https://www.drupal.org/docs/user_guide_guidelines/pm-guide.html#pm-guide...
You might want to read through it. There were several clarifications that were not in the version you used (it was updated on drupal.org just after you made this issue).

Note that I did not use the above patch, so if you started translating files in that patch, you will need to commit your updates. However, I suggest that you have each translation reviewed, and commit each file's translation on the issue for that file -- so do step 6 (make all the issues) first, and then put up your translations as patches on those issues.

One other note: SebCorbin and vanessakovalsky -- see note in step 5 or 6 of the issue summary about Git access.

The rest of the steps are for you -- but let me know if you have any questions. When you do step 4 (making the screenshot issue), I'll be helping with that process as well.

Happy translating!

jhodgdon’s picture

Component: User Guide content » FR translation
vanessakovalsky’s picture

Issue summary: View changes
vanessakovalsky’s picture

Issue summary: View changes

All issues are now created, we can start to translate, I'll take care of last points to do during this week.

Happy translating to all :)

vanessakovalsky’s picture

Issue summary: View changes
jhodgdon’s picture

Just following up here... It looks like there is only one item in this issue that still needs to be done, and then it can be closed?

artusamak’s picture

Assigned: vanessakovalsky » Unassigned
fmb’s picture

I believe we're done with this issue, are we?

jhodgdon’s picture

Status: Active » Fixed

Looks like it!

Status: Fixed » Closed (fixed)

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