[wp-meta] [Making WordPress.org] #2582: this-plugin-is-not-properly-prepared-for-localization-–-help

Making WordPress.org noreply at wordpress.org
Tue Mar 14 23:42:15 UTC 2017


#2582: this-plugin-is-not-properly-prepared-for-localization-–-help
--------------------------+-----------------
 Reporter:  elliotcondon  |      Owner:
     Type:  defect        |     Status:  new
 Priority:  normal        |  Milestone:
Component:  General       |   Keywords:
--------------------------+-----------------
 Hi Guys,

 Elliot here from ACF (Advanced Custom Fields plugin).

 I'm looking at the 'translate' page for my plugin
 (https://translate.wordpress.org/projects/wp-plugins/advanced-custom-
 fields) and it says "This plugin is not properly prepared for
 localization".

 I'm guessing this is because my plugin uses a textdomain of 'acf' which is
 different to my plugin slug 'advanced-custom-fields'.

 I don't see why I should be penalized for choosing an optimized
 textdomain, is it possible to allow this case?

 Thanks
 Elliot

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/2582>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list