Thread Starter
josjo
(@josjo)
Some more information for all of you who are working on translating this plugin.
I use Poedit with the following project settings:
Charset:
UTF-8
Source code charset:
iso-8859-1
Plural forms:
nplurals=2; plural=n != 1;
Paths (assuming your translation is in the plugin’s language folder):
..\.
Keywords:
_e
__
_x:2c,1
Most of the source files are in ANSI, but a few are UTF-8. If you rescan the sources with Poedit it will complain and the strings in the files with a format not matching the project settings will be marked as fuzzy.
Thread Starter
josjo
(@josjo)
The text domain needs to be loaded earlier. As it is now it gets loaded after create_post_type which means that the translations are not available when the menu on the admin panel is created.
I tried to move it to the top of actions added to init and now it works.
Thread Starter
josjo
(@josjo)
All non ASCII (or even extended ASCII) characters like the ones below makes it hard to translate. I think it is best if these characters is not used when calling the translation functions (_e, __ and _x) if possible.
One way is to sprintf them into the strings. Maybe they should be made into constants somewhere so they are more easily replaced. Suggestions?
I also think it would benefit the translation process if all files where either UTF-8 or iso-8859-1.
Example characters: ▾ ✘
@josjo
Thank you! Your contribution helps a lot. We will try to fix the localization in 1.0.7 and 1.0.8. There are a few bugs that are higher priority.
@josjo
Your patch is included in 1.0.7
Thank you!
Thread Starter
josjo
(@josjo)
Thank you Yani!
I think this plugin is great. I have tested most of the popular calendar plugins for WordPress, but I found this to be the most user friendly. Plus it integrates nicely into WordPress by using custom post types.
I’ll continue translating and when I have a Swedish translation ready I’ll submit it to the project.
Keep up the good work!
Cheers,
josjo
Thread Starter
josjo
(@josjo)
You can ignore my rant about non ASCII characters above. I solved it by changing project settings and preferences in Poedit. I now use UTF-8 for source code charset and have changed to a custom font (DejaVu Sans Mono). Poedit doesn’t complain anymore and I can see and edit the non ASCII chars.
The issue with the text domain being loaded to late however still remains. I don’t think the fix I suggested above it will break anything else.
@josjo
Thanks for updating us on the UTF-8 ASCII issue.
Loading of text domain will be fixed in 1.0.8
We are preparing a bug tracker that we might open to public and I will direct you there for better tracking.
Thank you for all your support.
