This an easy and short one, but the documentation on WP.org for the load_plugin_textdomain function might lead you into the wrong direction, if you start thinking about how to define the 2nd and 3rd parameter.
For a simple plugin, it is best to use the translate.wordpress.org repository for translations. This way the different strings can be translated individually directly online and you do not need to worry about having the right
.mo files updated within your plugins repository.
Continue reading i18n load_plugin_textdomain best used the simple way
Until a few days ago, I would never have envisioned to write a posting about i18n in WordPress… And then I started the task to make my plugins ready for translation by the community at translate.wordpress.org.
i18n stands for internationalization = I + 18 charachters + N
While working my way through the principles and standards to use, I realized that there are quite some things you should consider and have to do in a certain way – let me touch some of them over a few posts…
Continue reading i18n Internationalization and Translation for plugins