Translation

the same to me, I should be delighted if I could make the translation into spanish if it is any help.
do you support it??

The proper file name is genesis-author-pro-xx_YY.mo where xx is the language and _YY an (sometimes optional) country code. The language must match the language chosen in the WordPress settings. The file must reside in the languages folder under genesis-author-pro on the server. Make sure that proper permissions are set for the file. This works for me (with da_DK, because I am a Dane living in Denmark).

Does this help?

We will be releasing an update that fixes a problem with the internationalization. We have to verify the last item that was giving us translation problems is definitely working because one user testing for us reported success and another user reported that it failed but I think the issue is the second user did not update from the new .pot file.

Once we do that you can use the provided .pot file and upload your translation as genesis-author-pro-xx_YY.mo as indicated.

We also welcome localization files in the plugin itself. You can submit your localization file to the plugin for inclusion in a future update via a pull request at
https://github.com/copyblogger/Genesis-Author-Pro/

I will try to work up a Wiki about this. I’ll be honest, I’m not the best person for this as I find documentation on proper internationalization to be confusing, conflicting, and incomplete. I really wish there was a single, very clear and coherent source for all the steps for translating themes and plugins. It seems that everything is piecemeal or inaccurate. In some cases I had to go into the core code. In other cases it seems like we should use certain types of translation functions but those functions aren’t fully supported in all localization tools or require specific types of search strings when building the .pot file and only one obscure site seems to reference that.

Seriously, sorry for the rant. I want to make this the best plugin including international support and eventually support for accessibility but that’s difficult to do when the documentation is handled like some kind of obscure gnosis.

TLDR; we should have a fully internationalized plugin VERY soon and welcome community support for localization.

If I have to, I can use the .pot file, but I always prefer to update from the source files themselves. It is often difficult or rightout impossible to translate without knowing exactly where and how the string is supposed to be used. Even if the developers document the i18n functions very carefully using _x(), it is difficult to know all the problems that arise when translating to another language. ??

Thank you for your hard work!

Hi Georg, I am a Dane too. But I am living in Germany and I have a German translation up running here, https://movies.lindebjerg.de/, I have made the translation using films instead of books. The .pot translation files works fine.

Please notice!
At the moment the plugin makes troubles with some dates settings like mine: j. F Y
I try to help Nick nailing down the problem.

Hi Lindebjerg!

I have no technical problems with the .pot files, I just prefer to translate with access to the source files.

I use the same date setting. Thank you for working on it.