@eduardo: we’ve introduced a new interface that has a lot of new language and content and we really still need to get new translation files from people at this point. This is still coming for now.
I’ve noticed that NextGen Gallery new versions doesn’t include the proper localization funcions. For example, once generated, the first text chain in my .PO file is “Album: “, which corresponds to line 157 in /products/photocrati_nextgen/modules/attach_to_post/adapter.attach_to_post_ajax.php.
This is line 157:
$image->alttext = _('Album: ').$entity->name;
According to http://codex.wordpress.org/Translating_WordPress, it should be:
$image->alttext = __('Album: ', 'nggallery').$entity->name;
The localization function should be __(), instead of _(), and include the textdomain.
Anyway, if you are interesed in my translation, please let me know.
@photocrati:
May be I missed something obvious but as I can see in the code almost all new options are realised in violation of WordPress Codex.
The strings are returned either as plain text or through _() function. I can extract to a pot-file strngs from the _() function calls (in hope they will work some day) but I don’t see any way to deal with those returns like
function get_page_title()
{
return 'Other Options';
}
as in “nextgen-gallery\products\photocrati_nextgen\modules\nextgen_other_options\adapter.other_options_controller.php” for example.
How can I (or anybody else) help you with tranlation whilst there are no easy ways to extract original phrases?
@baev – Thanks for the feedback and we do appreciate the inconvenience and frustration at not being able to generate a full .pot file for the plugin at this time. We are aware there are many instances where the plugin is not written to properly adhere to i18n standards.
Although we do not have a timeline right now, it is definitely on our radar to be addressed as soon as we can.
– Cais.
