If you don’t write the font “exactly” you might run into copyright/TOS problems.
In most cases though, you are better off using standard fonts and using the correct name in the pdf - and let the viewer find/replace the font - you will not have a problem in that case. > On Feb 5, 2021, at 5:08 PM, Nigel Tao <nigel...@golang.org> wrote: > > >> On Sat, Feb 6, 2021 at 9:18 AM Nigel Tao <nigel...@golang.org> wrote: > >> It doesn't have any in-memory representation of the not-frequently-used >> parts, including the actual glyph vectors. > > Correction: it doesn't have not-frequently-used or too-big-to-cache parts, > and glyph vectors are the latter. Avoiding "takes double the memory" is > precisely the concern. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/8B99EFCC-5514-423C-9473-10E6E751DB59%40ix.netcom.com.
