Open Bug 1344179 Opened 3 years ago Updated 2 months ago

[translate] Keep unsaved translations when navigating to other strings

Categories

(Webtools :: Pontoon, enhancement, P3)

enhancement

Tracking

(Not tracked)

People

(Reporter: yfdyh000, Unassigned)

Details

It will be useful if I want to:
1. Look at another string for the context.
2. Immediately go to the next string when submitting, even no error checking result. [1]

[1]: https://crowdin.com allow to keep the translations, but submit will wait for error check result.
[1]: https://www.transifex.com/ allow to keep the translations, and will mark the saved translations if the error check is not passed or failed to submit.


For cause 1, I occasionally encounter it, I had to use the clipboard or notepad to temporarily store the unfinished translation.

For cause 2, I have to wait at least 300ms (e.g. China - US network latency time) for each translation's error checking and submission, it is a useful feature and is a rest, but also an interrupted and efficiency lowered.
Let's see if I understand this correctly:

1. You start by typing a translation of the first string. Then you open another string or two to check their details. Finally you return back to the first string and the partial translation you started typing initially is still there. Is this the expected behaviour? If yes, we probably shouldn't display the unsaved changes warning when moving to other strings.

2. After a translation is submitted, we should always go to the next string. If the translation check fails, we should show an error in the string list (by e.g. painting the status icon red in the string list) and presenting the error when the string is openned again. Is this the expected behaviour? If yes, we should file a separate bug for this and make it depend on bug 1237667, which will permanently store failed checks (errors) for each translation.

Anyways, I like both of the ideas very much.
Flags: needinfo?(yfdyh000)
(In reply to Matjaz Horvat [:mathjazz] from comment #1)
> Let's see if I understand this correctly:
> 
> 1. You start by typing a translation of the first string. Then you open
> another string or two to check their details. Finally you return back to the
> first string and the partial translation you started typing initially is
> still there. Is this the expected behaviour? If yes, we probably shouldn't
> display the unsaved changes warning when moving to other strings.

Yes.

> 2. After a translation is submitted, we should always go to the next string.
> If the translation check fails, we should show an error in the string list
> (by e.g. painting the status icon red in the string list) and presenting the
> error when the string is openned again. Is this the expected behaviour? If
> yes, we should file a separate bug for this and make it depend on bug
> 1237667, which will permanently store failed checks (errors) for each
> translation.

Yes. Unconfirmed have errors translations should not be commit to source repository, like a suggestion.
Flags: needinfo?(yfdyh000)
Severity: enhancement → normal
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3

This bug is related to one of the proposals for enhancements in pontoon.next
https://docs.google.com/document/d/1HDtCUMeogo2kjD5aNjulnlxSaC5kr928w5VnyXiAN3o/edit#
Feature requests and proposals
General
Add ability to navigate among strings without saving translations or losing progress (like in text editor)

@Matjaz, could you please add this bug to the doc?

Type: defect → enhancement

Thanks, Artem! I've updated the doc.

CCing adrian, since this bug also affects the changes to the unsaved changes popup we plan to refactor.

Summary: [translate] Allow to keep translations and go to another strings → [translate] Keep unsaved translations when navigating to other strings
You need to log in before you can comment on or make changes to this bug.