Thanks for reporting this. For future reference, please use the feature request form (linked from the top of the task creation page) to create feature requests, and fill in all the sections in the template. Thanks.

And here is a very initial and very basic MediaWiki extension to use Chemistoid, https://github.com/ebraminio/InChI

CDK https://github.com/cdk/cdk supports different formats so I've deployed it on tools, see https://chemistoid.toolforge.org/InChI=1S/C6H6/c1-2-4-6-5-3-1 and it's source https://github.com/ebraminio/Chemistoid I'm planning to create a PoC MediaWiki extension to understand with something like this <InChI>1S/C6H6/c1-2-4-6-5-3-1</InChI> syntax, similar to math syntax and Interactivity can be provided later by JSMol

I don't insist on it much though I have my original opinion about it so let's close. Thanks 😊

That works also, I didn't know, but border-color: var(--border-subtle-color, #c8ccd1); doesn't.

I suggest using the background success color for these, as @Ebrahim did in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ORES/+/1050668

We have 1,362,174 uses of InChI according to Wikidata, https://www.wikidata.org/wiki/Special:WhatLinksHere/Property:P234

In T368637#9937285, @Tacsipacsi wrote:

I think specifying border-top-color, border-right-color, border-bottom-color and border-left-color, while looks ugly, should work.

Sorry for the noise, the patch wasn't related to this issue.

• https://gerrit.wikimedia.org/r/1050724 implements most of new properties introduced in CSS Logical
• https://gerrit.wikimedia.org/r/1050707 implements new values of float.
• start and end for text-align is already available.
• 'recto' and 'verso' for page-break also is already available.
• These https://drafts.csswg.org/css-logical/#logical-shorthand-keyword aren't finalized by the draft and not implemented by the browsers as far as I can see.

I'm trying to help a bit here, will update this comment

I wanted to make compatible with dark mode but knowing var are allowed by background-color but not border-color I only fixed background-color ones https://commons.wikimedia.org/w/index.php?title=Module%3ADiff%2Fstyles.css&diff=889925503&oldid=360425282

Ah I missed that but are you sure they are readable as it doesn't seem to be in Persian Wikipedia at least,

@Ebrahim would you be interested in helping me with this one too?

Thinking more I think we can also consider possibility of allowing .ttf/.otf without any preview or use as a webfont as the first step, considering https://commons.wikimedia.org/wiki/Category:Noto_fonts it's already obvious what it can be useful for, archiving source fonts in addition to dumped glyph of each set and with the vision to reverse that and only keep the source font remove all the glyph dumps (or no longer uploading newer).

Since this is a prerequisite here, does someone know how to map from wikihiero's input syntax to hieroglyph unicode text? I liked to do at least T214232 then maybe help resolving this (or T367644#9910748 whenever that happened) but found I even don't know how to find corresponding unicode of e.g. hiero_a&t&x.png and to find it from Noto Sans Egyptian Hieroglyph font.

Sorry for the repeated messages, hopefully this is the last of them for now.

Now the custom text logic seems to work more or less on the extension https://github.com/ebraminio/FontHandler which hopefully can show better what I'm suggesting here,

Here is a very very initial proof of concept of a MediaWiki extension I suggest,

Just a drive-by comment, I was just wondering anything else can be adopted from a quick look at https://blog.pecar.me/sqlite-django-config and https://fractaledmind.github.io/2023/10/09/sqlite-on-rails-enhanced-sqlite3-adapter/

AFAIU this exists, see

People subscribed to this thread maybe will find T367644 interesting.

what exactly is the issue here though

Sure jQuery.ui has lost importance ever since but it's still not unused as I've made aware one of the issue of one of the tools on Wikimedia Commons for RTL languages interface so have applied on Commons "html[dir="rtl"] .ui-dialog { right: auto; }"

I've just added it for Wikimedia Commons, thanks for surveying the solutions @Aram I used the information to apply the solution to Wikimedia Commons also

Sorry about the trouble it has made, it's great that you are adding a comment to the section so changes in the future can be done more carefully, just to note in future if you can design someway to change this, please go for numeric instead of uca-default-u-kn as it was on the initial versions of the reverted patch (weird that it has changed last minute, probably even my own fault 😞). Maybe uca-default-u-kn can be desirable sometime but perhaps another community discussion is needed for that I think as some may don't like that T32996#2342009 and the request here was only to enable numeric sorting. (and quick question from @Jdforrester-WMF, is a change from uppercase to numeric also this costly?)

as this request is about settings / configuration of a Wikimedia website. In the future, please always follow

I assume if I open a new file for the following it will be merged with this so am bringing it here that OOjs dialogs don't support dark mode,

(I was asked by Ladsgroup to do this assign)

For the reference, the mentioned path improvement and optimizations in the commit message which is done by the designer who is uploader of https://commons.wikimedia.org/wiki/File:Wikibooks-tagline-fa.svg and https://commons.wikimedia.org/wiki/File:Wikibooks-wordmark-fa.svg also are like this,

Wordmark of the new version is put at https://commons.wikimedia.org/wiki/File:Wikibooks-wordmark-fa.svg also.

The mentioned pages are merged now so one can only have a look at history of https://commons.wikimedia.org/wiki/File:Wikibooks-logo-fa.svg

Turned the implementation into what @cscott said at the review system,

{{dir:fa}} or {{#dir:en}} would be both fine. I would go with the {{#dir:en}} format so it looks like other parser functions. We can than do bunch of replacements on Commons.

In T359761#9807517, @Bugreporter wrote:

The implementation can't replace {{dir}} as that needs to be invoked like {{dir|fa}} instead of {{dir:fa}} (it's not possible to have {{dir|fa}} as a parser function) ...

See: T204371: Replace initial colon in (hash-prefixed) parser function invocation with vertical bar