-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve kind views for i18n #211
Comments
I did some thinking... 🤔 For example. Here are some simplified sentences to show the issue if we want proper localization.
As you might notice, the English verb at the beginning is split across the sentence. Unfortunately, the plugin provides some variations in the output:
To support translation for any possible variation, each view kind should have one translatable Wouldn't this mean adding a lot of complexity and redundancy to the plugin? What do you think? |
the translations would have to be littered with markup for it to work effectively :/ |
This is also a duplicate/extension of your last issue, #205 |
I'm willing to entertain suggestions on how to address it best. I don't mind rearranging the logic if it helps with that, but to @Ruxton 's point, I'd like to not make the code too confusing for people. |
I noticed that some of the code in the views that will eventually can be localized is split up into chunks with multiple
_e()
statements. This makes it hard if not impossible to properly translate these texts.The other day I read the i18n/l10n handbook and I want to check the plugin code against these recommendations.
indieweb-post-kinds/views/kind-like.php
Line 41 in eaa62f4
I will have a look and submit a PR. Initially with 1 example open for discussion. Then if we agree on how to approach this, I will add more commits for the other views.
The text was updated successfully, but these errors were encountered: