Open GoogleCodeExporter opened 9 years ago
Confirming the bug. Unicode Nameslist clearly mentions need for both U+2E30 and
U+2E31 (I can confirm personally too, I had a hand in encoding both characters).
I just added a test to our lint tool to check for their availability
(https://code.google.com/p/noto/source/detail?r=1466e0a).
Assigning to Monotype for adding the glyphs to Noto Sans Avestan.
Original comment by roozbeh@google.com
on 3 Apr 2015 at 1:42
Original issue reported on code.google.com by
pim.riet...@gmail.com
on 2 Apr 2015 at 9:48