Making WordPress.org

#6544 closed enhancement (fixed)

Add a new option for Translation Feedback as 'Fuzzy'

Reported by: chaion07's profile chaion07 Owned by:
Milestone: Priority: high
Component: Translate Site & Plugins Keywords:
Cc:

Description

Currently when PTEs give feedback about individual strings there are 6 options. With every release and introduction of new content, there ate always strings which end up marked as 'Fuzzy'. While PTEs either update the Fuzzy string or suggest an updated one of their own it would super helpful with adding a new option for feedback as 'Fuzzy'.

https://drive.google.com/file/d/1QPQoMzIAYKJ2Zc0I6hcJGv3ZF2oTY_Ko/view?usp=sharing

Attachments (1)

Translation_Feedback_Enhancement.png (51.1 KB) - added by chaion07 18 months ago.
Mockup

Download all attachments as: .zip

Change History (4)

#1 @akirk
18 months ago

Hi Ahmed, Could you explain what you'd like to convey with specifying "Fuzzy" as a Reject Reason?

A current translation will turn fuzzy if the original slightly changes, in the best case someone else jumps in and just updates the translation. It could stay in fuzzy state until someone suggests such a new translation.

If you reject a fuzzy translation then the translation text will no longer be readily available as a basis for a new translation.

Since the Reject Reason is meant as feedback to the original translator with a chance to improve, I am not sure if "Fuzzy" as a reason would be helpful for them.

#3 @akirk
16 months ago

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

It is also possible to give Feedback and mark fuzzy at the same time. Unfortunately we haven't received further clarification by @chalon07, so we're closing this ticket. We close it as fixed since we did add the ability for locales to get additional custom reasons.

Note: See TracTickets for help on using tickets.