ClassicPress 2.0.0 "Bella" Release Notes

I installed the public release version 2.0.0, but the Dutch translations are still being downloaded for 1.0.x - Dev. Several strings are now not being translated, such as the Previous and Next buttons.

I also noticed that “Discussion” has been translated to “Reacties”, not only is the translation plural instead of singular, but also incorrect. It should be “Discussie”. Because of this, there now seem to be two identical screen options. (See the enclosed screenshots).


Thanks for the report. Sorry about this.

Hi Tim,
Because I was curious, I took a look at the source code in /wp-admin/includes/translation-install.php. I noticed that the version /1.0.0/ is hardcoded on line 53.

As listed on Index of /v1/translations/core/1.0.0, these translations were last modified / updated on 21 November, 2023. Is that still the source?

I would really like to help out with the Dutch translations, but cannot find exactly were to do that.

I’m not sure about that. @elisabettac77 would know more.

Me thinks you are correct this are last sources uploaded. I am working with @MattyRob to get Crowdin all set and up to speed, will also check that hardcoded string to see if it’s better to make some amends to it. I personally would avoid hardcoded strings where possible but clearly Matt has the last word in it (there could be a reason for that in V1).

I am also working on an announcement and a tutorial to keep as reference for people who approach translating CP without prior knowledge of Crowdin.

Thanks for your help in localizing CP to Dutch!

2 Likes

@StonehengeCreations

The API server was rebuilt and migrated recently, the date on the translation zip files is when those files were uploaded to the new server. The last modified dates within the json file is a more accurate indication of the last time they were touched.

As Elisabetta has said, we are prioritising getting translation processes working on our side again. Hopefully that will be done very soon.

Ehm… I really hope that this is not true, because the dates in the JSON-file are much older.
nl_NL => 2019-03-06
pt_PT => 2019-03-27
ru_RU => 2019-01-29
All the others => 2018-12-20

@StonehengeCreations - those dates would indicate to me one of two things, either that id genuinely the last time the translation files were updated, or the dates were never changed with any update - either of those two are not good and I’m trying to work on a better solution going forwards. :grinning:

1 Like

I would like to think that the dates were never updated, so the current dates would then be their initial release date. :wink:

1 Like