cPanel® Blog

Localization: x3 and Paper Lantern in 29 Languages

Greetings,

I am Phil King, Product Owner for the Angry Llama scrum team, which is actively completing our work to provide translations for cPanel & WHM. Ken Power summarized the localization project in a recent post.

I am pleased to announce that we have merged the 29 available translations into cPanel & WHM version 11.46. This work represents a great many changes to how we phrase things in x3 and Paper Lantern and standardizes on a more modern locale system.


Our legacy LANG system, while providing the potential for a translatable product, was truthfully too English-centric. Our earlier interfaces contained sentences that the system chopped up into several partial phrases based on English syntax. Now, we prefer to use phrases that form complete thoughts, which are considerably easier to translate. This also provides opportunities, not available in the legacy system, for translators whose languages read from right-to-left.

The legacy LANG database has been kept untouched and in place. Similarly, the software that looks up the translated value of a phrase is, for the most part, unchanged. In this phase of the project, we have removed usage of the legacy LANG system from the cPanel & WHM code base.

What does removal of our use of the legacy LANG system mean for you?

You need to examine your systems for use of the old style lookup keys. Sometimes these keys are called short tags. The following are examples of these old style keys:

  • ChangePassword
  • email_page_description_singular

A full list of old style lookup keys can be found in /usr/local/cpanel/lang and /usr/local/cpanel/base/frontend/x3/lang.

If you have provided your own custom translations, such as Slovak, using the old style lookup keys, they will no longer be used by x3 or Paper Lantern. Your users will only see English text. In order to function, you will need to convert your translations to the Locale Maketext format. You can translate phrases using the Edit a Locale feature in WHM.

If you have implemented old style lookup keys in one of the following ways, the correct text should continue to display:

  • Customizations of x3 or Paper Lantern
  • Custom applications that use old style lookup keys
  • Third-party themes that use old style lookup keys

A caveat with these implementations is if your users switch their language a newer locale, such as Korean. In this situation, they would see a mixture of English, from old style lookup keys, and the new language.

Visit https://rosetta.cpanel.net:2083/ to preview the translated x3 and Paper Lantern themes. We have created 29 different users that represent the available translations. Due to the nature of the demo mode, these accounts cannot be switched between x3 and Paper Lantern. To allow you to see both localized, we have created two accounts for each language. To login you can simply click the username that corresponds to the language (if you have issues with logging in, the password for the accounts is set to “localedemo”).

Use the following accounts to see x3 localization:

Use the following accounts to see Paper Lantern localization:

Please send all feedback about the new localizations to localization@cpanel.net. I encourage you to give us as much detail as you can; this will help us find and address any issues you might have before cPanel & WHM 11.46 ships to EDGE.

Thank you for your time,

Phil King

  • Manu

    Still lot of the text are in English. I hope you do the work and make it 100% translatable and also translate 100% of the English texts.

    • escherlat

      Hello Manu, we just receive the translations for 11.46. They should appear in builds after the first of the year. It took longer than we expected to get the translation done this time around. We’re working to reduce that time for future releases. During the period where we release the product and we receive the translations there will be English text in all the new, and modified, interfaces.

      There will always be a certain amount of English text in the interface. We must respect trademarks, for example. Thus MySQL will always appear as MySQL. The same with technical terms that are defined by standards, such as the SELECT SQL statement.

      • Manu

        Of course I’m not talking about translating words like MySQL or MySQL statements.

        I’m talking about regular text in cPanel interface. The new builds has not helped the situation. For instance most locale text that is in Javascript files is shown in English.

        Even though you advertise that you have done localisation in 29 languages, the translations are at least in some languages so bad that they are no better than what Google Translate does.

  • How can i email subscribe to the Day D when these languages become freely available to use in cpanel? PS i have a few czech language translation advices..

  • Monarobase

    While it’s better than before, the French translation is still is canadian French and not French French. Will we be able to fix this with the languages on github ?

    • Kenneth Power

      Do you have a style, or other, guide you can point us at? Our translation company assures us the translations are not Canadian French. Having something we could point to (beyond individual words) would be very helpful in clearing up matters.

      Yes, you will be able to submit your own fixes to the languages on github.

      • Monarobase

        Canadian French is close to French French, the main differences are words that are different or have different meanings.

        For example a “parked” car (or domain) in french is a voiture (ou domaine) “garé”, in canadian they use “parqué” instead of “garé”. While “parqué” exists in French it’s used for animals and not objects.

        Another word that sounds strange in the translation is “Redirecteurs” (e-mail forwarders), this word does not exist in French

        See here the french dictionary did not find it :

        http://www.larousse.fr/dictionnaires/rechercher?q=redirecteur&l=francais&culture=

        The previous translation “Renvois automatiques” was correct.

        Another one that I guess is Canadian :

        “Package d’hébergement”

        A french person would say “Formule hébergement”, package is very english.

        Another correction I submitted by e-mail when I had your preview :

        L’accès FTP a été octroyé avec le nom d”utilisateur.

        “octroyé” is very formal / old french, maybe still used in every day french in Canada but not in France. A French person would understand but probably smile at it as it’s proof that the translater doesn’t live in France.

        It should be :

        L’accès FTP a été autorisé pour cet utilisateur

        There are also a few mistakes that aren’t necessaraly from Canadian French

        For example :

        “FTP comptes” the words are in the wrong order and should be “Comptes FTP”

        Trace d’e-mail doesn’t mean anything in french either, as trace in this sense means mark or smudge. It should be more something like “Suivi d’e-mail”.

        Maybe this hasn’t been translated but “Marques de commerce” isn’t french either It sould be something more like “Utilisation de marques”

        “Définir ma langue sur” sounds bad to. Should be something like “Changer la langue”

        I haven’t read everything in detail yet but I haven’t noticed any other errrors in what I have read so it will be easy to fix on github if your translation company refuses to admin that their translater isn’t someone who was born or who lived in France.

        Hope this helps 🙂

        • Totally agreed with Monarobase, the french translation is so bad.. like in the WHM ‘Compte listes’ should be “liste des comptes”..
          A lot of errors in there translation.