Revamp internationalization section

Review Request #807 — Created July 12, 2021 and submitted

sorvival
pidgin/nest
default
NEST-33
e00da269926b
pidgin-www
- Adapt the contents of the tips for i18n page into the main
  internationalization one.
- Change reference from tipsfortranslators to the internationalization page in
  the about->supported languages page.

Ran dev-server.sh and verified content looks as intended.

  • 0
  • 0
  • 7
  • 1
  • 8
Description From Last Updated
sorvival
  1. 
      
  2. I'll need help from senior Pidgin project members specially on the How translations go from Transifex to Pidgin section of the Internationalization page.

    Particularly I'm looking for feedback here as to what the wording should be, since I believe that even if notifying translators about an upcoming Pidgin release I don't think we've been following that guideline lately, and I don't know if we necessarily want to and this was just an old guideline that stopped being followed.

    1. Sort of disregard this comment, since I noticed that the string freeze is also detailed in the release-process page so I'll just link to it in the Internationalization page so that we follow DRY.

  3. 
      
sorvival
grim
  1. 
      
  2. hugo/content/development/i18n/_index.md (Diff revision 2)
     
     

    Use they wish instead of he/she wishes there's no need for gender specific pronouns here.

  3. 
      
sorvival
rekkanoryo
  1. 
      
  2. hugo/content/development/i18n/_index.md (Diff revision 3)
     
     

    This would read better if it was everything between "the globe" and "so having" was replaced with a comma (so "across the globe, so having...")

  3. hugo/content/development/i18n/_index.md (Diff revision 3)
     
     

    Change "strings of this" to "strings for this" so it reads better

  4. hugo/content/development/i18n/_index.md (Diff revision 3)
     
     

    I'd rephrase this as "translating Pidgin and has notified the Pidgin Developers" so that it sounds better.

  5. hugo/content/development/i18n/_index.md (Diff revision 3)
     
     

    Shouldn't these two paragraphs be not indented?

    1. I left them indented because both paragraphs are related to the item "Translation updates for each language are accepted only from its current translator, except when[...]". The first paragraph is the explanation of why this is handled this way and the second one is providing a way to contact the appropiate team in case someone thinks one of the items under "except when" is being met.

    2. How are they presented when rendered?

    3. This is how it looks with the paragraphs indented:

      Image

      This is how it looks without the paragraphs indented:

      Image

    4. Okay, this makes much more sense. Dropping the issue, I think we're good to merge here.

  6. hugo/content/development/i18n/_index.md (Diff revision 3)
     
     

    I'd rephrase this as "that no strings will be added or changed" to make this read a little more clearly.

  7. 
      
sorvival
ivanhoe
  1. 
      
  2. hugo/content/development/i18n/_index.md (Diff revision 4)
     
     

    looks like there's a word missing here (find a evaluate it)

  3. 
      
sorvival
rekkanoryo
  1. Ship It!
  2. 
      
grim
  1. Ship It!
  2. Awesome work! Thanks!!

  3. 
      
grim
  1. 
      
  2. Landing this is causing merge conflicts, can you rebase?

  3. 
      
sorvival
grim
Review request changed

Status: Closed (submitted)

Loading...