| | <<<Back 1 day (to 2016/07/02) | 20160703 |
| sebras | when my RGB fz_pixmap has alpha, then the 8-bit components are supposed to be stored samples[0..3] == "RGBA", right? | 11:09.03 |
| kens | AFAIK yes | 11:09.22 |
| sebras | I'm seeing that my 3 component + alpha pixmap is being rendered as CMYK. | 11:09.25 |
| | fz_fail() | 11:09.43 |
| kens | Umm, beyon me, sorry | 11:09.51 |
| sebras | maybe robin is awake? | 11:10.06 |
| Robin_Watts | I am | 11:10.18 |
| | sebras: n = 4, alpha = 1, colorspace = ? | 11:10.48 |
| sebras | Robin_Watts: n == 4, alpha == 1, colorspace->name == DeviceRGB | 11:12.16 |
| Robin_Watts | and where is the CMYK kicking in? | 11:12.33 |
| | In the saving of the pixmap I would hope. | 11:12.46 |
| sebras | Robin_Watts: when I let mupdf render the image. | 11:12.48 |
| | Robin_Watts: I'm not saving the output, just viewing it. | 11:13.01 |
| Robin_Watts | Where are you viewing it? In the MuPDF X11 app? | 11:13.15 |
| sebras | Robin_Watts: could it be n == 4 that is being interpreted as cmyk somewhere? | 11:13.17 |
| | Robin_Watts: yes. | 11:13.20 |
| Robin_Watts | It could be, but it would be a bug. | 11:13.33 |
| | (obviously). | 11:13.40 |
| juexing | Hello | 11:13.43 |
| 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. | 11:13.43 |
| sebras | Robin_Watts: I agree. | 11:13.44 |
| juexing | Is anybody there | 11:14.23 |
| Robin_Watts | juexing: Yes. Don't ask to ask, just ask. | 11:14.37 |
| sebras | Robin_Watts: do you know where the decision is taken how the pixmap should be rendered? | 11:14.58 |
| | Robin_Watts: shouldn't the output window always be RGB?! /me is confused. | 11:15.14 |
| Robin_Watts | Yes, I would have thought so. | 11:15.28 |
| juexing | Excuse me, mupdf can do PDF signature protection? | 11:16.20 |
| Robin_Watts | juexing: MuPDF can (with some limitations) check PDF signatures. | 11:16.47 |
| | creating PDF signatures might be a trickier question. | 11:17.14 |
| juexing | I see there is this method, is to import a PFX file, but do not know how to call? | 11:17.25 |
| Robin_Watts | Me either. | 11:17.40 |
| | The guy who would know will be around in about 24 hours if you ask again. | 11:17.58 |
| juexing | Really? That's really thank you. I'll ask again, I always want to know | 11:19.04 |
| sebras_ | Robin_Watts: sorry, dropped out. | 11:20.07 |
| | juexing: can I ask, what is your project where you use mupdf? | 11:20.54 |
| | juexing: it is always interesting for developers to know how mupdf is used. | 11:21.15 |
| Robin_Watts | sebras: If it was me, I'd put some breakpoints in, and try and black and white PDF. | 11:24.02 |
| juexing | The project has not been used in the mupdf, but see the source code to see when there is a PFX on the increase in signature protection function. But I can't call it all the while. | 11:24.30 |
| Robin_Watts | Then examine the output on the pdf_drop_device at the end of the draw phase. | 11:24.32 |
| | juexing: Sorry, I didn't understand that. | 11:25.03 |
| | You're saying your current project doesn't mupdf? | 11:25.13 |
| | But you might like to use MuPDF to add signature protection functionality? | 11:25.33 |
| juexing | sorry,my english is poor. | 11:26.06 |
| Robin_Watts | no worries! | 11:26.14 |
| juexing | yes, i might like to use MuPDF to add signature protection functionality?But i can not call this function | 11:27.05 |
| Robin_Watts | juexing: Right, so before you start work you should check that the license is OK. | 11:27.27 |
| | MuPDF is released under 2 different licenses. | 11:27.35 |
| | Firstly, it is released under the GNU AGPL. If you accept and comply with all the terms of the GNU AGPL then you can use it for free. | 11:28.36 |
| | This includes the fact that you have to license your entire app under the GNU AGPL. | 11:28.54 |
| | And give away the source code to anyone that asks for it. | 11:29.02 |
| | Many people are not prepared for that. | 11:29.14 |
| | If you can't abide by those terms, then we can sell you a commercial license. | 11:30.04 |
| | If you're not prepared to pay for a commercial license, then you can't use MuPDF. | 11:30.26 |
| juexing | Okay, I know. | 11:33.20 |
| | I have read the mupdf source code for PDF to add the PFX file function, is to do with pkcs7. | 11:33.21 |
| | I would like to ask how to add a PDF file for the PFX file, so as to achieve PDF file signature protection. | 11:33.21 |
| | In fact, I would like to ask is about the PDF digital signature protection technology issues | 11:33.57 |
| sebras_ | juexing: what license is your project released under? what is the name of the project? maybe I know of it! :) | 11:35.00 |
| juexing | No project is in use. | 11:36.22 |
| | I'm just asking about the technical problems in this area. | 11:36.22 |
| Robin_Watts | Then you'll need to come back at a later date and hope that the engineer responsible has time to talk to you. | 11:36.52 |
| | He is EXCEPTIONALLYU busy at the moment, so I suspect will be too busy to talk to someone who is not a customer. | 11:37.15 |
| Robin_Watts | runs | 11:37.30 |
| sebras_ | Robin_Watts: thanks for the idea to try b/w. I'll give it a shot. | 11:38.29 |
| juexing | No relationship. Then he can contact with him, but a technical problem does not understand to ask. | 11:38.55 |
| | Because I have been unable to use the function of PFX mupdf protection, may be a bug. | 11:40.27 |
| | Because I have been unable to use mupdf to protect the function of a PFX signature, may be a bug. | 11:41.17 |
| sebras_ | juexing: you will have to try again in 24h when the engineer is back. the people who are here now cannot help you because we also don't know the signature code. | 11:41.38 |
| | juexing: if you think it is a bug, you can always write a bug report at bugs.ghostscript.com. please attach an example file | 11:42.15 |
| | juexing: I also need to go now. | 11:42.52 |
| juexing | That's OK. Thank you very much! | 11:45.08 |
| | Forward 1 day (to 2016/07/04)>>> | |
IRC Logs