Comments on: echo __(‘I Hate Localizing My Plugins. How About Something Different?’);

By: Joost de Valk

Joost de Valk — Sat, 14 Mar 2009 13:41:23 +0000

I agree with Westi, would be a good thing to discuss this on wp-hackers. I find the localization process to be so annoying that I just don’t do it…

By: Kretzschmar

Kretzschmar — Sat, 28 Feb 2009 17:05:52 +0000

Don’t like your idea on reinventing the wheel but would love to have exactly your technology for posts and pages. Without adding translations inside tags (like most translating plugins do).

By: A?k

A?k — Sun, 22 Feb 2009 15:40:20 +0000

daima wordpress:)

By: Stefano Aglietti

Stefano Aglietti — Sun, 22 Feb 2009 15:14:48 +0000

It’s something that was in my thoughs time to time in the past, we at wordpress italy would love to give users a large library of localized plugins and I can have few people that would love to collaborate tokeep them updated. Unfortunatly in the past i made some translations and some I18N of plugin and sent my works back to the authors… very few give a feedback few added the translations but failed to send me a beta of new version to update the translation, so new release are partially untralsated. Now with auto update it’s worst than before.

Having a centralized repository as wp.org that can care for localizations as we do for WP would be great people can translate plugins they love and submit to us locale team for a check and for commit (we need to have a method to give credits to translators) and this will improve the numbers of translations, the quality of them (locale team can write tralsation guide with rule and dictionary for trnaslating some words making the plugin follow the trsnaltion style of WP etc)

I agree with Westi put this on polyglots and hackers and let’s do some brainstorming on it!

By: westi

westi — Sat, 21 Feb 2009 10:17:17 +0000

Maybe we should provide a way within the plugin/theme installer framework for I18N file discovery and download.

Based on the translations ending up in plugins svn and being servered by the wordpress.org download infrastructure.

This could include automatically providing a translated version when a localised install of WordPress does plugin installation.

Maybe a good discussion topic for wp-polyglots/wp-hackers.

By: codestyling

codestyling — Fri, 20 Feb 2009 22:41:08 +0000

I have my doubts about reading file at backend from remote sources if i want translations for plugins/themes. In my opinion the plugin directory at wordpress.org should get the same subfolder architecture like wordpress itself: an i18n folder for each trunc and tag version not been pre-packaged to the download zip. The autor of plugin should be able to give other users (translators) the ability to checkin/checkout there language files. The plugin/theme author is responsible to branch/tag and authorize this translated checkins.
In this way also a plugin/theme language file update management could be introduced similar to the core or plugin update mechanism and would allow easy browsing the needed files for plugins (nessessary for multi-lingual environments).
This would fit much more seamless into WordPress as a new technology. I’m interested nevertheless into your more specific idea to do it beside the road.
(and if interested you will find a complete WordPress plugin compete a bit with PoEdit but pure PHP and Google Translate support at WordPress plugin directory or at my development page)

By: Elad

Elad — Fri, 20 Feb 2009 22:13:25 +0000

Would be happy to help you test such a thing. My case a difficult one: I use rtl :)