Improve navigation between strings

[Madis0]

I think it is a bit hard to navigate between strings when they have varying lengths, as the back/forward buttons keep shifting up-down, making it hard to go, for example, 5 strings forward. To fix that, I have two ideas:

• align back/forward buttons to the bottom
• let the user swipe between strings as if they were tabs

It is up to you whether you'd like only one of them, or both.

[gsantner]

swipe: use viewpager? with each string being a fragment

[Lonami]

Actually this was kind of a "feature" since you would be forced to go carefully go through the strings, rather than just skipping a lot. But indeed, it must be annoying when you're reviewing a translation, as the spinner just isn't enough.

align back/forward buttons to the bottom

What about small screens, and if the keyboard is shown? I guess someone would hide the keyboard to go through everything.

let the user swipe between strings as if they were tabs

Yep, this would be nice. Maybe someone is up to the task with @gsantner's idea, otherwise I don't think it would be too hard ^^

[ldmpub]

Hi, on the same subject is it possible to display "position" of the current string while translating? For instance "String x / y" where x is the current position and y the total number of strings available in the file.

It will drastically improve to navigate backward / forward among several strings, remembering positions of particular strings.

[gsantner]

In bottom left this is displayrd

[ldmpub]

Thanks for your answer.

I have seen these numbers but there are more a "status / progress" of the translation(*) because the x part is not the position => it does not change when just navigating with Previous / Next buttons.

Note (*) this status may be displayed in the repositories home page instead (next to the percentage of translation done).

[Lonami]

it does not change when just navigating with Previous / Next buttons

Having the two would be somewhat confusing in my opinion, and introduce more visual noise. In my opinion, knowing how many strings have been translated so far is more relevant.

[ldmpub]

Yet the following main info are needed to help translators work:

• total number of translation strings
• status of translated strings : new (empty, ie strings left to translation), translation done (already translated Ok), changed strings (translations to be reviewed)
• position of the current string.

From my point of view we can add some of these info on the "Welcome page" (for instance detailed number of strings by status) and other on the "translation string screen" (like current string position). We should allow user to filter and navigate in one of "status sub-categories". I also think we can win a lot of room on the "translation string screen" to display some of these info by replacing big "PREVIOUS" / "NEXT" buttons by little and visual icons.