At present there are the following, stripped of the "Index:" prefix, that appear in only one of the lists Andre linked to:

In T61983#3895884, @Dzahn wrote:

please see T184664#3895870

noto fonts are now installed on mediawiki app servers

I compiled the latest SVN version here, @Aftabuzzaman, and the Bengali edit summaries show up. Here's hoping that there is an official release soon, @Reedy, @Rjwilmsi, and @Magioladitis.

I am rewriting it now to support modern graphics libraries that allow different fonts, ligatures, right-to-left etc.

I'd go ahead and close this as invalid. He should be made aware of the need to reupload the image in question to Commons, though.

La imagen de lo que escribe Ud. no fue subida en Commons y por eso no la puede usar. Tiene que subirla allí, y ya que la licencia de la imagen es CC0 lo puede hacer si mismo.

@Aklapper You appear to have mistyped his username. This seems related to T186945.

I just noticed, @Reedy, that only a select few Noto fonts are actually in the noto-fonts package; the rest are in noto-fonts-unhinted and noto-fonts-hinted, so they should be added as well. (There are also noto-cjk and noto-cjk-extra, but I’d rather speakers of languages using those fonts weigh in for those.)

Per T184664 Noto fonts will soon be available for rendering SVG images. These necessarily include (not yet since those particular fonts aren’t available in Debian jessie) Noto Sans Bengali and Noto Serif Bengali. @Aftabuzzaman @MoheenReeyad @Tarunno what do you think of those two fonts?

Per T184664 Noto fonts will soon be available for rendering SVG images.

On a related note, per T184664 Noto fonts will soon be available when rendering SVG images.

The idea, @Ebe123, is for this module to take LilyPond markup and render it as the appropriate series of tables (it may however be advantageous if these tables are produced graphically to reduce DOM clutter rather than rendered by the browser)—in other words, have the separate "\relative c" and "\addlyrics" commands such that the regular score extension with the markup gives you the Western notation and this module with the markup gives you the swaralipi equivalent. (Here, for example, ideally the same LilyPond markup should be used for outputting both of the staves, which represent the second line of music on this page.) Hardcoding the tables is not optimal and prevents reuse in other notation formats, which reduces the accessibility of this music only to those able to read (this format of) swaralipi.

The previous bug report by @jayantanth himself was closed as invalid. Also the format used by Tagore (as shown in the link in the task description) differs in several respects from that used by, for example, Hindi/Marathi composers (see the page previews here and here), so simply asking the developers to support 'swaralipi' makes little sense.

@greg Okay, thank you for the clarification. I will close this task after Monday, then. (Probably should fix the URL I linked to, though.)

@Sjoerddebruin @Smalyshev @greg What’s up with https://tools.wmflabs.org/versions/ then? Are dewiki and wikidatawiki versions just not reported correctly there?

@debt No, the results are simply not appearing. The JSON response is still normal, up to the warning I mentioned above, but the results do not render on screen. The symptoms as listed in the task description still persist. See the screenshot in the task description.

This task reminds me of T114318.

In T173145#3527784, @dbarratt wrote:

Are you implying that, to understand any of the arguments posted here, I must first acquire a 'secret knowledge' that can only be obtained by further participation in the community?

In T173145#3524145, @dbarratt wrote:

I do not understand the validity of any of these arguments.

Added three supporters and three opponents of a related property proposal. (I wasn't able to find Innocent bystander on Phabricator.)

(subscriber removed in the spirit of @Sjoerddebruin's request)

I would also recommend Hind Siliguri and Noto Serif Bengali (both SIL OFL). I am unaware of any fonts that encode U+09FC and U+09FD yet.

@Reedy, @MarcoAurelio As I was not then subscribed to the wikisource-l mailing list, only now did I find this thread detailing more of @Bodhisattwa's motivations.

@Reedy: A rendering of the first part of @Bodhisattwa's community notice:

While the specific bug is quite important to fix, I must note that that particular image is intended to show what it showed before Suyash and Shyamal's recent changes--that is, the appearance of the Devanagari on Wikipedia's logo prior to mid-2010--and thus the specific edits that were made to 'correct' it have been reverted.

@Koavf: I am not a Hindi speaker, but I can at least discern Devanagari text and the English loanwords in it. Your first link is to "Category:Intelligence" with subcategory "Artificial intelligence". Your second link (Computer Programming/IDE/Visual Basic .NET/...) bears only a link to a Japanese online IDE. Your third link (Computer Graphics/2013-2014/"Page Foot", a page footer which is transcluded elsewhere) has an email address prefixed with a link to @Jayprakash12345's userpage--maybe it is his own email address?

This character (U+0445), অ (U+0985), Յ (U+0545), օ (U+0585), ׅ (U+05C5), अ (U+0905), Ӆ (U+04C5), and ԅ (U+0505), all possibly among others, all trigger this error. I was attempting to use the second (which generated this error), and seeing that both অ's and х's UTF-8 representations ended in 0x85 tried the rest of the characters in that list.