[…] [Entrada traducida. Original] […]
[…] Weblog Tools Collection – WordPress Translations: mo and po files […]
[…] käännöksen korjaamisessa tarvittavat ohjelmat. Sen jälkeen muunnan Transmissionin käyttämän käännöstiedoston tekstieditorin ymmärtämään muotoon seuraavalla komennolla: msgunfmt /usr/share/locale/fi/LC_MESSAGES/transmission-gtk.mo > […]
Although decompiling is interesting in itself. It seems strange to focus on “you should not have to depend on anyone” at the end of the article. Sure, that is always a valid option, but are the localization communities not just that, communities? — welcoming of contributions and collaboration.
Lloyd: There was some GPL related questions brought to me regarding .mo files, thus this post and the suggested solution.
I don’t really understand your comment, and IANAL, but if that advice was that decompiling a .mo file could allow someone to distribute the file outside of the terms that the .po file was licensed, I would consider that advice with caution because (1) “translation” is too close and likely covered by the .po’s license if it explicitly has one or (2) the distribution of the .mo is covered in another package.
Well, let me put it bluntly. One of the translators of WordPress is giving grief to the people looking for the source of his translation. Rather than choose conflict, I helped them extract the source of the .mo and learned a lot more about .po and .mo files. This is a tutorial based on my experiences.
Interesting, although I managed to download the po-file directly by using the url, too. A lot of people store it in the incluces/language directory. The part that seems difficult to me is creating a pot-catalogue file in the first place. This could be necessary if you want to properly translate your theme.
So far so good with the po/mo files but how can I make the content in wordpress site multilanguage ?