User talk:MF-Warburg

• Archive 2007–2011 (diff, oldid)
• Archive 2012 (diff, oldid)
• Archive January–June 2013 (diff, oldid)
• Archive July–December 2013 (diff, oldid)
• Archive 2014 (diff, oldid)
• Archive 2015–2016 (diff, oldid)
• Archive 2017–2021 (diff, oldid)
• Archive 2022–

SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 3 days and sections whose most recent comment is older than 31 days.

Serbo-Croatian interface translation question

Dear MF-Warburg,

The Serbo-Croatian-speaking area has seven different interface translations:

• bs – Bosnian
• cnr – Montenegrin (could split eventually to cnr-cyrl and cnr-latn)
• hr – Croatian
• sh-cyrl – Serbo-Croatian Cyrillic
• sh-latn – Serbo-Croatian Latin
• sr-ec (renaming to: sr-cyrl) – Serbian Cyrillic (could split to sr-cyrl-ekavsk and sr-cyrl-ijekavsk)
• sr-el (renaming to: sr-latn) – Serbian Latin (could split to sr-latn-ekavsk and sr-latn-ijekavsk)

There is also an idea to split sh-cyrl and sh-latn with -ekavsk and -ijekavsk (Phabricator task). Translation in sh and sr is disabled as fallbacks exist.

However, this situation is not sustainable. We are kind of wasting resources and many messages are simply duplicated. For example, sh-latn mostly matches bs, and sh-cyrl matches sr-ec (with both codes having these fallbacks).

I would like to hear what is the stance of LangCom about this:

1. Do we want to centralize and integrate into sh macrolanguage code (with translation only in sh-cyrl-ekavsk, sh-cyrl-ijekavsk, sh-latn-ekavsk, sh-latn-ijekavsk)?
2. Do we want to decentralize and disintegrate the macrolanguage translation to variants (with translation in sh-cyrl and sh-latn disabled as fallbacks exist)?

Thank you in advance, Aca (talk) 14:14, 20 April 2025 (UTC)

User:Aca: I'll bring this up in Langcom. --MF-W 09:19, 15 May 2025 (UTC)

Thanks! This question can also include translation on Meta-Wiki (and elsewhere, where the Translate extension is used) and Wikidata (e.g., labels, aliases, and descriptions). – Aca (talk) 15:46, 15 May 2025 (UTC)