-
Notifications
You must be signed in to change notification settings - Fork 28
Translations improvement / Added German translations #23
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
Conversation
|
Yes, Gary, it matters on this area: in load_ functions the unique id string is needed, otherwise it can under some circumstances pull an "random" id from plugin slug etc. also added domain path to plugin header, --> you only need to remove the "old" .pot file "blazer-six-gist-oembed" |
|
Codestyling Localization plugin has no more error messages with my changes included. Thanks, Dave :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should "Raw Key" have been left in the translation here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe, don't know how to properly handle this in other languages like German, seems like a special term, and I should change it back - thanks for the feedback :)
|
Can you please also pull against dev branch, rather than master? Thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does plugin_dir_path() not give the same result as dirname(plugin_basename())?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, does not work - had this with lots of other plugins already, only the change brings it to work.... "load_plugin_textdomain()" requires relative path depending on plugin dir, maybe plugin_dir_path() is absolute or one level to high? It just does not work...
|
Just pulled/pushed in dev branch again and made 2nd pull request, also with your suggested changes/corrections |
|
Closing in favour of merged #24. |
No description provided.