Do the string status indicators mean anything #4698
Replies: 3 comments 1 reply
-
The full list of possible displayed states can be seen here: https://github.com/WeblateOrg/weblate/blob/master/weblate/templates/snippets/unit-state.html Also, these are not used only in the zen mode, but whenever listing string - search results, nearby strings, other languages, .... |
Beta Was this translation helpful? Give feedback.
-
@nijel I don't understand how the "untranslated" one does anything. If there is nothing in the field, there is nothing. Furthermore, the untranslated icon has no resemblance or connotation to "untranslated" as a component category, (which is a red squircle). What would be lost if it was removed? |
Beta Was this translation helpful? Give feedback.
-
This thing for suggestions is strange. Should be a questionmark instead. (?). |
Beta Was this translation helpful? Give feedback.
-
Flying a bit low on not fully thought through suggestions for the Zen editor with #4696 and #4697
The status field doesn't fit with that, and keeping the flow of information in central areas and consistent questions the status field.
Does anyone have any use of the status section in the top left?
means untranslated (this status is usually green, but that is the soft-keyboard)
I don't see why that is relevant. In Zen mode it just means the editing started from somewhere. There is no way to not save edits other than to Ctrl+Z all the way back
means translated (this is usually green, but so is the soft keyboard, so that isn't very distinguished)
(Why is the soft-keyboard green is the bigger question.)
The statuses don't update on the fly (?) while one is in the editor, so why doesn't the user already know that the string is being edited?
means some sort of error (I think surrounding the editing field or ideally where the error is would be better)
means the string is commented (the functionality show them is not good)
I had an idea for showing comments in Zen in #2767
There are probably other statuses (will update when I see them), but for XML errors, fuzzy and whatnot, I think the colours from the bars should be used. Red and green are problematic for colour-blind users.
There are palettes that work a lot better, but then one that signifies "good" "bad" and so on is needed.
Grayscale where reviewed is white, and then one "look here, error" in colour could do?
Semi-related: #4476
My current assumptions:
means "needs editing". However I didn't know that, because there the connection between clicking the checkbox to do so, seeing it as a string status, the colour, and finding it with the regular expression picker/search.
Beta Was this translation helpful? Give feedback.
All reactions