Yeah, seems that upload of files (despite it clearly suggests that this is how you upload existing translations, even if for example someone wants to work locally and then upload…) does not work.
What I thought… to press the “pre translate” button.
Because I have seen in the activity logs you did that a couple times in past, so perhaps if I press that, it will at least do some translations even if perhaps not pull the ones from po file, it will machine translate them?
Can I ruin anything by pressing that button?
I think we can always “undo”, as far I saw in the activity log.
I am trying to chat with support now there to get more clarity, before I proceed…
I wouldn’t do that. I don’t remember doing that in the past either. I would expect the resulting translations to be terrible.
I’m not sure why uploading translations didn’t work for you (and in fact, it looks like I would be able to upload a .po file). Still, I am doing it another way: by resetting the GitHub integration with the new language file in place. This needed to be done anyway since it was no longer pushing new translations to GitHub.
They say PO should work and yet it does not. They could not resolve the issue and forwarded the problem to email for further check.
@James - I guess whatever you wanted to … will be faster than waiting for them. Yet I will be eagerly awaiting their resolution so we can do that on our own in future…
PS they also recommended to use WPML to translate “our site”
Fun times.
That is weird. Me gets an error only XLIFF being supported…
I will update support about this status (because since 100% Indonesian is translated, de facto it should show that, I think)
I guess its progress, still, as compared to before. @steamboatid I suggest you hold on with doing anything there yet.
Then under Admin, there is one more sub-project for Network Admin.
I uploaded these other files and got the translated strings up to 78%, which should be higher - around 90-95% - the difference is that many of the WP strings and translations that say WordPress should actually say ClassicPress. So I created separate copies of the .po files to correct for this (just replaced all instances of WordPress with ClassicPress), and then re-uploaded.
For new languages we can download all 4 of those translation files from GlotPress, create copies of the .po files that have WordPress replaced with ClassicPress, and upload all 8 files at once (we need the original 4 also, since some of those strings will still say WordPress). Here are the settings used. The only change from the defaults is to check the box to import strings that do not change when translated, like city names:
Now we are up to 94% translated for Indonesian, and these are steps we can repeat for other new languages. (I still don’t think we should add new languages without a bit more consideration though, we should focus on making the existing ones fully working first.)
I think this may not be correct. Can you post an example?
Please follow the instructions at Approving and cleaning existing strings on Crowdin before doing any more translations, and let us know when you’ve done that. This will make sure we can tell the difference between WP translations and your new ones, otherwise we can’t review your new translations separately.
These are correct and need to be left as WordPress.
We need to get all the existing strings from WordPress cleaned up and approved first, that is the reason the steps at Approving and cleaning existing strings on Crowdin need to be done first. Then we will be able to review your new translations separately.
Plugins extend and expand the functionality of ClassicPress. You may automatically install plugins from the <a href="%1$s">WordPress Plugin Directory</a> or upload a plugin in .zip format by clicking the button at the top of this page.
that another one. because CP also have plugin directory
Yes, of course. We are very clear about where security fixes come from. These strings apply specifically to the About page when we upgrade ClassicPress to include everything from newer WP 4.9.x versions.
This is correct. There are a lot of other threads here about the ClassicPress plugin directory.
Also, a couple of general rules when you think there is an issue with a translation:
Look at the code where the string appears, and make sure you understand the context of the source string. Just saying “I think this should / should not say WordPress” is not right.
