@Amire80 People's Archive of Rural India uses the spelling "गुज्जरी", an endonym. Aaley et al. (2019. Kusunda 250 Word List Audio Files. http://doi.org/10.5281/zenodo.3377537) as well as Watters (2006: 139-152) both mention the endonym of the Kusunda language as "gejmehac/gejmehaq gipan". I reached out to Aaley to ask for the correct Devanagari spelling and "गेम्येहाक़ गिपन". He is also the lexicographer of the Kusunda-Nepali-English dictionary "Kusunda Jati ra Shabdakosh," which mentions this spelling. The first word, "Gejmehac," and the second word, "gipan," can be heard respectively in this and this respectively, taken from a 2018 interview with Gyani Maiya Sen-Kusunda, one of the two fluent speakers alive in 2020 (she died that year and her younger sister Kamala is the only fluent speaker of the language). "ରେମସାମ୍" is mentioned in the 1998 eponymous book by Gobardhan Panda. I hope these suffice.

In T381934#10470326, @Nikki wrote:

In T381934#10432671, @gerritbot wrote:

Change #1108403 merged by jenkins-bot:

[operations/mediawiki-config@master] Add bfw, gju-arab, gju-deva, hoc and kgg to wmgExtraLanguageNames

https://gerrit.wikimedia.org/r/1108403

gju-arab needs a MessagesGju_arab.php file in core (see MessagesOta.php for example) so that MediaWiki treats it as rtl.

bfw and kgg need adding to LocalNamesEn.php in the CLDR extension.

bfw, gju-arab, gju-deva and kgg should be added to the language-data repository.

For consistency, bfw, gju-arab, gju-deva and kgg should also be added to WikibaseContentLanguages.php in the Wikibase extension.

