WordPress.org

1. codestyling
   Member
   Posted 1 year ago #

   After inspecting your plugin version 1.9.17 I found, that you provide localization of backend by utilizing gettext functions of WordPress. The Problem is, that you never load a textdomain, so even if I have a translation, it won't be loaded!
   I placed for testing purpose the load_plugin_textdomain('wptouch', false, 'wptouch'); at the plugin main file beginning and voila, it loads the translation out of plugins main folder.

   Please update your plugin to be able to load translations!

   http://wordpress.org/extend/plugins/wptouch/

2. codestyling
   Member
   Posted 1 year ago #

   Sorry for second remark but also the update from 27.08.2010 for version 1.9.18 doesn't contain the above mentioned load_... function call, so the plugin is again not translatable at all even if it is prepared for!

   Please make sure, that the plugin loads a language file to be able to translate the backend texts (and some frontend) into needed languages. How to achieve this has been written in my first post.

3. BraveNewCode Inc.
   Member
   Posted 1 year ago #

   WPtouch Pro is fully localized, ships with a variety of languages, and supports custom language files.

   Our efforts are focused on it, not the free version. If you'd like to make a contribution to the work, send the patched files to help@wptouch.com and we'll include them in the next release.

4. svedman
   Member
   Posted 1 year ago #

   So, what are you saying? That localization is purposely disabled for the free version?

   If so, please state that clearly somewhere. I've spent a lot of time trying to get localization to work in the free version, because your changelogs for the free version mention fixes for localization.

   But it's not working.

5. BraveNewCode Inc.
   Member
   Posted 1 year ago #

   No, it's not purposefully disabled! Why would we have wasted time readying it for localization only to not implement it?

   1.9.19 is localization ready, and we're working with a number of people to bring translations in. In the next few updates you'll see those additions.

6. svedman
   Member
   Posted 1 year ago #

   Excellent news, Bravenewcode! Sorry for misunderstanding.

   Looking forward to that!

7. svedman
   Member
   Posted 1 year ago #

   BTW, I made my own Norwegian translation with the "CodeStyling Localization" plugin, which I've done successfully with a lot of other WP plugins, but the translation is not picked up by WPTouch.

8. BraveNewCode Inc.
   Member
   Posted 1 year ago #

   We'll get that going, don't worry.

Topic Closed

This topic has been closed to new replies.