cPanel 106 removes almost all translations
-
Behind the scenes, we've been working on our localization system to enable 100% translation coverage, including complex strings that were never previously translatable. After completing that work, we are now contracting with professional translators to complete the supported languages you listed and entirely re-translate a handful of more languages, French included. While I can't give an ETA on the replacement translations, please know that we're working to minimize that time as best we can. In the interim, you can restore the previous French translation by downloading and installing them from GitHub - CpanelInc/cplocales: Locales for cPanel & WHM. 0 -
Why did you need to remove all old translations? Was it not possible to keep old ones until the new ones are ready? 0 -
Hope you revert this situation. You should only remove the old translations when you have the new ones ready. What you are doing doesn't make any sense... 0 -
I agree. Removing something because you plan to improve it later doesn't make any sense. Why not keep the current translations (however terrible some of them might be) and then replace them once you actually have something to replace them with? I can't believe that decision was made by a team. It must've been made by a single person, without ever being mentioned to anyone. Had that decision been mentioned just once, someone from cPanel would surely have asked: "But why?" 0 -
All translations that were removed suffered from a number of problems, including lack of completeness (some as bad as 0%), terrible quality, rampant inconsistency in terminology, and string corruption. Some of those languages were found to have translations for strings we no longer have in the product as well, further complicating our understanding of coverage. The decision was made to remove them entirely in order to stop "over-promising" the support we offer. In my opinion, providing a bad experience is worse than declaring, if temporarily, that we don't provide an experience at all. The languages that remain were actively updated since the pandemic and, upon completion, will cover ~85% of our detectable userbase. ( on your servers to help us detect more of our user-base and update our understanding.) We also have enabled end-users to tell us directly what languages we should translate into with an in-app survey found wherever languages are listed throughout :2083 and :2087. To get that ~85% number beyond 95%, we are pursuing translations into Portuguese (which itself would jump the support to 90%), Turkish, French, German and Indonesian. Based on preliminary results from v106's in-app survey, we may add Arabic and Chinese to that list. 0 -
Please, make sure you include pt_PT and not only pt_BR. 0 -
Some of those languages were found to have translations for strings we no longer have in the product as well
Didn't the English language include strings that were nowhere to be found as well? I started translating cPanel and used the English language as a template. There were a lot of strings that I had never seen before. Why not provide system administrators with an option to manually add the removed languages? A few customers will prevent us from being able to upgrade. They're old and don't know much English. They've used the Danish translation of cPanel for years and that was fine for them, even though it had a few (very few) issues.0 -
It"s not possible to enable cPanel"s interface analytics program for countries in the EU because of GDPR. All big companies in the EU will probably have it disabled by default. Especially as it also makes user experience for non English users worse by asking them to accept a text en English. 0 -
Please, make sure you include pt_PT and not only pt_BR.
Can do, though please understand that pt_PT may not be first out of the gate. I do see pt_PT users in the analytics we are referring to when generating the list.0 -
It"s not possible to enable cPanel"s interface analytics program for countries in the EU because of GDPR. All big companies in the EU will probably have it disabled by default. Especially as it also makes user experience for non English users worse by asking them to accept a text en English.
We understand. Participation is totally optional. We also survey (both from our newsletters, direct conversation with customers/partners, and now in the product UX) so that we can learn from there as well.0 -
Didn't the English language include strings that were nowhere to be found as well? I started translating cPanel and used the English language as a template. There were a lot of strings that I had never seen before. Why not provide system administrators with an option to manually add the removed languages? A few customers will prevent us from being able to upgrade. They're old and don't know much English. They've used the Danish translation of cPanel for years and that was fine for them, even though it had a few (very few) issues.
You can indeed manually restore the removed languages, if you'd like to do that. Instructions are0 -
I think the best option would be to use a tool like Weblate to allow translations to be open and created collaboratively by cPanel users. I already helped translate many software in the last years and that would allow us to contribute and accelerate the availability of those languages. 0 -
It's a shame to remove everything and then put it back, it would be better, as the dear colleague above said, for the community to help in a collaborative way for the translation, than to remove everything and not have anything translated into Brazilian Portuguese or from Portugal. cPanel is not a new platform, it's something old and mature to make a drastic change like this. 0 -
This change is causing some concern, for example: PT_BR even though the current translation is deficient, it makes no sense to remove 100% I believe the approach should be correction before removal. cpanel is unfortunately ignoring its community once again. These unilateral decisions are having negative impacts on their clients' operations. It would be much more valid to open votes injected within the cpanel itself so that the user himself will decide which decisions will be more useful. 0 -
Please add the Ukrainian language to the survey. In our country, according to the law, all interfaces must be in Ukrainian. 0 -
simply, soon they will start charging for the language we need, just like plesk 0 -
@UAhosting - noted! @tpmpropaganda - definitely not something we are planning. 0 -
@cPRex Not sure if it's necessary given you have already mentioned you are working on French, but it might be a good idea to add it to the survey as well. 0 -
Oops. I also missed that information prior the update from my side. I did not get any notifications by updating to v106 about the removal of the French for instance" or it was not obvious at the first time for me ? However, I read carefully the big update notices after each cPanel updates, but I should probably read better the b"ta release notes. Globally, that was nice to will remain without their favorite languages for a while, before discovering the easy workaround here (not all "End-User" report missing languages and just think their provider switch to english panel). If possible to get more communication for updates which makes consequences on our customer service and reputation please! It would be perfect :) Long life to Jupiter! 0 -
@nlaruelle - I'll let the team know! 0 -
@nlaruelle - it looks like we did include a notification about this in the WHM "Feature Showcase" area as part of the update to version 106: 0 -
@nlaruelle - it looks like we did include a notification about this in the WHM "Feature Showcase" area as part of the update to version 106: alt="Screen Shot 2022-09-12 at 9.40.12 AM.png">79481
It's curious, but I probably missed it so, my mistake. Thanks again! :)0 -
There's a lot on that page for sure. I just wanted to let you know we did say something, even it wasn't very obvious. 0 -
All translations that were removed suffered from a number of problems, including lack of completeness (some as bad as 0%), terrible quality, rampant inconsistency in terminology, and string corruption. Some of those languages were found to have translations for strings we no longer have in the product as well, further complicating our understanding of coverage. The decision was made to remove them entirely in order to stop "over-promising" the support we offer. In my opinion, providing a bad experience is worse than declaring, if temporarily, that we don't provide an experience at all. The languages that remain were actively updated since the pandemic and, upon completion, will cover ~85% of our detectable userbase. ( on your servers to help us detect more of our user-base and update our understanding.) We also have enabled end-users to tell us directly what languages we should translate into with an in-app survey found wherever languages are listed throughout :2083 and :2087. To get that ~85% number beyond 95%, we are pursuing translations into Portuguese (which itself would jump the support to 90%), Turkish, French, German and Indonesian. Based on preliminary results from v106's in-app survey, we may add Arabic and Chinese to that list.
You refering for this survee: Customer Language Preference ? Its not listing even all languages what was in cpanel before v106...0 -
yes, that's the right survey. Which languages are you expecting to be on the list? 0 -
yes, that's the right survey. Which languages are you expecting to be on the list?
Hello, Is there a forecast to make the language "pt_br" available in versions (104 e 106) of cPanel? Thanks0 -
I've just voted for French, as French wasn't in the list at the beginning but is now. Are you lacking translation firms for certain languages ? We woud love to put you in contact with a good translator for English to French 0 -
@ldxsant - I would say that's one of the highest priority languages on our list at this time. @monarobase - I've let our UI team know! 0 -
Why did you need to remove all old translations? Was it not possible to keep old ones until the new ones are ready?
Removing things and then making us beg through the Feature Request system to get them back is the way.0
Please sign in to leave a comment.
Comments
29 comments