Changes between Version 130 and Version 131 of ReleaseProcessDraft

Timestamp:

Apr 24, 2018, 11:06:18 AM (6 years ago)

Author:

Itms

Comment:

Add a step for checking the long strings once the translations are ready

ReleaseProcessDraft

@@ -42 +42 @@
 || [wiki:ReleaseProcessDraft#Confirmtranslationfreeze Confirm translation freeze] || Itms ||  ||
 || [wiki:ReleaseProcessDraft#Translationcheck Translation check] ||  ||  ||
+|| [wiki:ReleaseProcessDraft#Longstringscheck Long strings check] ||  ||  ||
 || [wiki:ReleaseProcessDraft#Updatetranslatorscredits Update translator credits] ||  ||  ||
 || [wiki:ReleaseProcessDraft#PackageEastAsianmods Package East Asian mods] || Itms || ||
@@ -97 +98 @@
 === Translation check ===
 '''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
+
+=== Long strings check ===
+'''Description:''' [[BR]] Run the script that deletes the translations that won't be packaged, then run the script that generates the so-called [https://trac.wildfiregames.com/wiki/Implementation_of_Internationalization_and_Localization#LongStringsLocale long strings locale]. Go through as much parts of the GUI as possible, and see if some parts should and can be tweaked. In case the fix needs to break Translation Freeze, create a ticket for the next release. [[BR]]'''Can be completed in phase:''' Translation freeze [[BR]]'''Candidates:''' Whole team
 
 === Update translators credits ===