I wouldn’t try to localize your slugs. Instead, why not give your users the option to change them by adding another field to the permalink settings page? Hook into load-options-permalink.php and set up some things to catch the $_POST data to save your slug. Also add a settings field to the page. <?php add_action( ‘load-options-permalink.php’, … Read more
This is a very faceted issue. It combines inherent HTML content issues with whole new load of translation challenges, such as scanning for strings, translation process itself, and its verification. So we have to combine: Text (in translatable form) HTML markup (in hard to break, but preferably flexible form) URL destination (in secure and preferably … Read more
1. Write with localization in mind Don’t use echo or print() to produce text output, instead use the WordPress functions __() and _e(): /** Not localization friendly */ echo “Welcome to my plugin”; // OR print(“Welcome to my plugin”); /** Localization friendly */ _e(‘Welcome to my plugin’, ‘my-plugin’); // OR $my_text = __(‘Welcome to my … Read more
These are not any kind of WP’s own format but rather just gettext file types which WP implements. Translate Handbook has following definitions in its Glossary: MO files: MO, or Machine Object is a binary data file that contains object data referenced by a program. It is typically used to translate program code, and may … Read more
The Editor There are others, but this is most used: Poedit, a cross-platform gettext catalogs (.po files) editor. The Formats .mo stands for Machine Object — compiled export of the .po file which is used by WordPress .po stands for Portable Object — editable text file with the translations strings — based on the master … Read more
You may try Eazy Po. From file menu select “New from source code files..”. In xgettext Command Manager window; Press “Browse folder” to select base source folder. In Build pane press “Execute Command” button to generate Pot file.
I was getting the same warnings even without multiple languages in my app, which led me to find out what was really going on. . . There are a few different things going on here. I was able to silence the fixed-width warnings in my own app by changing the width of the object spacings from fixed width to greater than … Read more
I’m pretty sure “-” is the standard. If you see “_” somewhere it’s probably something some people came up with to make it a valid identifier. Personally I’d go with “-“, just to be correct. http://en.wikipedia.org/wiki/IETF_language_tag