Changes between Version 143 and Version 144 of ReleaseProcessDraft


Ignore:
Timestamp:
Nov 19, 2018, 10:27:35 PM (5 years ago)
Author:
Itms
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseProcessDraft

    v143 v144  
    106106
    107107=== Translation check ===
    108 '''Description:''' [[BR]] Check the translations for "vandalism". It's really just checking if there are any strings that were added in bad intent and not about trying to improve translation quality. There's a script to check the translation files for URLs ([source:ps/trunk/source/tools/i18n/checkTranslationsForSpam.py checkTranslationsForSpam.py]), but this task also involves manual checking. Obviously we can't carefully read through all strings in all translations. [[BR]]'''Can be completed in phase:''' Translation freeze [[BR]]'''Candidates:''' Whole team
     108'''Description:''' [[BR]] Check the translations for "vandalism" and syntax breakage.
     109* Against vandalism, it's really just checking if there are any strings that were added in bad intent and not about trying to improve translation quality. There's a script to check the translation files for URLs ([source:ps/trunk/source/tools/i18n/checkTranslationsForSpam.py checkTranslationsForSpam.py]), but this task also involves manual checking. Obviously we can't carefully read through all strings in all translations.
     110* Syntax errors can happen when translators incorrectly copy `sprintf` calls and special GUI tags. Most of the errors are detected by Transifex, but sometimes translators ignore the warnings. So we have [source:ps/trunk/build/jenkins/lint-translations.sh lint-translations.sh] which detects broken sprintf calls, but it doesn't detect broken GUI tags. So manual checking is still necessary.
     111[[BR]]'''Can be completed in phase:''' Translation freeze [[BR]]'''Candidates:''' Whole team
    109112
    110113=== Long strings check ===