Re: CJK fonts
Glenn Linderman <[email protected]>
| Newsgroups | gmane.comp.python.reportlab.user |
|---|---|
| Message-ID | <[email protected]> |
On 6/20/2011 2:32 AM, Robin Becker wrote: > In the TTF fonts the assumption is that they cover all of utf8/unicode > and we make lazy subset fonts so we don't get errors at the right > time; in fact we only detect that the font lacks a glyph when we are > building the subset. That means we might end up trying to build a > subset for a different font in the middle of building subsets. I'm not > sure how feasible it would be to do that. Three and a half years later (yeah, I got distracted), I've finally learned enough to understand and appreciate what you said there. So if you don't detect the missing glyph until building the subset, that means you can detect it then. For efficiency, I can understand why it might be deferred, allowing and assuming the user specifies the right font for the particular characters. But this user doesn't always know. Now I could make an assumption about certain character ranges being in certain fonts, but is there a way I can ask reportlab "Does this character exist in this font?"