[wp-trac] [WordPress Trac] #34134: Do not import strings without domains if string exists in Core

[WordPress Trac]

#34134: Do not import strings without domains if string exists in Core
--------------------------+-----------------------
 Reporter:  niallkennedy  |       Owner:
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  I18N          |     Version:  trunk
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:  template
--------------------------+-----------------------
Changes (by dd32):

 * status:  new => closed
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 Plugins really shouldn't use strings without a textdomain. If core changes
 the string, suddenly the plugins string is no longer translated - it's
 just not a good user experience.

 translate.wordpress.org currently has Translation Matching enabled, if you
 use 'My String' in a plugin and it's already translated in another
 project, it'll get imported to your plugin too (so translate in one
 project, and it's available for all others). In the past I've used what
 you're proposing too, but thankfully with everything in the one GlotPress
 instance, it's no longer really needed.

 Core Trac is for Core Development only, it's not a support location for
 either WordPress or WordPress.org tools, if you'd like to discuss anything
 further to the request, feel free to drop in the
 [http://make.wordpress.org/chat #meta-i18n channel in Slack] or file a
 ticket on
 [https://meta.trac.wordpress.org/newticket?component=translate.wordpress.org
 the Make Trac under the translate.wordpress.org component].

--
Ticket URL: <https://core.trac.wordpress.org/ticket/34134#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform