Hi,
In my CP 2.3.1 install I can choose between a couple of languages (English (US), English (UK), Deutch, etc). I’m missing Dutch (NL), but from various threads I get the impression there’s a (partial) translation available. At least for v1 of CP. If it is available, where can I find it?
Guido
@ElisabettaCarrara I’m sure you know most about this.
@timkaye & @Guido07111975 fact is that for now we aren’t releasing not completed locales.
We are trying to bring what we have up to speed and we release the completed ones as soon as they are.
This means that technically there is not a Dutch translation available for now yet, unless some Dutch mother tongue volunteers in completing it on Crowdin.
That said I was thinking about proposing a slight change to our workflow, allowing us to release the unfinished locales.
This would achieve the following:
I need to understand however if this is technically possible with how we are set up now, and if the community really thinks this change would benefit us in the way I envision.
@MattyRob pinging you here to evaluate if the CP release process can include partial localization releases since it is different from what WP does
If it’s technically feasible, I agree that releasing partial translations would be a good idea.
Are strings actively being translated into Dutch, at the moment?
How much is translated?
I have translated quite some strings for WP, not my hobby, but am willing to step in, if there’s a need for Dutch translators.
Guido
Thanks for volunteering to help with Dutch and welcome onboard!
At the moment we do not have a Dutch localizer actively working on them.
Dutch locale is 70% translated and 0% approved.
We use Crowdin to localize (this is an invite link expiring in one week to join the localization team there).
These are some tutorials to get you started with it:
How to localize CP
How to deal with weird thing in translations
Approving and cleaning existing strings on Crowdin
There is an issue with date formats in some places that I am still investigating because Crowdin seems to be unable to convert the destination date format to the correct PHP format to render via the tag. That should not be concerning however since when I am able to figure things out I will apply the eventual fix on all affected locales.
If you have any questions about Crowdin and localization feel free to ask.
One of the things we have briefly discussed is having a translation API endpoint specific to the ClassicPress version. This would allow release specific translations and even incomplete translations for each new core release.
It has two disadvantages though. It makes the release process a little more involved and lengthy. And with the way the core code currently works, if the translation files were updated they would only be automatically updated with the next core release. (Manual updates would be possible of course via FTP)
@MattyRob So if I understand correctly the current approach of CP is that translations are manually added to the CP-zip, each release? And between releases of core, no translations are added automatically?
@Guido07111975 basically locales get to be released only when completed as of now and have a separate release process handled directly between GitHub and Crowdin (the short description is Crowdin puts the completed locale in a i18n repo that then pushes a PR to CP).
What I would like to achieve is more of a “rolling” model where locales gets released whenever there is a change in them (for example a locale that is 80% translated get updated to 95% translated, still a partial locale but the update gets released).
As Matt mentions however to do this we would have to make the whole process slightly different and trickier/with more steps.
That is why between end Jan and early Feb I want to discuss things during a meeting in the i18n in Zulip with all the localizers and someone of the core team. We need to decide knowing what we are going against…
That’s not quite the way it works. The translation files are not bundled with the release but are made available via an API that defines what translations are available and provides the download zip links.
There are limitations on the core code though that translations files can be versioned or updated within a release of the core code.
Hello. I can try to help with the Ukranian translation, but don’t see this option. Also do really ClassicPress has so much unique strings, that differ from WordPress?
Also do really ClassicPress has so much unique strings, that differ from WordPress?
Yes, because in many strings “WordPress” is replaced by “ClassicPress”.
For Dutch translation I have done this in Crowdin:
You will need time for this.
Guido
Thank you for suggestions. If team will create Ukrainian translation in Crowdin, I will try to create one.
Will check if there is the Ukrainian locale and give you access later today.
Thanks for volunteering!
Hi,
I have finished the Dutch translation 
Hopefully shipped with next CP version.
I have used the WP-translations as much as possible.
Have found a few mistakes in core strings (misuse of ClassicPress for example), but will open a seperate thread for that.
Guido
@ElisabettaCarrara / @MattyRob
I have added my translation to my local CP-install. But which file I need to edit to make the translation selectable at page Settings > General?
This is better answered by @MattyRob but I believe there is somewhere a file that should list the available locales in an array. I am going to see if I find it.
I think the one you need to check is wp-admin>translation-install.php
I could be wrong but this handles translation packs.
Another place to look into is wp-includes>i10n
Thanks, will try that tomorrow.
Guido
The API will need an update. I’ll try to look tomorrow.