Open GoogleCodeExporter opened 9 years ago
Er, uh, the same comment equally applies to Extensions C through E (Extension E
is being added to Unicode this year as Version 8.0). To play the devil's
advocate, I feel obliged to point out that it takes a non-trivial amount of
time to design glyphs for the tens of thousands of CJK Unified Ideographs that
are in Plane 2, so a great deal of patience is necessary.
Original comment by ken.lu...@gmail.com
on 26 Jan 2015 at 10:02
Well, sure. Things do take time. At least we should probably document where
we are along the continuum from mo-tofu to noto-fu. I suggest a character set
coverage table or something. The project proposes to be a font for all of
Unicode, but if stuff like Extension B (which was in Unicode 3.1, and is 14
years old now) are always going to be on the nice to have list, then maybe we
need to call it "lessto", not "noto". I happen to care about Extension B
because my genealogy data includes given names which are out there in ExtB, so
they are (typically) tofu on my family tree website. It's also useful for
testing surrogate pair support with real text.
Original comment by swa...@yelp.com
on 26 Jan 2015 at 11:33
Original comment by stua...@google.com
on 28 Feb 2015 at 12:32
Original issue reported on code.google.com by
swa...@yelp.com
on 26 Jan 2015 at 8:46