-
Notifications
You must be signed in to change notification settings - Fork 125
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 i18n #99
Comments
PR #101 cleans up _n(). |
Some strings in gp-templates/project-permissions.php would be impossible to be translated into some languages. (For example, Japanese.) |
Could you provide an example of what can't be translated? Items like the slug, username, login id, etc. aren't translated as they shouldn't be. |
@toolstack: Japanese has quite different sentence structure. In this case, word order is the problem. Here's an example:
|
See also https://github.com/deliciousbrains/GlotPress/pull/198 Merge similar strings with different variations and avoid using HTML |
Hi @ocean90 I have some suggestions to improve i18n. |
Hi @ocean90,
Did you mean the There are also these two, that I believe you weren't refering to: |
Previously: #16
_n()
is wrong in some cases, like_n('One translation rejected.', '%d translations rejected.', $ok, 'glotpress' ), $ok );
__( 'edit', 'glotpress' )
should get a context:_x( 'edit', 'glossary', 'glotpress' )
esc_attr( __( ) )
should beesc_attr__( )
echo _x( )
should be_ex( )
Note: Each point can have its own PR.
The text was updated successfully, but these errors were encountered: