785
edits
Changes
From SME Server
Jump to navigationJump to searchLanguage translation for Server Manager 2 in SME11 (view source)
Revision as of 06:36, 23 July 2024
, 06:36, 23 July 2024→Spotting untranslated messages
==== Spotting untranslated messages ====
==== Spotting untranslated messages ====
Untranslated messages are spotted by comparing the original English with the "translated" text. If they are the same, then the text has NOT been translated. The other situation that occurs is that when comparing the translated text in <modulename>_<language_code>.lex (imported from the smeserver-msanager-locale rpm) and the english text <modulename>_en.lex (which is imported in smeserver-manager rpm), then the key taken from the translated file does not exist in the English (original) file. I assume that the latter is due to the lex translated lex file being brought across from SM1 un touched whereas the english lex file has been editted to reflecxt which of the messages are actually in use by SM2. Incidentally all the lex files (from either rpm) are held in /usr/share/smanager/lib/SrvMngr/I18N/Modules/<modulename>. This difference is reflected in the placement of those files in the git repos smeserver-manager-locale and smeserver-manager,
So I wrote another program https://src.koozali.org/brianr/Lex2Po/src/branch/main/Check_Translation.py to spot the untranslated messages and also to delete in the "translated" lex filers the entries that do not appear in the english file. There were a few expcetions to this - ones dealing with time (AM, PM and AM/PM) and also the ones for some of the linux internals (cifs and nfs). These have been played back to the main git repos. Clearly we need to test all (or an many as we can) paths through all the SM2 modules to make sure we are not missing messages.
==== Other Anomalies ====
