Opened 12 months ago
System applications names hardcoded in strings make Locale settings non-consistent when user ask to not translate them
|Reported by:||TheClue||Owned by:||nobody|
|Has a Patch:||no||Platform:||All|
The user can have Sytem Applications and Folders translated into her local using the 'Locale' preflet.
But many often, application mames are hardcoded into the catkeys and are not aware of the preflet settings. For example, in Network Status:
You can run NetworkStatus in a window or install it in the Deskbar
This make non-consistent behaviour to users than could read both the translated/untranslated versions, depending on how the catkeys was handled by the translation teams vs her Locale settings.
This is also true to applications referencing other applications in strings (not often, but it happens. A typical example is the Installer and Drive Setup in EULA)
I think that the application names should be dynamic parameters in text and being aware of Locale settings
You can run %s in a window or install it in the %s
Related to #10387