[CA] Tradueix aquest fitxer preface-organization.txt

First approach for the translation.

Sorry, it needs review first.

1. +++ b/source/ca/preface-organization.txt
   @@ -1,36 +1,39 @@
   +Potser també voleu remetre-us a la secció del <<glossari>> a mesura que llegiu -
   

   This is incorrect.

   Anything in these << brackets is a link to an ID, and the IDs cannot be changed. So this needs to say <<glossary>> without glossary being translated into Catalan.

   I will fix it because this has broken the build scripts, but please check this in other translations.

2. +++ b/source/ca/preface-organization.txt
   @@ -1,36 +1,39 @@
   +Escrit per https://www.drupal.org/u/jhodgdon[Jennifer Hodgdon].
   

   Also you can add attributions to topics for the translators. So it would say something like:

   Written by Jennifer Hodgdon. Translated by ..... etc.

   See
   https://www.drupal.org/docs/user_guide_guidelines/practicalities.html#pr...
   https://www.drupal.org/docs/user_guide_guidelines/phase-checklists.html#...

   For the project managers:

   Is attribution provided? You will need to add attributions for the translator and reviewer to the bottom of the file. Note that the attributions for the glossary are located in the main attributions.txt file and cannot be added to the glossary.txt file.

Great! I do not expect this to be the last time this happens for a translation. :) It is not difficult to fix, anyway, and now that you know to look for it, that will be good.

By the way there is a checklist you can use to make sure everything happens in a translation issue:
https://www.drupal.org/docs/user_guide_guidelines/phase-checklists.html#...

It was supposed to be part of the issue template, so it would be there for translators and committers on each issue, but unfortunately when you use URLs to create issues (as we're doing for the translation issues), the issue summary is limited to I think 255 characters, so this template got left out to save space.

Anyway, you might want to refer to it when you make commits. We had similar checklists during the writing/editing process and I personally found them to be very helpful so that I remembered to verify/do everything when committing.