Line 151:
Line 151:
==== Testing the language translations ====
==== Testing the language translations ====
−
The latest smeserver-manager is version 11.0.0-10 and the smeserver-manager-locale is at 11.0.0-4. Note that in the latter case you have to load each rpm for each language. If you are on earlier version then the menu is not correctly translated in many cases.
+
As at 27july2024, The latest smeserver-manager is version 11.0.0-10 and the smeserver-manager-locale is at 11.0.0-4. Note that in the latter case you have to load each rpm for each language. If you are on earlier version then the navigation menu is not correctly translated in many cases.
−
This works:
+
This should work:
`dnf update smeserver-manager-locale-*`
`dnf update smeserver-manager-locale-*`
+
+
and
+
+
`dnf update smerver-manager`
Using the Chrome or Chromium browser, there is a plugin called "Locale Switcher" which will allow the browser locale to be switched into whatever language you choose. This can then be used to test each language translations.
Using the Chrome or Chromium browser, there is a plugin called "Locale Switcher" which will allow the browser locale to be switched into whatever language you choose. This can then be used to test each language translations.
−
No translations have complete coverage , so testing each one will result in anomalous messages.
+
No translations have complete coverage , so testing each one will result in anomalous messages, remeber to look at the left navigation menu as well as the panel text.
So, go through as many of the SM2 panels as possible in each of the languages and spot situations where the message has not been translated (and is in English) OR shows the message ID rather than the translated OR where the translated text has html in it which is not being interpreted. This screen shot demonstrates what I mean:
So, go through as many of the SM2 panels as possible in each of the languages and spot situations where the message has not been translated (and is in English) OR shows the message ID rather than the translated OR where the translated text has html in it which is not being interpreted. This screen shot demonstrates what I mean:
Line 173:
Line 177:
−
In this case its looks as though the button text does not match the equivalent id in the .lex files (this will require a change to the template files or more likley to the lex file(s).
−
In some cases the Message Id in the translation file does not match the Id used in the Code. Html has to b e passed through Mojolicious specifically so we need to wrap a routine around that message in the code. Please log any anomalies.
+
+
+
In this case its looks as though the button text does not match the equivalent id in the .lex files (this will require a change to the template files or more likely to the Turkish lex file(s). These may be similar errors in other files.
+
+
In some cases the Message Id in the translation file does not match the Id used in the Code. Html has to be passed through Mojolicious specifically so we need to wrap a routine around that message in the code. Please log any anomalies.