[wp-meta] [Making WordPress.org] #1411: Wrong translations are automatically validated

Making WordPress.org noreply at wordpress.org
Wed Dec 9 14:34:47 UTC 2015


#1411: Wrong translations are automatically validated
---------------------+-------------------------------------
  Reporter:  Chouby  |      Owner:
      Type:  defect  |     Status:  new
  Priority:  normal  |  Component:  translate.wordpress.org
Resolution:          |   Keywords:
---------------------+-------------------------------------

Comment (by pedromendonca):

 Hi'
 I've been across this problem too, a lot. It's a problem because is not
 just the core, different projects/developers use different aproaches in
 their coded strings, and very often a short word string like "No" or
 "None" have different context and meaning across different plugins, and
 it's bad if it gets imported as *current* in the first place. So I think
 it might work better to just mark as fuzzy, as waiting, or even add a
 context.

 Please add some plugin context or at least mark as a waiting/fuzzy
 suggestion for other projects, EVEN if the use who imports/adds it have
 permissions to edit/validate other projects. He is importing in a specific
 context, not all.
 I've found translated strings by myself in near 0% translated projects
 that I didn't touch before, those strings came from imports I've made in
 other projects and their contexts.

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/1411#comment:5>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list