The rendering for the Hindi text - ट्विस्ट - seems incorrect

[kirsn]

1. Steps to reproduce - View the Google Fonts link for Noto Sans, with the Hindi text
2. Observed results - the Noto Sans Devanagari rendering is incorrect
3. Expected results - whereas the Noto Sans Japanese or any variation other than Devanagari renders the text correctly

A screenshot of the rendering on the Google Fonts site. The last rendering is the right one.

[simoncozens]

Confirmed, we seem to have lost a conjunct here.

[simoncozens]

Wait, we've never had that conjunct. That "Noto Sans Syriac" is some (Apple?) fallback font. It would be nice to have it, but this isn't a regression.

[kirsn]

Thanks for the response.

The font renders as expected for every variation (language variation) other than *Devanagiri, and Noto Sans.... as the screenshot below indicates

[simoncozens]

Right, but this is because you are seeing a different font in your browser - the fallback font which is the default Devanagari font for your system. If a font does not contain codepoints for a certain script - for example, Noto Sans Arabic does not contain any Devanagari characters! - then the browser will choose a different font instead. So where it says "Noto Sans Arabic" you are actually seeing something like Mangal Pro.

[kirsn]

Thanks for the clarification; helped me understand the issue better.
As per your earlier comment, this conjunct may be considered for inclusion in Noto Sans at some point?

[simoncozens]

I think it is a fairly rare conjunct, and a challenge with Devanagari is that there is not really an end to the process. You have to draw the line somewhere. Every extra byte of Noto Sans/Serif Devanagari is multiplied over billions of devices. Nevertheless this is quite a well-supported conjunct and probably should be added at some point: