TurboPT wrote:Look down in the locale/ directory for your language.
READ the text found in the 'custom_strings.txt.example' file.
The default strings will be found in the strings.txt file, and then the same default variable can be overridden in the custom_strings.txt file to match what you need.
As I found, that would not work.
The root cause - TL developers modify strings.txt only while adding new $TLS_ constants.
Yet, I have found a solution
Here is information for Russian, yet it is do applicable for all languages.
I have found that files strings.txt and texts.php in folders en_GB and ru_RU are not the same!
As a result, even if I take all not translated texts from locale/ru_RU/strings.txt, put them into locale/ru_RU/custom_strings.txt (as I did) and translate, I will have lot of untranslated UI elements still.
Fortunatelly for me and my team, I did compare for locale/en_GB/strings.txt and locale/ru_RU/strings.txt, found LOT OF missed in locale/ru_RU/strings.txt definitions for UI elements, copied them into locale/ru_RU/custom_strings.txt and did translation.
Now I have much more better translated to Russian UI for TestLink 1.9.11.
As of the reports titles, here are the items you have to add to your custom_strings file and define translation(s):
// printDocument.php
$TLS_report_test_plan_design = 'Test Plan Design Report';
$TLS_report_test_plan_execution = 'Test Plan Execution Report';
$TLS_report_test_plan_execution_on_build = 'Test Plan Execution Report (on specific build)';
$TLS_execution_time_metrics = 'Execution time metrics';
$TLS_gen_test_plan_design_report = 'Generate Test Plan Design Report';
$TLS_right_pane_test_plan_tree = "Click to display Test Plan Tree (on right pane)";
$TLS_display_tsuite_contents = "Click to display Test Suite Contents (on right pane)";