all devices regression report - 2018-04-11-12:50:53 - 36e7d38af2a11b5e4d7117ddd0ebf7326fad7c72
[email protected] Wed, 11 Apr 2018 12:50:53 -0700 (PDT)
| Newsgroups | gmane.comp.printing.ghostscript.regression |
|---|---|
| Message-ID | <20180411195053.4F95620404B0@i7> |
Differences in all devices errors using gs/examples files Previous Revision: 890e637bf7a1d8a5e3438c2aab4e0eef33d795f1 Current Revision: 36e7d38af2a11b5e4d7117ddd0ebf7326fad7c72 commit 36e7d38af2a11b5e4d7117ddd0ebf7326fad7c72 Author: Chris Liddell <[email protected]> AuthorDate: Tue Jan 30 09:31:04 2018 +0000 CommitDate: Wed Apr 11 08:34:19 2018 +0100 Bug 698767: Improve handling of multiple master fonts The FAPI API didn't really handle the possibility that multiple master fonts could change (via setweightvector) without a call to definefont/setfont etc. We now allow two ways for FAPI to handle this: if the scaler in force allows it, we'll set the new weight vector, and carry on as before. If the scaler does *not* allow us to change the weight vector "on the fly", we'll destroy the scaler's font object and related data, and recreate it with the new weight vector in the font dictionary. base/fapi_ft.c base/fapibstm.c base/fapiufst.c base/gsalloc.c base/gxfapi.c base/gxfapi.h base/write_t1.c psi/zfapi.c new errors: errors that went away: errors that are not whitelisted: === ghostpdl/examples/text_graph_image_cmyk_rgb.pdf === pxlcolor === === ghostpdl/examples/text_graph_image_cmyk_rgb.pdf === pxlmono ===