Clarify words/strings of total labels

[nijel]

Describe the bug
The "Strings of total" / "Words of total" columns available on some views are confusing to many users.

Additional context

See discussion at https://hosted.weblate.org/translate/weblate/master/fi/?checksum=655539e4b9213b2e#comments

This was introduced in #2732

To Reproduce
Steps to reproduce the behavior:

1. Go to https://hosted.weblate.org/languages/

[comradekingu]

The difficulty is with keeping the category name short and sweet. Since the first is already "strings" and "words"
( ____ ) "of instance total." or ( ____ ) "of total on instance".
I envisioned it as "of total" at first, and if the current "Strings of total" "Words of total" fails, maybe that would fail too, but how about ( ____ ) "on instance".

A possible mouseover that describes how many strings there are total, and states it in absolute numbers would be helpful.
For me the confusion is which field the bar corresponds to, and I don't know exactly what the description of the problem is. Back when it was implemented there was one bar for each.

How about being able to click the actual field name to show the corresponding bar?
Right now it sorts by "of total", showing the bar from total without any indication that it is the wrong bar.

Sorting while seeing a different bar actually brings back seeing unadded components visually, which is the same click arrow for dropdown, and name for navigation for "projects" and "languages" up top. Then again the current system there is nice enough.

What that boils down to is having sorting by show the corresponding bar right away.
That, along with some indication that the "Strings" is selected (by default), would maybe help?
I noticed (just now) that the dropdown arrow is blackened when selected, but not by default, could be it is more obvious a selection is made if it is connected to a graph change too (?)
The top dropdowns don't behave in the same manner.
Stating Language twice is redundant.
"Dashboard" is redundant.

This gives one extra project

And for dashboard view

Underscore is uglier, the turquoise text is prettier. Could make categories turqouise and project names black? (I don't really know how the colouring works)

With the middle-ground changes, I don't think anything is missed for anyone.

Right now the design is a bit unbalanced between showing everything, and hiding some things.
The ideals are simple simple, and everything everything. In between that, it needs to be a bit smarter.

[ldmpub]

My concern is to understand and then to clarify for users by using "good" words ; what "total" are we speaking about here?

Total can not be used alone but needs a "reference" for instance: "Total of words in a phrase / in a book". Above the word "instance" does not refer to anything, as far as I know, in Weblate ; maybe it means "server"?

[comradekingu]

@ldmpub
A total does not need to be qualified. https://www.merriam-webster.com/dictionary/total
Regardless, your point remains I was wrong suggesting it.
Since the bar, and "half-full glass" way of looking at a bar is describing the added, rather than the missing part, it needs to detail completion positively.

I rather like the "on instance", because then all the graphs can have this segment.
In the dashboard it would detail how many % of the total available strings/words any respective project represents. (In danger of confuzingu striking), also, the % of currently untranslated is missing there. (but it was anyway…)

I don't know that the ( )s made it any clearer, nor do I know what happens with this way of doing it in RTL languages.

Edit: I read

Above the word "instance" does not refer to anything, as far as I know, in Weblate ; maybe it means "server"?

The logic was originally that total implied the outmost totality of strings available. "Strings" are in a similar fashion, "of currently translatable strings".
Instance means what is on the running Weblate server in question. So on a one project server, with all components added, it would just be the same graph.

The argument could be made to keep statistics to statistics, and keep the info-navigation to itself.

[ldmpub]

@comradekingu Thanks for your confirmation "instance = server".

I'm quite lost by your other explainations and I'm still confused on using, understanding and translating theses dashboard statistics :-(.

If I go back to my major concern, in merriam it's stated

Total noun
English Language Learners Definition of total (Entry 2 of 3)
: the number or amount of everything counted

So it confirms, from my point of view, that a total is counting something which should be clearly identified by a name and / or context.

[comradekingu]

@ldmpub There are however many ways to use "total".
A count or tally comes to a total. You could describe that number as the total, by saying "the total is x".

[comradekingu]

I have given up on being theoretically correct and problematic in practice.

To make a long trail of thought short, I want to go from

to

The idea being to represent unadded strings as a percentage of the total of the bar. This way it is easy to see if components are not added, and their respective breakdowns, without having an extra category.

[nijel]

I'm not really convinced it's a good idea to assume this is something that interests most projects. In case projects wants, it can enable language consistency and the stats is what you want to see. In case it doesn't, what are these numbers for?

Typical example could be OsmAnd. The iOS and Android apps are developed and translated independently, so there is really no pressure to have same languages supported in both.

[comradekingu]

@nijel If it doesn't interest most projects, I would argue the same goes for "of total", which I find useful. This new proposal removes "of total", and the reason why it confuses people, retains the same info, with less visual elements and a lot of horizontal space saved.

It would be great for OsmAnd iOS if more people discovered the resource. (It is almost a duplicate, and it doesn't have automatic propagnation(?). It is however nearly always the case that things should be added (or have reason to) when they could. In due time, and for what is deemed important to the translators. That makes it important to discover what can be added, and what isn't.

[nijel]

C. Rüdinger suggested on https://hosted.weblate.org/translate/weblate/master/en/?checksum=655539e4b9213b2e:

What about "share in total" (percentage share of all strings in project)?

[nijel]

Revisiting this now as the column is still a source of confusion. While I can see this information is useful to some users, it doesn't seem to be widely needed. Going through proposals I've seen so far, I think we should pick one out of:

• Remove the column without any replacement, most people won't notice it's not there
• Move the information to progress bar only, that seems to be confusing as well, as the progress bar would not match the numbers
• Find better description for the column. It seems we have failed in this for several months
• Find alternate metrics which would be easier to understand and describe. How about using "Missing"? That should be understandable to most of the users while still giving the information.

Unless I see compelling reasons against that, I'm going to implement the last option.

[comradekingu]

@nijel

With there now being ghost-icons for unadded components, the need to discover unadded projects through the "of total" is not as present. Moreover, it is very kingu-like, for a platform that otherwise is very easy going, so removing it is an outright benefit that plays into the consistency of what Weblate is. The ghosts work, and this is sort of both, so I am thinking ghosts only is way better.

If going with dual-functionality bars, they would have to differentiate between "missing" and "unadded" (like the last part of Airsonic here) That maybe isn't obvious, so let's see what happens without.

It would be nice if the icon could mouse-over to give more specialized info.

To carry the ghost-icon into the bar works (in the interest of not adding complexity), (Andor's Trail example) but not if there isn't room, like it would be for Airsonic.

[github-actions]

Thank you for your report, the issue you have reported has just been fixed.

• In case you see a problem with the fix, please comment on this issue.
• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.