One consideration is that not al the topics have such info available, so a fallback may be needed (option to contributing it, leaving it blank, or something else...).

we can explain this as a tradeoff for increased usage of language switching, which hopefully people will appreciate as a worthwhile tradeoff.

In T279635#6987095, @Zabe wrote:

The combination of Kartographer and FlaggedRevs with $wgFlaggedRevsOverride set true, which is the case for bswiki, can produce some known issue (see T229726#5419327). Kartographer can still be activated in bswiki, but the community should be informed about this.

In T279635#6983068, Zabe wrote:

Is there a community consensus for this change?

@Dbrant: That would mess with the current UI/UX of the Main Page, as we would have redundant links (the button labeled "Više" leads to the article).

Since bswiki is also set to uca-bs-u-kn, it would make sense to set it here as well. I've updated the task accordingly.

@bearND : How about now?

Note: It might be a good idea to strip (''na slici'') as it's equvivalent to (pictured) on the English Wikipedia.

It's pretty easy to delete all the rules and subrules by mashing the Delete key, but it would be useful to be have the option to multi select several and disable/enable them in one go.

@pmiazga: I was referring to the gender preference of the block creator, whose username is displayed right below this header. It's impossible to translate "Blocked by" without resorting to a gendered verb in Serbo-Croatian, for instance.

Infokutija boja, Infokutija softver, Infokutija film, Infokutija album, Infokutija teniser, etc. (you get the idea...)

How do Wikipedians label articles by their quality level?

Well, this task is for the Bosnian Wikipedia, not the Bashkir Wikipedia... bs is the code for Bosnian, and ba for Bashkir.

@Halfak: Whoops, I totally forgot about this, and I didn't get that ping for some reason...

@Jdforrester-WMF: Any update on this? It's been a while.

Is it useful to have sr-cyrl-ekavsk, sr-latn-ekavsk, sr-cyrl-ijekavsk and sr-latn-ijekavsk and additionally sr-cyrl and sr-latn for words that don't differ between Ekavian and Ijekavian?

@Fomafix: If fallback works there as well, then move it to sr-cyrl-ekavsk and sr-latn-ekavsk. Otherwise, go with sr-cyrl and sr-latn.

It might have been intended for content which is why it wasn't used. Anyhow, it's pointless to dwell on the past. People nowadays clearly want the option to use the Ijekavian variant for the interface.

So, just to make sure, does that mean that the translations would be done in sr-cyrl-ekavsk, sr-latn-ekavsk, sr-cyrl-ijekavsk and sr-latn-ijekavsk? If so, it'd be great to get this done as soon as possible so we can start working on the -ijekavsk translations on TranslateWiki.

This means that all system message should be renamed from sr-ec to sr-cyrl-ekavsk. Are all current system messages in sr or sr-ec in the variant Ekavian?

What is the intended fallback between the new language codes?

Any update on this, @Fomafix? Would be nice to get this done so subtags can be added.

In T185421#3970563, @Liuxinyu970226 wrote:

I don't see how there's benefit to do so.

Here's a copy of MessagesSr_el.php (diff) and MessagesSr_ec.php (diff) with the Ijekavijan aliases.

Sorted.

Sorted.