make rejecting cancellation more clear #3576
Conversation
There is a "Discard input?" menu appearing after user fills answer, at least partially and tries to leave answer window. It has options "cancel" and "discard" with "cancel" being not entirely clear - as user is cancelling filling of the quest. And "cancel cancelling" is tricky. Situation is even worse in some translations where even the best found text is more confusing than English version. see streetcomplete#3396 where it was discussed
There was a problem hiding this comment.
Known negative effects: translation required again
I am aware of
<string name="quest_generic_hasFeature_no">"No"</string>but in some languages this fields may require different translations.
I am not sure if this is a good practice, but one option would be to pre-seed the value of confirmation_discard_negative2 with whatever is translated for quest_generic_hasFeature_no, and then mark confirmation_discard_negative2 as fuzzy / needs-review in POEditor. I did something like this once when I was changing strings in Red Moon.
|
Sadly there was some accident with translations strings and nearly everything got marked as fuzzy - which is still not entirely repaired, what makes it less useful :/ |
|
Speaking with my translator hat on, I support that new answer which should be translated from scratch. Perhaps it should be bundled with some other new translation strings (like Smoothness quest #3257 ?) and translators be notified some time before so they can update it, then it should work well (for languages which are kept up-to-date at least). And beta release with new translation strings would be good idea before pushing an official one... Stuff being marked as fuzzy is better than nothing, but for example I have several dozen translations I've myself marked as fuzzy as I'm not completely happy with them... I most probably won't see a new one pushed by SC there for quite some time, unless I'm specifically warned to go look for it. |
That is happening already in every release cycle if I understand what you mean right.
In general such changes are merged and appearing in beta releases, in part to give time for translations. |
There is a "Discard input?" menu appearing after user fills answer, at least partially and tries to leave answer window.
It has options "cancel" and "discard" with "cancel" being not entirely clear - as user is cancelling filling of the quest. And "cancel cancelling" is tricky.
Situation is even worse in some translations where even the best found text is more confusing than English version.
see #3396 where it was discussed
Known negative effects: translation required again
I am aware of
<string name="quest_generic_hasFeature_no">"No"</string>but in some languages this fields may require different translations.