PRO translations

[referee]

Hi,
I would like to wonder whet the PRO was checked last time for translation strings references? I tried to create translation from existing .pot file inside /pro/framework/lang/ but it turned out that that quite a few strings are missing in it (I used Loco Translate). Then I used PoEdit to scan PRO folder for all strings. I’ve got almost twice strings in this case comparing to the first scenario. However, the strings which appeared inside .po file after second scenarion turned out to have a bad reference. So I tried to translate them inside PoEdit but these translations didn’t apper at the site.

Here are just some examples.

[christian]

Hey @imdyakov,

Yes, they’re not in the pot file. You need to translate them by other means including filtering gettext.

Also, note that they’re using cornerstone Text Domain.

Hope that helps.

[referee]

Thanks for confirming that.

Are there any plans to update translational strings inside PRO within coming releases?

[tristup]

Hi @imdyakov,

Regretfully, there are no such plans to translate those within upcoming releases of the Pro.

Thanks for understanding.

[referee]

@tristup that’s a pity but understandable of course. I hope that it will be done later this year.

[alexander]

Hi @imdyakov,

I’m sorry for the confusion here, we’re actually in the process of auditing our codebase to properly localize things. We regretfully missed a few cases like what you’ve discovered in the Pro 4.0 update. These will be fixed and made translatable. Admittedly it’s been a challenge to make translation accessible because of how a massive part of the codebase is shared between Cornerstone and Pro. Technically speaking Cornerstone is embedded in Pro so we’re juggling two text domains and there is room for improvement on how that is organized.

I’m not sure when it will be finalized, but as early as 4.1 or 4.2 we’re going to be reorganizing how some of the text domains are setup. There will likely be a new admin/backend text domain to localize things that are inside the builder like navigation items and text controls. Regretfully it means that some of the translation work you have already done may need to be updated. However, we’re hoping to create a better foundation for keeping localization accessible moving forward as both Pro and Cornerstone evolve and grow.

Thanks for your understanding here!