Southern Kurdish (sdh)
Currently, the aid/support language for Southern Kurdish is Persian. For the following reasons, I'd like Central Kurdish (ckb) to replace the role of Persian: 1. A significant number of Southern Kurds are in Iraq and don't speak Persian and do not benefit from seeing a Persian translation when translating into Southern Kurdish. They have have active news agencies, TV channels and websites that publish and broadcast in the Southern Kurdish dialect of Iraq. 2. Central Kurdish is the closest language to Southern Kurdish for which many items have already been translated and its speakers have managed to create several Wiki projects. 3. Even as of now, Southern Kurdish translators get inspiration from Central Kurdish translations and it's helped us a lot. TerranBoy (talk) 12:30, 7 September 2023 (UTC)
- @TerranBoy: Hi! Languages can have several fallback languages, as we call them. For Southern Kurdish, the fallback languages are already Central Kurdish and then Persian, in that order. That means that if a message hasn't been translated to Southern Kurdish yet, it will be shown in Central Kurdish, and if it hasn't been translated to Central Kurdish either, it will be shown in Persian (and then in English if there's no Persian translation either).
- By default, the assistant languages shown in the Translatewiki interface will be the fallback languages set for that language, so you should be seeing both Central Kurdish and Persian if translations into both languages exist; however, since Persian is a bigger language than Central Kurdish, it is likely that you will see only Persian in many places because a particular message hasn't yet been translated into Central Kurdish. Does that make sense? Jon Harald Søby (talk) 23:04, 7 September 2023 (UTC)
- @Jon Harald SøbyI see. But I think there must have been a mistake. The order may be the other way around. I haven't a single Central Kurdish equivalent being shown when translating into Southern Kurdish, even when the same text already has a Central Kurdish. Central Kurdish isn't shown at all. Additionally, for the interface language, I'm using Southern Kurdish and I see 80% Persian. For example, here at https://translatewiki.net/w/i.php?title=Special:Translate&group=wikimedia-tools-bookreader&language=ckb&filter=&action=translate , the first item is already translated into Central Kurdish. But it's not shown for Southern Kurdish.
- TerranBoy (talk) TerranBoy (talk) 02:23, 8 September 2023 (UTC)
- @TerranBoy: OK, thanks for the examples – I can confirm that I also experience the issue.
- I found the reason for this error. Instead of the first fallback language being set to
ckb, it was set to
cbk, a language code that is currently not supported by MediaWiki, and which is wholly unrelated to Southern Kurdish. I have submitted a fix for this problem, which will hopefully be merged and deployed here quickly (within a week, I believe).
- If you don't want to wait for this solution to appear here, you can set
ckb(and/or any other languages you want) as your personal assistant language in Special:Preferences#mw-prefsection-editing-translate. Jon Harald Søby (talk) 06:51, 8 September 2023 (UTC)
OpenStreetMap in Spanish is starting a reversion war
I am part of the OpenStreetMap-OSM community, collaborating on this project for a long time. I am also a Spanish speaker, and I saw a couple of months ago a lot of strings in the OSM website with many issues: lack of concordance (tu vs. usted), missing translations, etc.
I asked the OSM project about how to improve the translations in Spanish, and they redirected here (https://community.openstreetmap.org/t/accepting-users-terms-for-a-spanish-non-english-speaker/102093). I reviewed all strings (more than 2000) to validate that the user experience is the same across the entries. I mean the interaction with the user is "tu" instead of "usted", and always provide a friendly and close dialog.
However, some strings were reverted, and I consulted the OSM community what they think about this user experience (tu vs. usted), confirming me that they also prefer "tu" (https://github.com/openstreetmap/openstreetmap-website/issues/4238).
Also, I asked the OSM project maintainers if there were translation guidelines, and they provided me extra feedback to ensure the translation follows some structure (https://community.openstreetmap.org/t/spanish-osm-website-translation-mensajes-en-la-pagina-de-osm-deben-tutear-o-ustear/103509/1)
I have written to many translators here who have perform an invalid change, and most of them have replied me accepting the fact, or giving a valid feedback. However, the user Fitoschido has not replied me any of my messages in his talk page, and he has reverted me several entries. Lastly, he wrote me a message in my talk page (User talk:Angoca).
- @Fitoschido, do you have anything to respond? Amir E. Aharoni (talk) 01:35, 16 September 2023 (UTC)
- I can read Spanish, but I don't want to get too much into discussions of languages in which I don't write well myself. However, as an administrator, I sometimes have to get involved. For now, I find @Angoca's arguments because they cite multiple community discussions. Unless @Fitoschido cites something else, I'd say that Spanish OpenStreetMap translations should use tu. Amir E. Aharoni (talk) 15:41, 24 September 2023 (UTC)
Alesaru is a user that has recently started performing translations in Romanian. However, a part of them are of low quality, and at least 2 of them caused site-wide issues at ro.wikipedia.org. We suspect (the local Romanian language Wikipedia community) that this account belongs to a LTA vandal at Romanian language Wikipedia. We are discussing the possible necessity of a mass revert (and I think that also an indefinite block might be necessary). See these 2 discussions: Lipsă spații după virgule în interfață (permalink) and Titlul filei (permalink).
- I've removed the translator permission from that account. Amir E. Aharoni (talk) 02:28, 25 September 2023 (UTC)
Fuzzy messages for Dissemin not showing up
In the Dissemin project, a lot of existing translations have been marked !!FUZZY!! for a long time, but they are not showing up as obsolete in the statistics overview, so these fuzzy translations have never been updated. McDutchie (talk) 20:35, 24 September 2023 (UTC)