“Lots of people” does not conform with “partially translated”.
Multiple variants of Chinese are in fact completed to the tune of 99+%.
You seem to have 99.0 zh_Hans Chinese (Simplified) problems, completeness not being one.
Having been in China to fail noticing for example Uyghurs and Tibetans are not the same, or the difference between the many different written languages they could confuse you in, it is hard to tell where arrogance being blind to the blindness of ignorance start and end.
In my opinion, the quality of F-droid strings, even upstream, isn’t, and hasn’t ever been, good.
There being a will and a way to get away from that, the same rationale is presented there.
Upstream errors and oversights carry into translations, so short of any special (and only local) efforts, it is all bad.
What makes things better is people looking at strings and then changing them.
People > Tools > Changes
I dare say the rigorous adherence to fear and perfect theory is the ultimate barrier in the way of that happening.
If that wasn’t also part of the problem, it could not stagnantly sustain itself.
But the question was asked, and that is good, so here we go changing it.
Ideally everything would be “done”, and peer-reviewed. Yes, but how would it get there?
For a variation over the theme “done”, it could be a percentage. Sure.
In this case, largely an unchecked one, and one that sounds high.
It could for the case of argument be all erroneous, potentially malicious, and when not wrong, doing nothing in plain view.
Or even a inconsistent mix thereof. Like the argument of “policy” is in this case.
Translations with more translators, (assuming a fixed quota of attracted translators, each assumed to finish an equal amount) have their work included, whereas those for smaller ones, at a certain cut-off, depending on percentage, do not. That in effect means treating a language of few extra speakers, vastly different.
It makes any n%-1 translation effort, for reasons why it is made, worthless.
And in doing so, I think to the inherent effect of taking it to n+1%, longer.
To get to the magic number, you start out short and having to learn what it is.
Short of a feedback-loop, working in the dark on strings without context, nor explanation, relegated to a long tunnel of the same darkness.
100% is not a more magical number.
100% sounds a lot less good signifying potential chaos.
Not making the distinction means pulling it out of a bag. A bag that may have a sweepingly good idea of how to generalize, but a bag nonetheless.
Were you to pull it off your head, you would notice it having been a box all along.
So I care, true, I care a lot.
Even so, what is the issue with going the opposite way?
Acknowledge some languages are 1. Smaller 2. Don’t have people that care.
And ask for help to fix it. How?
Meritocracy in effect. If at present you can make your written English complaint heard, you can help by doing. Your problem, your solution.
Engaging with translators is most easily done through what-you-do-is-what-you-see.
Any translated string is for the better. The more immediate the better.
If it proves a problem, and it very seldom is, and at that, easily corrected,
or, if for some reason proving to be a problem, thwarted by imposing two rules:
- New accounts can only suggest.
- To edit you need to be verified by a manager. Same place of trust where it resides now, making a chain of it. Not perfect, but certainly better than faith in high numbers.
Noticed now, a point still amiss.
To the premise of it being noticeably halfway done, well.
That would be the impression you get from any translation, by looking at the project listings, which are all in English.
We imply here the user is already in f-droid, without having seen the untranslated website, and it does not go without notice, even for the bigger languages, the language used to introduce other programs in one which purpose is to acquire them, and we worry about consistency, for a smaller group of people, most of whom would be delighted to see something in their language, the system-language they picked.
Let me ask why the user wouldn’t feel "what am i doing here - if the program thinks my language isn’t important at all, or in part. It spells danger, all the same, now. It is a call to action for others. Going with status-quo does not get the ball rolling.
The winning move is to fix or not to play. I would make a theatrical play on the play store, but it had no plays in store for me.
The more people seeing errors, the embiggened the chances of someone fixing them. Good.
Imposing a fixed level of translated strings, is no way to get away from it. What could have larger impact than pushing more strings into upstream, only to remove a language entirely from one version to another, for languages that don’t meet it? What kind of signal does that send out?
While the level at which language is commanded and language by, is not exclusive to F-droid, expectations overall are no worse than similar. Language in comparable programs, will stand out once people stop noticing the language used in F-droid. Bonus.
Problems play out one of two ways, and not without issue either way. But it pans out much better when size works in your favour, rather than to discourage even small efforts:
A small problem will be better off getting some traction, rather than slipping away at nothing.
Faced with only the extreme of those options, over learning an entirely new (included, likely to be bigger,) language, it is more important to get basic usability, rather than for others to have a better native experience, or much less inconvenient option, of merely changing the language.
So lets deal with what we have, and get professional down the line. A self-enhancing prophecy.
Work towards fixing inconsistencies, by working, rather than avoiding them, by avoiding work.
Take the meta of work to working levels.
Point all people to translation, from everywhere. The website, F-droid, blog, IRC etc.
Starting with knowing when strings go live. For all.
“You have * days until string-freeze.” being the crucial bit, with room for improvement to be had.
A guide on how to download alphas to see live work before anyone else does. That empowers people without asking of them to build F-droid, to solve their issue without putting it on others.
Language is another way in which F-droid can be, and arguably is, superior.
It is not as if there are languages too small not to increase the user-base and the effort overall in a meaningful way.
Translations hinge on the premise of; more people doing light work of things lighten the load.