| <<<Back 1 day (to 2017/08/03) | 20170804 |
irctc620 | Hello Everyone | 06:04.55 |
| When i Clone Git Url i can not show Android and iOS platform | 06:10.39 |
chrisl | I assume you mean for mupdf? | 06:21.23 |
| irctc620: ^^ | 06:21.40 |
irctc679 | hi | 08:12.50 |
ghostbot | Welcome to #ghostscript, the channel for Ghostscript and MuPDF. If you have a question, please ask it, don't ask to ask it. Do be prepared to wait for a reply as devs will check the logs and reply when they come on line. | 08:12.50 |
deekej | chrisl: hello Chris! I've opened this BZ (https://bugs.ghostscript.com/show_bug.cgi?id=698333), but later found out fontconfig upstream has already done the same work | 12:06.43 |
| chrisl: could you please ignore it, until I hear back from fontconfig upstream? thanks | 12:07.00 |
kens | I've seen the bug, chris is afk at the moment | 12:07.02 |
| Oh OK I'll tell him | 12:07.13 |
deekej | I just want to avoid a situation where the fontconfig files would suddenly live in 2 places at one :) | 12:07.32 |
| *once | 12:07.35 |
kens | Yeah best to avoid that | 12:07.44 |
ray_laptop | There was a comment/question recently (from a customer and from some Artifex folks) about "how ghostscript sets device parameters during startup". This is done by gs_init.ps in the section following the comment % Set any device properties defined on the command line. | 17:02.30 |
| other than a little "special" adjustment with BufferSpace and MaxBitmap, the general process is: 1) use "getdeviceprops" to get the list of parameters known to the device, next | 17:06.04 |
| 2) any parameters that are defined in systemdict (which is what putting -d___ or -s___ on the command line does) are retained, otherwise they are discarded (pop pop), then | 17:06.07 |
| 3) "putdeviceprops" sets the command line value of the parameters for the device | 17:06.36 |
| This works for most simple cases, but there are a couple of issues that can arise: 1) parameter types that are not simple values (-d___=numeric, name or true/false), or string (-s) cannot be used (e.g., arrays or dictionaries) | 17:09.46 |
| 2) once initialization is performed, subsequent -d___=___ or -s___=____ will define those values in systemdict, but will NOT send them to the device. Since initialization is completed before -c arguments are processed, any device parameters must precede -c (or -f or an input file) | 17:12.07 |
| 3) interpersing files to be processed with device parameters won't work. For example: "-dUseFastColor file1.ps -dUseFastColor=false file2.ps" will run file2.ps with UseFastColor set to true | 17:15.30 |
raypc | comments about gs_init and device params also added to bug 698334 | 18:54.46 |
| Forward 1 day (to 2017/08/05)>>> | |