Is your feature request related to a problem? Please describe.
In many cases (mostly in refactoring) nobody knows how to check the localization correctly.
Check msg catalog keys one by one and check the code if getCatString() use correct values cost too much time. Probably most of developers skip it and are then surprised on production site.
Describe the solution you'd like
As a QA engineer, I want to know
if all msg catalog keys are used
if all error codes from msg catalog are used
if getCatString() use existing key
if makeError() use existing error code
if msg keys (or error codes) are provided in all languages
Furthermore consider new language handling since WinCC OA 3.20.
Describe alternatives you've considered
N/N
Additional context
Highlight will be to use hunspell or something like that to check if the translations are correct. It works for many languages and it is open source too. So it should be no problem to use it here for free too.
Is your feature request related to a problem? Please describe. In many cases (mostly in refactoring) nobody knows how to check the localization correctly. Check msg catalog keys one by one and check the code if getCatString() use correct values cost too much time. Probably most of developers skip it and are then surprised on production site.
Describe the solution you'd like As a QA engineer, I want to know
Furthermore consider new language handling since WinCC OA 3.20.
Describe alternatives you've considered N/N
Additional context Highlight will be to use hunspell or something like that to check if the translations are correct. It works for many languages and it is open source too. So it should be no problem to use it here for free too.