The editor now bundles Charis SIL plus Noto Serif for the Indian scripts and Noto Naskh for Arabic (#448), but the source column does not get any of it.
Source verses render as plain elements in DraftingGridVerse.tsx and PericopeRteGroup.tsx with no scripture font class, so they inherit the app font. That is Inter, which covers Latin, Cyrillic and Greek. A Devanagari or Tamil source falls to whatever the machine picks, which is the same problem #444 described for the target side.
The narrow fix is to append the same Noto families to the source column's stack. That fixes the missing glyphs without changing how Latin text looks.
The wider question is whether source scripture should use the same serif as the editor. #443 was about making the two columns match, so there is an argument for it, but it changes the look of the source column and that is a design call rather than a bug fix.
The editor now bundles Charis SIL plus Noto Serif for the Indian scripts and Noto Naskh for Arabic (#448), but the source column does not get any of it.
Source verses render as plain elements in
DraftingGridVerse.tsxandPericopeRteGroup.tsxwith no scripture font class, so they inherit the app font. That is Inter, which covers Latin, Cyrillic and Greek. A Devanagari or Tamil source falls to whatever the machine picks, which is the same problem #444 described for the target side.The narrow fix is to append the same Noto families to the source column's stack. That fixes the missing glyphs without changing how Latin text looks.
The wider question is whether source scripture should use the same serif as the editor. #443 was about making the two columns match, so there is an argument for it, but it changes the look of the source column and that is a design call rather than a bug fix.