| | <<<Back 1 day (to 2014/06/28) | 2014/06/29 |
| who_me | hi. is the fact that my printer is shown as being capable of higher resolutions than it can actually do a driver issue or a cups issue? I want to know where I should report the problem. | 06:42.04 |
| | hi. is the fact that my printer is shown as being capable of higher resolutions than it can actually do a driver issue or a cups issue? I want to know where I should report the problem. | 09:38.22 |
| Robin_Watts | In what way is ghostscript involved? | 09:45.21 |
| who_me | Robin_Watts, is pxlmono related to ghostscript? | 09:49.05 |
| | Robin_Watts, this page says it is: http://openprinting.org/driver/pxlmono | 09:51.13 |
| Robin_Watts | pxlmono is an output device of gs, I believe. | 09:57.39 |
| | but it's not specific to any particular model of printer. | 09:57.56 |
| | so it can cope with any resolution (within reason) you throw at it. | 09:58.12 |
| | If it's being exposed as a driver or something on your OS (perhaps through cups) then that is a question for the people developing that driver, rather than for us. | 09:58.42 |
| sebras | tor8: (for the logs) commit bb66f6335fce7cacf83fa6289eb3b433c4e29b6a causes https://github.com/jordan-fontorbe/TER/blob/master/Document-ollinger/IMX50RM.pdf?raw=true to take approximately 1.8s to open on my computer. prior to this commit opening this file is instantaneous. | 18:45.37 |
| | tor8: I think this is due to us re-reading the link destinations no less than 12 times. | 18:52.01 |
| | tor8: I wonder if 1.8s is not just the normal parsing time for the outline for the entire 3300+ page document. and previously we skipped most of the parsing so it seemed faster but it was inaccurate... | 18:55.49 |
| | Forward 1 day (to 2014/06/30)>>> | |
IRC Logs