I've tagged this Design and re-titled it to make it clearer what the "ask" is here; if we're doing this, we'll need to convey to the user that we're showing a label in a "wrong" language (already done for fall-back chain languages), and also that it's a "surprising" language to use because it's not something the user can necessarily even read (e.g. showing a zh label for an English speaker, or an ar one for a Faroese speaker). Does this last point need special design language to convey this surprising state, or can we just rely on the existing design?

building on top of our current work for the about widget improvements i'd like to suggest two proposals:

option 1.
given that we're going to display a fallback language in the about widget (right below), we could keep the placeholder text in the mediawiki header and mark this task as declined.

OR

option 2.
display the fallback* language in the mediawiki header too, if available (if not keep the placeholder text). *for the about widget we're going to follow the mediawiki language sequence API, and we could do the same for the page title (aka object label). given that we display the fallback language right below in the about widget, it might be ok to remove the language chip (this is also something that we might revisit once we pick T340624)

@Sharvaniharan @DVrandecic what do you think?

@AAlhazwani-WMF
I like option 1, because it removes the surprise element of seeing a non-chosen-ui language label. It also gives clear guidance that it is available in other languages for reference. I feel while option2 is an improvement, it still doesn't as effectively remove the confusion with fallback languages.

Wondering if there is still work to do here or not. We implemented some fallback languages and such for the title aswell in the meantime:

So, is this solved @DVrandecic ?