Opened 9 years ago
Closed 8 years ago
#1765 closed enhancement (duplicate)
GlotPress import: Avoid overwriting current translations
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Translate Site & Plugins | Keywords: | needs-patch |
Cc: |
Description
(moved from the GlotPress plugin repo issue since this is specific to the GTE/PTE roles on wordpress.org)
Current GlotPress import feature only lets GTEs/PTEs import translated PO file as a whole, overwriting existing translations.
A new option to import without overwriting can be useful for cases like the following:
- For the cross-locale PTE trial, to make sure community translations are not reversed by the third-party work
- Import a PO file from an old version of the plugin/theme (use new translations as current, do not import obsolete translations if the glossary or style guide is changed)
On the import screen, add one of these:
- A checkbox that says "Do not overwrite existing translations"
- Two radio buttons: 1) "Overwrite existing translations" 2) "Only import new translations"
@ocean90 suggested a custom plugin with the gp_translation_set_import_over_existing
filter and a custom template for the import screen (and possibly an added action to the import template).
Change History (2)
Note: See
TracTickets for help on using
tickets.
As the cross-locale PTE will probably be a PTE and the fact that it's just a choice, the cross-locale PTE still has the technical possibility to overwrite in this case.
If implemented as above, make sure the checkbox is ticked by default or that the default radio button is set to 'only import new'.
It might be better to have a new role like PTE-newstrings-only or PTC (Project Translator Contributor) that could only import new strings. But that's a bigger thing of course.