Hi,
I localized SiteOrigin CSS, SiteOrigin Widgets Bundle, and Page Builder by SiteOrigin to Traditional Chinese (Taiwan), all of them are done.
The GlotPress Projects for SiteOrigin CSS and Widgets Bundle are updated, so I can submit all translations to the following URLs and users can receive localized files through WordPress Updates.
SiteOrigin Widgets Bundle: https://translate.wordpress.org/projects/wp-plugins/so-widgets-bundle
SiteOrigin CSS: https://translate.wordpress.org/projects/wp-plugins/so-css
Please notice, GlotPress project is so old for Page Builder by SiteOrigin, current strings are 428 items, but the old version strings are 325 on the following URL.
https://translate.wordpress.org/projects/wp-plugins/siteorigin-panels
This means users will receive incomplete translations for Page Builder even if this old translation project is completed.
Please update GlotPress project for Page Builder asap so that I can submit updated translations for Page Builder.
Thanks.
Regards,
Alex Lion
Hi Alex
Thanks for your thread.
I think we’ve found the issue in our build script. We’ll add it as a priority 1 issue on GitHub and get it completed ASAP.
Hi Andrew,
I don’t see any update for this plugin’s GlotPress project after two months, I am still waiting for this important update.
When its GlotPress is updated, I can submit Traditional Chinese (Taiwan) translations immediately.
Regards,
Alex Lion
Good to hear from you. We were just chatting about this issue this week and what might be the problem. Let me go find the commits.
The paths in the .pot file were pointing to the tmp folder which was incorrect. The date was also not printing correctly in the .pot file. We hope that one of these two will solve the issue:
https://github.com/siteorigin/plugin-build/commit/19bdbf3ba98d6ad94ee8be7a4c68eb1d42a09fd1
https://github.com/siteorigin/plugin-build/commit/aa6f67a8601404b0d7297bdab21b2a88f0db3b43
https://github.com/siteorigin/plugin-build/commit/6d8f3cba0ae7cbba52b43a98cd40890a87301e10
The next release of Page Builder will include these fixes made to the Plugin Build script. The team is offline right now but I’d guess next week for an update. I’ll reach out to you after the update to check how things are going. Thanks for your help :)
This bug still exists, there are 325 strings for the current GlotPress project of SiteOrigin Page BUilder, but the latest version contains 447 strings.
Hi Alex
Thanks for following up. As far as we’re aware, our only control over this is a properly formatted .pot file, is that correct? Can you see any issues with the updated .pot file that might be causing this problem?
If you encountered any WordPress I18N issue, asking the question on the official Slack channel may be a better way.
I am not a WordPress developer but I many friends who are WP developers. One of them told me you maybe read the following Codex doc to resolve current issue.
https://developer.wordpress.org/plugins/internationalization/how-to-internationalize-your-plugin/#text-domains
Thanks for that. We’re definitely up to speed on internationalization in our themes and plugins. Something unexpected is occurring here. I’ll re-open the issue with our developers, hopefully, they can find the problem.
Hi Alex, we’re looking at the translation issue again. There are 37 strings waiting to be translated at the moment if that helps.
Please, could you remove the links to your site and Facebook page found here.
Kindly remove the links to your site and Facebook page here too please:
Widgets Bundle
SiteOrigin CSS
1. Even if I translate the remaining 37 strings, translation package still doesn’t cover all
strings for current SiteOrigin Page Builder because there are 449 strings for version 2.8.1.
Please note, these remaining 37 strings are not used for new version either, this is why I don’t translate them.
2. The links you mentioned tell users who provide the localized version UI so that users can report typo or wrong translations to me. If you mind this, I already removed it but you are the first one minds this. If you don’t mind this, I will still add these two links again.
These new strings including two links are translated as the following.
Traditional Chinese (Taiwan) translations are provided by webmaster Alex Lion of Alex’s Classroom.
I think no Taiwan user confuses about this and think I am the developer for this page builder.
How can this be the case?
I think no Taiwan user confuses about this and think I am the developer for this page builder.
Your username was clearly on record as having added the string with links to your own site. That’s an unbelievable explanation.
The links you mentioned tell users who provide the localized version UI so that users can report typo or wrong translations to me. If you mind this, I already removed it but you are the first one minds this. If you don’t mind this, I will still add these two links again.
As an Editor you should realize this not ok at all. It’s spam.
All links are removed before I posted this.
You’ve done the same with other plugins: https://translate.wordpress.org/projects/wp-plugins/search-and-replace/stable/zh-tw/default
I only removed links from your plugins.
These links don’t increase my SEO, just let users report typo or wrong translations. Please understand I want to keep the translation quality.
Users need a link to your Facebook page to report translation issues? Again, that isn’t a believable explanation. GlotPress has a button for each string that says Suggest a new translation. That’s where users are meant to contribute, not on your site or via your Facebook page.
Actually, the most of Taiwan users don’t know what is GlotPress even if I make some public courses for these topics.
I will remove all links from all plugins and themes I localized, but the above fact is true.
There are about 100 projects I joined, this action will take some time.