@Anoop, thanks. [https://phabricator.wikimedia.org/T383785 Done].

Another language I want to request adding is Desia ('dso' => 'ଦେଶିଆ'). It's a part of the Odia macrolanguage. Predominantly a spoken lect, it can be written in the Odia script.

Hi @jhsoby et al., while these languages appear in videos after SRT files are uploaded, I still don't see the language name in the dropdown while uploading.

Thanks much @jhsoby! Let's see how it goes.

Happy New Year @jhsoby. Thanks for the flag. jgu should indeed not be needed, making space for gju-arab and gju-deva. we should have 'hoc' => '𑢹𑣉𑣉 𑣎𑣋𑣜', instead of 'hoc' => 'Ho' which is in Warang Citi, the script used widely by native speakers. bfw and kgg are predominantly spoken languages. The majority of the literate Bonda ('bfw') speakers would know Odia, the official script for the Odia language of Odisha, where the speakers live, and some books have used Odia in publications, but there is no standard script. Similarly, kgg also has no native script, whereas most literate speakers are in Nepal and are fluent in the Devanagari script. bfw is ରେମସାମ୍ ("Remosam", an endonym) in Odia script and kgg is गेम्येहाक़ गिपन("Gejmehac Gipan", the endonym).

Hi @jhsoby and other friends: I wanted to follow up and check about this again. Will my last suggested options work? If so, what would be the next step?

Ok, we can have just the following for the time being:

@Aklapper, yes, @Jnanaranjan_sahu seems to be on this. BTW did you see the ENWP screenshot and the issue? Might be something to check before closing the issue.

@mrephabricator, Gujari is actually written in multiple scripts. Most Gujari speakers in India are in states where Hindi is a dominant and official language, and in Nepal where Nepali (written in Devanagari) is the national language. Gujari is predominately an oral language and is not taught widely in schools or is used in media or publications. So, those residing in India and Nepal learn Devanagari due to school education and use it for Gujari when they need to. Van Gujjari, a variant of Gujjari, uses Devanagari for this reason even though all Van Gujjars are Muslims who would have preferred Perso-Arabic over Devanagari. Over 174 books are translated and several books are published in Van Gujjari and these are in Devanagari. Gujjars living in Pakistan and Afghanistan would use Perso-Arabic. For that reason, keeping the name in both Perso-Arabic and Devanagari might be helpful (I've edited my earlier comment). Thanks for suggesting this.

Thanks for the clear guidance, @jhsoby.

The reproduction steps are right. You're unable to edit as it's restricted to admins only. A notification similar to "MediaWiki:Titleprotectedwarning/or" on Translatewiki appears automatically. I couldn't find any special CSS change made for a notification for protected pages. However, the first screenshot in my original message show the text with sever accessibility issues.

@TheresNoTime, I'd really like to draw your and other stewards' attention to the issue with IP edits. We're a small community with a handful active editors. Only two admins are active (I'm personally less active now and counting MKar and Jnanaranjan_sahu). The recent 2024 general elections has led to significant political shifts and a huge number of articles are being vandalised, edited without following Wikipedia MoS, and is adding more to the burden Ssgapu22, MKar and Jnanaranjan_sahu are taking through co-leading an editing sprint dedicated to the elections-related articles. This is literally setting up a small community to fail as the three-four active contributors are overwhelmed with the amount of IP edits. It'd take months or more to go through each edit, remove incorrect info/formatting, and keep and modify the rest. As a local community we need some control locally. There are hundreds of articles that are being and about to be changed like this. Can we at least temporarily, for a couple of months, allow only logged-in editors to create new articles/edit existing ones?

Hi @Bugreporter, I tested the two examples I shared using Z10553 and the output is void for both.

@Anoop: thanks for pointing at the meta-wiki page -- let me share more background against all the criteria mentioned:

I wanted to highlight that it's been nearly 1.5 years, and this issue remains unsolved. An entire historically and socio-economically marginalized community cannot even upload a file in its native script. Ganesh Birua shared earlier about this issue and it reminded me the frustration a group of young people who excitedly gathered once to record pronunciations of words using Lingua Libre only to fail collectively. Ganesh has been building a dictionary, brick by brick, with his limited time and finds out that he can record the pronunciation. I tried it myself (see screenshot, Firefox 111.0.1), and it failed just like before.

Thank you much everyone!

Thank you @Amire80, @Bugreporter and @Nikki for helping out. As I am not, and probably @Biswajeet3 is probably not too, very aware of JS or how to fix this, I am going to wait for anyone who knows it well. To address the last part of Nikki's comment, I think Warang Citi's range(118A0–118FF) is relevant to this particular bug. But as Amir rightly points out, many other writing systems also suffer because of the larger issue. To test, and for Biswajeet and my own selfish reasons, it would really great to make things work for Warang Citi to test. I am a bit worried that the participants, who form a potential new set of contributors, of a workshop that Biswajeet and I conducted might completely forget if things take too long. Thanks in advance to whoever is helping out.

We reported this issue on the day of a workshop. To our frustration it did not work for any when the participants were trying to upload the pronunciations. If this bug remain unattended the problem is not fixed, the participants will probably forget. I'd request to the developers to help provide the ways to address this issue.

This was detected while many were trying to contribute pronunciations using Lingua Libre. So we created a few sample recordings (Ho-aandi.wav, Ho-andhratayed.wav, Ho-andun.wav) with Audacity and tried to directly upload to Commons using Upload Wizard and failed as the Warang Citi characters in the filenames were not recognized. So, we had to rename the files with transliterated Latin names and uploaded. This is the suspected reason for all uploads failing while attempting to record and upload using Lingua Libre.

I just downloaded using the exporting link above and it still shows the text in the same typeface with rendering issues. The svg remains the same like before.

Thanks Sam for the quick action. I have translated the messages. When Noto Sans Oriya has fixed the font issue, I still see the English messages instead of the Odia translation. It probably takes some time?

Thanks much, Sam!

Please do add the Odia (ISO: or) logo to this list: https://commons.wikimedia.org/wiki/File:Wikisource-logo-or.svg

As it has been over seven months I wanted to flag again and would request for further updates. Thanks.

The XY problem is an interesting perspective -- it helped me look at this whole thing from a different angle. That said, I'd like to ask you something too. When you're saying "I have a device" what is the persona of this person that you're assuming? The persona of an average Odia speaker who would read Wikipedia goes like this:

In T253712#6196130, @Aklapper wrote:

the default writing system on ULS should be Arabic and not Latin.

I would disagree here (if I understand correctly): The default input method should be the one defined by your operating system that is running on your device.
It would not be a good user experience if a website silently preselects some input method for you (plus many languages have more than one input method, which one to preselect?) and you suddenly type in a different script and different letters are shown on the screen than the letters on your keyboard that you just pressed without having an idea what is happening.
@psubhashish1: Wouldn't that be totally confusing to a user? (Or do I misunderstand you?)

Updated in the first message in this thread.

By project I meant a Wikimedia project. I opened Odia Wikisource in private mode (Firefox 76.0.1) as well and the default input is still Latin.

As someone who works with audio quite often, I wanted to add that noise is complex and not same universally. It totally depends on the recording gear, environment, unique voices each individual has. To put it in simple terms, if the high and mid frequency in the voice of a person are significant, a part of their voice might get removed if an auto-noise cancellation is used. This might make the recordings not so useful for any future text-to-speech projects. Many people including myself use pro gears for recording which already cleans up background noise. If a default noise cancellation/fading option is applied, it might affect the voice. So, any experimental noise cancellation feature should be kept optional.

1) What you expect and why:
As the project's primary language is Odia, the input method which is default for Odia on ULS should be enabled instead of Latin appearing by default. The reason being many new contributors might not log in or know how to change it in the very first place. Keeping the default input in the writing system that is used for the project will help.

Adding that this was recently discussed on the LinguaLibre discussion page.

In T253712#6168400, @Aklapper wrote:

Open a page that is yet to be typed on Odia Wikisource in private/incognito mode in any browser.

The link above is NOT to a page on Odia Wikisource. Hence the steps are either incomplete or wrong. That page explicitly says "This is the multilingual Wikisource".
Please correct the steps to reproduce. Furthermore,

If this is about taking into account your web browser setting for preferred languages, I'd wonder which input method (if there are several available for a language) should be used?

Tested on Odia Wiktionary on Firefox 63.0.3. Syntax Highlighting and ULS don't work at the same time. I had to disable Syntax Highlighting to be able to use ULS.

Thanks for the ping @Amire80. It does not appear anymore.

It's working now. Thanks a lot all of you! :)

Both UplodWizard and other Move-Files-To-Commons tools but most importantly UploadWizard.

Hi guys, you might have seen this already. The blog has gone live little early. Thanks for the great post. Cheers!

Hi @MelinaMasnattaWMAR83 @Paolaricaurte @TFlanagan-WMF please find the blog draft here. Please feel free to share with us about any changes you need to be done. @mcruzWMF and I would love to reflect them. As the blog draft has been submitted to the WMF blog team we would really appreciate if you could share your suggestions for any correction by this week. Thanks in advance. :)

@Billinghurst Just curious why there is a need for a consensus to have a really essential feature on OR WS? Is it not understood the default features should have been made available in the beginning of the project release but has somehow not been made available so far?

Hi @KartikMistry, can you ignore 403 and 408 and use https://github.com/wikimedia/jquery.ime/pull/421 instead? As it was showing problem for mine, another Odia Wikimedian Gyan111 fixed both or-odiscript and or-lekhani. Can they be rebased now?

Hi @KartikMistry, please find the updated layout for Rodali at https://github.com/psubhashish/jquery.ime/commit/7524a1a3da55afcce4cdf48bbad251b20f77f413. I have also forwarded Gunadeep's email for verification. Thanks.

Hi @KartikMistry, thanks for starting this. @Amire80 actually has the email for the correct IME for as-rodali as Gunadeep, the developer faced a lot of problem in forking and submitting the request. He finally could not submit it from GitHub and sent an email to Amir.
The Odia ones are correct.

Hi @Nemo_bis, did not understand how a longer conversation could be too messy to turn a grave problem invalid? Do you regularly upload non-free images in your home wiki? If you did, then you must have understood the problems Wikimedians face. Not just in seeing hundreds and thousands of pages of pages without images, but showing the same to institutions and participants in outreach sessions is painful. You may delay or ask for more clarification. But closing down a request, especially when there is a unanimous consensus from the community is very nonsensical, sorry to say this bluntly.

Hey @Mdann52, can you point to the restrictions with fair use in India. Being a citizen, I am not aware of any. @Sipun also has mentioned how Bengali and Hindi Wikipedia allow fair use. Both are official Indian languages.

Hi @Krenair, yes. There is a consensus and it has been unanimously agreed that there is a need to re-enabling local file uploading on ORWP.

@Aklapper: Sorry for that. I was not aware as I was reporting a bug of this kind for the first time. Thanks for helping out. Hope this will be solved soon.