This object is in archive!
Broken locale after migration to new translating system (cpaenl 11.42)
Completed
Hello,
we have communication with cPanel support on ticket ID 4717101 that in new system you change some Keys in locale and then they direcly go in English ,because can't be catched in locale file.
Can you please check ticket and make new Keys to be same as Old keys.
It will help to back correct translation, many users of using different languages of cPanel will be happy.
Thanks.
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
This is a side effect of the slow but steady conversion from our old/former localization system to our newer and more robust localization system. In the context of our features we discuss at cPanel, it would be moving from the old "LANG/Short Tag" system to our new "Locale" system.
There isn't a way for us to mitigate this behavior where custom languages that cPanel users custom write themselves that rely upon the older localization system will be unaffected.
The best way I can advise handling this is testing out new releases on a testing server/non-production system to see what the locale changes are before you upgrade your server to them. That will give you the time needed to review and change your custom localization to accommodate with any changes.
This is a side effect of the slow but steady conversion from our old/former localization system to our newer and more robust localization system. In the context of our features we discuss at cPanel, it would be moving from the old "LANG/Short Tag" system to our new "Locale" system.
There isn't a way for us to mitigate this behavior where custom languages that cPanel users custom write themselves that rely upon the older localization system will be unaffected.
The best way I can advise handling this is testing out new releases on a testing server/non-production system to see what the locale changes are before you upgrade your server to them. That will give you the time needed to review and change your custom localization to accommodate with any changes.
This is a side effect of the slow but steady conversion from our old/former localization system to our newer and more robust localization system. In the context of our features we discuss at cPanel, it would be moving from the old "LANG/Short Tag" system to our new "Locale" system.
There isn't a way for us to mitigate this behavior where custom languages that cPanel users custom write themselves that rely upon the older localization system will be unaffected.
The best way I can advise handling this is testing out new releases on a testing server/non-production system to see what the locale changes are before you upgrade your server to them. That will give you the time needed to review and change your custom localization to accommodate with any changes.
This is a side effect of the slow but steady conversion from our old/former localization system to our newer and more robust localization system. In the context of our features we discuss at cPanel, it would be moving from the old "LANG/Short Tag" system to our new "Locale" system.
There isn't a way for us to mitigate this behavior where custom languages that cPanel users custom write themselves that rely upon the older localization system will be unaffected.
The best way I can advise handling this is testing out new releases on a testing server/non-production system to see what the locale changes are before you upgrade your server to them. That will give you the time needed to review and change your custom localization to accommodate with any changes.
Replies have been locked on this page!