On 1/26/2019 12:01 AM, Karl Berry wrote:
If the FontDescriptor dictionary of an embedded Type 1 font contains a CharSet string, then
I see nothing in that wording that implies CharSet is anything but entirely optional.
that was my impression so the problem is that as soon a some validator complains we tend to 'fix' it (by inclusion again) but we really should be willing to doubt validators (interesting is that for validating the correctness of a pdf document in terms of xref and such, many pdf tools are pretty useless: when it comes to viewing, gs, mupdf, qpdf, xpdf, web stuff all have tolerance and/or recovery built in so they react differently ... only (old) acrobats can be trusted in that department)
Anyway, right now the choices are a) omit /CharSet or b) output a possibly-incorrect CharSet.
maybe we should just make a statement and always do (a) ... and as most folks use resonable modern viewers, just ignore a validators complain in that area
If you want to have a third option c) <something else>, you (or someone) will need to send me a patch. (I highly doubt that Thanh has time to look into this.) Sorry, but that's the reality. -k _______________________________________________ ntg-pdftex mailing list ntg-pdftex@ntg.nl https://mailman.ntg.nl/mailman/listinfo/ntg-pdftex
-- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------