Making WordPress.org

Opened 2 years ago

Last modified 2 years ago

#6598 new enhancement

Add a button to the consistency tool to ignore archived projects

Reported by: nekojonez's profile NekoJonez Owned by:
Milestone: Priority: normal
Component: Translate Site & Plugins Keywords:
Cc:

Description

Just as the title of this ticket says. I think it would be helpful if you had a button to ignore archived projects in the consistency tool since they are extremely low priority to translate.

Attachments (1)

consistency-view.JPG (82.0 KB) - added by psmits1567 2 years ago.

Download all attachments as: .zip

Change History (7)

#1 follow-up: @psmits1567
2 years ago

Why add a button to achieve that?
On top of the results you have a view selection with the amounts of found records. You can instantly go to the wrong translation, because you know it is probably the one with only a few translations selected

#2 in reply to: ↑ 1 @NekoJonez
2 years ago

Replying to psmits1567:

Why add a button to achieve that?
On top of the results you have a view selection with the amounts of found records. You can instantly go to the wrong translation, because you know it is probably the one with only a few translations selected

What if there are wrong translations besides the first 500 correct results?

#3 @psmits1567
2 years ago

Hava a look at the image, because I believe you do not understand what I indicated.
Here is an example about a translation we discussed about

#4 follow-up: @psmits1567
2 years ago

You can easely pick the wrong translation out of this list

#5 in reply to: ↑ 4 @NekoJonez
2 years ago

Replying to psmits1567:

You can easely pick the wrong translation out of this list

Oh wait, I'm confusing the two tickets I made today.

For this ticket I meant, why should archived projects appear in the consistency results in the first place? Since they are archived, we don't find them any other way then via the consistency results by sheer luck.

(Or when we know the name of the plugin/theme and have the direct link.)

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

#6 @psmits1567
2 years ago

It depends if the archived projects still get translation updates. If that is the case, then those still need to be fixed, otherwise translation memory will still show those wrong translations.
If the projects do not send updated translations, we should have an option to remove the wrong translation from translation memory

Note: See TracTickets for help on using tickets.