הלוואי שהיה קל לדווח על בעיות בכל שפה.
את התמונה שלי צילם עמיתי קרטיק מיסטרי.
I can do this technically, but just for verification: Was there any discussion about this among Kurdish speakers elsewhere? For example, on the Kurdish Wikipedia talk pages?
... And another, more general, follow-up: T187721: Resolve Zawgyi and Unicode issues in MediaWiki core.
Indeed, this is probably fixed, although I'm not sure how.
Sorry, no. I had tried, and the most that I managed to do is to make it work with SVG, although it wasn't perfect.
I agree. I'm not sure what is the problem. Selecting the same engine brings back user's changes, so no data is lost. I just tested it.
It doesn't sound like an exceptionally complicated thing to fix, but I don't even know where are these strings.
I couldn't reproduce it in Firefox or Chrome on Mac.
Tested in production. Thanks!
Thanks for fixing.
Verified in production. Thanks!
Is it important? I use Wikidata in Hebrew, and I actually find this (possibly unintended) feature convenient, but maybe it's because I'm accustomed to typing the date according to the xkcd 1179 standard (a.k.a. ISO 8601).
All the most common cases listed in the current task description are fixed. I tested this in production on the Catalan Wikipedia. Tomorrow this is supposed to go out to all the other Wikipedias.
Is anything blocking this?
Is this in the CSS tab in the developer tools? These messages probably indicate issues with some CSS files that you are using, but not something that causes a crash.
Browsers, indeed, provide spellchecking capabilities. Safari on desktop even provides autocompletion, similarly to mobile phone keyboards.
Scheduled for deployment later today.
Looks like you are running a user script Benutzer:Schnark/js/fliegelflagel.js/load.js from your common.js. Can you please ask the user script author to check this?
Examining the suggestions from the task description:
I'm a bit confused: Isn't the whole point of these shim templates to make translation easier? Aren't they at least supposed to be more suitable for use for Content Translation?
Why lengthy discussions?
Oh wow, one of my oldest!
I see "one more" at these pages: