WordPress.org

Making WordPress.org

Opened 3 years ago

Closed 14 months ago

Last modified 8 months ago

#1703 closed enhancement (maybelater)

Batch search/replace to ensure translation consistency and fix incorrect propagations

Reported by: SergeyBiryukov Owned by:
Milestone: Priority: low
Component: Translate Site & Plugins Keywords: needs-patch
Cc:

Description

Translation Consistency view added in #1682 is a great first step to ensure translation consistency across different projects.

I think a second step should be batch search/replace to fix incorrect propagations.

Use case:

  1. I've noticed a weird string ("Загрузка и помощь") in Rosetta admin.
  2. I've tried to find it using the Translation Consistency view to no avail. (It looks like you can only search by an original. It would be great to be able to search by a translation too.)
  3. Finally, I've found the string in the Rosetta project. Someone in some project translated "Loading…" as "Loading & help", and it propagated to other projects too :-(
  4. Now there are 11 projects where "Загрузка и помощь" needs to be replaced with "Загрузка…". Could be worse, but fixing all of them manually is still not fun :-)

Change History (13)

#1 @ocean90
3 years ago

  • Keywords needs-patch added
  • Type changed from defect to enhancement

This ticket was mentioned in Slack in #polyglots by sergey. View the logs.


3 years ago

#3 @ocean90
3 years ago

  • Priority changed from normal to low

#4 @SergeyBiryukov
2 years ago

Just stumbled upon 200 incorrect translations of "Save" as "Экономить" ("to save up") instead of "Сохранить". Someone definitely used Google Translate there...

Going through all of them manually is just not feasible for me at this point.

Last edited 2 years ago by SergeyBiryukov (previous) (diff)

#5 @SergeyBiryukov
2 years ago

Some more incorrect translations to fix later:

These are all a part of the CMB2 framework used by many plugins.

"Second" and "None" are a great example of strings that require a different translation depending on context and cannot be reliably propagated across multiple projects.

#6 @pedromendonca
2 years ago

This would be quite nice, just found a typo in a string of mine that was propagated to a huge ammount of projects.
Bulk editing accross projects is very dangerous because it would depend a lot on the context, but equal strings that have the same timestamp and author can be easily marked as propagated.

Hope this is implemented in a near future.

A good adition to concistency listing is order by date, or identify clearly the original contribution vs propagated contributions.

This ticket was mentioned in Slack in #polyglots by sergey. View the logs.


2 years ago

This ticket was mentioned in Slack in #polyglots by sergey. View the logs.


2 years ago

This ticket was mentioned in Slack in #core by sergey. View the logs.


21 months ago

#10 @ocean90
14 months ago

  • Resolution set to maybelater
  • Status changed from new to closed

There are currently no plans for adding batch search/replace functionally due to performance reasons.

This ticket was mentioned in Slack in #meta by sergey. View the logs.


9 months ago

#13 @ocean90
8 months ago

#3734 was marked as a duplicate.

Note: See TracTickets for help on using tickets.