- Posts
-
1. languages files are not included with download, you will need to download the language that you need, this is to avoid using user server space.
2 I think you are downloading the wrong file, check a few languages and all include the .po file.
3. Not all languages are up to date, contributors have not provided update for the lates version, I think the Spanish version is complete.
4. This could be because of what I mentioned on item 3.
5. Thank you for your interest on providing the Dutch translation, you can send it to [email protected]
Thank you for your feedback.
1. Server space is cheap, time (to figure out how to get the translations and such) is not… It’s standard practice to include all translations if you host your plugin on WordPress.org. And considering we’re currently talking about something like 500kb in server space, I would strongly suggest and advice you to include the language file by default.
2. I think you are confusing a .po file with a .pot file (which is what I was talking about). The .po files are included in your translation files, the .pot file is *not*.
The .pot file only contains the strings to be translated and serves as a translation basis/master file.
A .po file is derived from the .pot file and contains translations of the strings to one specific language.
When a new version of the plugin comes out, it will sometimes contain new strings. If there is no .pot file, each and every translator will have to manually figure out what strings are new and manually add them to the .po file for their language.
However if you use a .pot file, this becomes a whole lot easier. You generate a new .pot file for the new version of the plugin. The translators use this .pot file to *automatically* update their .po file to include the new strings (in effect the files are merged to a new .po file by the .po editor program) and the translators can then easily adjust the translation/concentrate on translating rather than figuring out what strings are new.
I hope this explanation makes it a bit clearer. You may also want to read this explanation for more info.
WordPress offers a simple way to generate a .pot file from the plugin repository admin page, I strongly suggest you try it out.
3. As explained in ad2, if you generate an up to date .pot file, this problem should solve itself really easily as translators can then just update their translation based on the .pot file.
4. Again, automatically generating a .pot file is the first step in trying to debug this as that is the only way we can be a 100% sure that all strings will be picked up corectly. If translations based on a newly generated .pot file are not being picked up, then we look elsewhere for the solution. I’ll gladly help you debug as soon as I see a .pot file.
5. Dutch translation is on it’s cyber-way to you 😉
Hope this helps.
Smile,
Juliette
- You must be logged in to reply to this topic.