[wp-meta] [Making WordPress.org] #8226: Currently translations can be imported without a proper header

[Making WordPress.org]

#8226: Currently translations can be imported without a proper header
--------------------------------------+--------------------
 Reporter:  psmits1567                |      Owner:  (none)
     Type:  defect (bug)              |     Status:  new
 Priority:  high                      |  Milestone:
Component:  Translate Site & Plugins  |   Keywords:
--------------------------------------+--------------------
 With GlotPress you can translate originals for your locale. When you
 export lines from a project, it contains a header with several lines of
 info
 One of them is the locale.
 However if you import translated originals, you can do that without this
 header. I have experienced large import containing translations for a
 different locale. That causes a lot of work, to reject them all, and
 unnecessary records in the already huge database.

 One solution would be to only accept imports with a proper header
 containing the locale. If the locale does not match the locale of the
 project, then the import should fail.
 That is the first and most easy step to implement a fix. I am aware that
 you still can import translations from a different locale, by setting the
 matching locale. But in that case we know who imported them, and can point
 out, that this is very wrong

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