A discussion in the UX category addresses a backtick rendering issue caused by the NotoSans font in text boxes. P16 reports that backticks are improperly displayed—showing only one, indented, and overlapping text—when using NotoSans. awesomerobot confirms this is a known issue linked to a GitHub bug report and suggests removing NotoSans, noting Open Sans as a similar alternative. P16 asks if updating the font version could resolve it. amundo expresses relief at the topic’s arrival, while sam clarifies that NotoSans is redistributed via the discourse-fonts gem and that a fix exists in a newer build. awesomerobot confirms the font will be updated, with the fix already committed here.
Changing the default font to NotoSans creates a strange bug where backticks are not rendered properly in any text box (See video below for reference):
Bug gets resolved when not using NotoSans, which is a shame as it is a beautiful font 
Unfortunately this is a known problem with the font!
https://github.com/googlefonts/noto-fonts/issues/736
We should probably remove it from our site settings, we already have Open Sans, which is very similar and doesn’t have the backtick issue.
Thanks @awesomerobot. It says the issue was fixed in newer versions - would it be possible to update the font instead of removing it?
So happy to see this topic, this big has driven me bonkers for ages.
Time for me to nix Noto.
So does Doscourse distribute Noto as opposed to using the web font?
We redistribute the fonts in our discourse fonts gem. My take from reading the giant topic on GitHub is that there is a build with this fixed. Not sure we need to nuke Noto, just update the font but deferring to @awesomerobot on this.
Yeah we can just update it, that seems fine!
I’ve updated the font in our gem, so this should be updated soon!
https://github.com/discourse/discourse-fonts/commit/3edb86923f21b9d2f79526e6312023fae24a19e2