| | <<<Back 1 day (to 2014/08/04) | 2014/08/05 |
| mvrhel_laptop | robin_watts_mac: I heard an interview with the guy who wrote "The Martian" a while ago | 14:09.24 |
| | it sounded like an interesting book | 14:09.31 |
| | apparently the guy who wrote it worked hard to make it based in reality | 14:09.49 |
| | i.e. he had no "special" things to help him survive. everything was plausible | 14:10.13 |
| mlen | rayjj: took me some time, but finally I submitted the patch :) (This message has been postponed on 2014-08-04 23:08:07.) | 14:25.08 |
| kens | mlen I commented on it last night, I was planning to discuss it with the rest of ther staff at the meeting today | 14:25.38 |
| rayjj | mlen: yes, I saw it. I haven't seen kens comments yet (still perusing email) | 14:27.01 |
| henrys | which bug is that? shall we start the meeting with it? | 14:27.50 |
| kens | Its an enhancement to tiffsep | 14:28.03 |
| | one minute and I'll get the number | 14:28.13 |
| rayjj | mlen: my initial look prompted me to ask "How invested are you in the format of the output?" | 14:28.16 |
| | henrys: actually, I don't think it should take time from all of us. | 14:28.38 |
| kens | bug 695407 | 14:28.39 |
| | rayjj do we have much else to discuss otday ? :-) | 14:28.59 |
| chrisl | Surely, we want it to give the actual tint transform output? | 14:29.07 |
| kens | chrisl what if its not a CMYK alternate ? | 14:29.25 |
| henrys | if kens wanted to discuss I assume it appropritate for the meeting | 14:29.29 |
| kens | I think mlen specifically wants CMYK I htink | 14:29.36 |
| rayjj | kens: that quartet of CMYK does represent the tint transform | 14:29.47 |
| chrisl | kens: that's what I mean - I'd expect the alternate space values, not forced to CMYK | 14:30.06 |
| kens | rayjj can't possibly be the result of hte tint transform if hte alternate is (eg) /DeviceRGB | 14:30.07 |
| | I'm not even sure its the result of the tint transform if the space is CMYK, does Little CMS have any effect here ? | 14:30.58 |
| rayjj | kens: ahh. I see. Well, it i_is_ the CMYK "spot equivalent color", which is what we put in the psdcmyk | 14:31.00 |
| mvrhel_laptop | morning | 14:31.07 |
| rayjj | mvrhel_laptop: just in time to answer the color question from kens | 14:31.33 |
| kens | mvrhel_laptop : will almost certainly have to scan the patch first | 14:31.53 |
| henrys | we are here http://bugs.ghostscript.com/show_bug.cgi?id=695407 | 14:32.13 |
| rayjj | I don't recall if the DeviceN logic that captures the spot equivalent colors is before or after the input colorspace for the tint transform has been munged by lcms (or whatever is the CMS). | 14:32.59 |
| kens | Without being able to raise a specific objection, I'm uneasy about the patch on 2 fronts, as I mentioned in the thread. I'm not at all certain what the CMYK values are here, and while I understand that mlen wants these for his purposes, I'm concerned people will use them thinking they are the real spot values. | 14:33.07 |
| mvrhel_laptop | rayjj: that reminds me | 14:33.09 |
| rayjj | it's easy enough to test. See if the colors change with -dUseFastColor :-) | 14:33.30 |
| kens | I'm also a little worried about sticking random stuff in a TIFF file which isn't referenced by an entry in the IFD | 14:33.34 |
| mvrhel_laptop | were you going to deal with the question about NONE colorants from the customer | 14:33.50 |
| | looking up customer id number... | 14:34.00 |
| chrisl | I thought TIFF allowed for "custom" tags | 14:34.03 |
| rayjj | kens: I haven't looked, but, I agree that putting it in the TIFF is not a good idea | 14:34.14 |
| kens | chrisl I don't think it is writen with a tag..... | 14:34.15 |
| | As far as I can see its just stuffed into the TIFF file, I could be wrong | 14:34.30 |
| mvrhel_laptop | rayjj #885 | 14:34.42 |
| rayjj | in the myriad of tags, there probably already is one | 14:34.44 |
| kens | Let me look again at the tiff 6 spec | 14:34.58 |
| chrisl | kens: I thought there was something like a comment tag | 14:34.58 |
| rayjj | kens: the TIFF 6 spec is pretty worthless. You need the reference of all the other tags | 14:35.28 |
| kens | rayjj there is no specification beyond 6 | 14:35.39 |
| | Just a couple of tech notes which were never formally adopted and a bunch of tech notes for specific applications | 14:36.03 |
| | There's an ImageDescription tag | 14:36.22 |
| henrys | marcosw: anything for the meeting and when does your vacation start? | 14:36.25 |
| mvrhel_laptop | ok. I am trying to get up to speed on this | 14:36.42 |
| marcosw_ | i'm leaving tomorrow morning at 6:00 and don't have anything for the meeting | 14:36.57 |
| kens | Oh oh, the support list goes bonkers again tomorrow then :-( | 14:37.27 |
| henrys | rayjj and others: also I wanted to bring up the tmp file business. That seems to have momentum letâs finish it up. | 14:37.46 |
| kens | The ImageDescription tag looks the most appropriate to me, its basically a comment | 14:38.15 |
| henrys | kens: marcosw releases announcements to customer that they may now report bugs. | 14:38.20 |
| | ;-) | 14:38.28 |
| kens | would not be surprised...... | 14:38.32 |
| henrys | chrisl: so directory restructuring: too late for this next release I think, but are you still stuck with windows makefiles? | 14:39.20 |
| chrisl | henrys: no, I've made some progress, but I keep being distracted by other issues | 14:39.51 |
| marcosw_ | henrys is the one who mentioned it here :-) | 14:40.12 |
| kens | will simply ignore support@ and let henrys field them all :-) | 14:40.37 |
| mvrhel_laptop | kens and rayjj: I don't see where this is getting stuff in a TIFF tag? | 14:41.14 |
| henrys | hah | 14:41.14 |
| mvrhel_laptop | it is just printing out to the console yes? | 14:41.28 |
| kens | mvrhel_laptop : it isn't, there are 2 discussions. | 14:41.31 |
| henrys | I hope the patient ones come by | 14:41.32 |
| mvrhel_laptop | hehe. sorry | 14:41.39 |
| kens | mvrhel_laptop : Does it ? I thought it stuffed it into the TIFF file | 14:41.43 |
| | It was late last night, let me look at it again | 14:42.00 |
| henrys | tor8, paulgardiner mupdf business for the meeting? | 14:42.30 |
| chrisl | Private tags don't work the way I thought they did - using them would be a bad idea :-( | 14:42.33 |
| kens | mvrhel_laptop : Ah yes, I see you are right, its using dmprintf, so its going to stdout. At least, it is when the build is a debug build, I have a sneaky suspicion that does nothing in a release build. Maybe someone else can remember | 14:43.13 |
| paulgardiner | henrys: I've done nothing on MuPDF this week. | 14:43.14 |
| chrisl | dmprintf should be debug only | 14:43.37 |
| kens | dmlprintf, but I assume its the same | 14:43.47 |
| henrys | also I wanted to check my memory about the agenda - I noted I was going to check with Till about deprecating X11 but I canât remember if we decided to abort that goal for some reason. chrisl do you remember I would have discussed it with you. | 14:44.01 |
| kens | So it won't do anything on a release build, which doesn't seem right | 14:44.05 |
| tor8 | henrys: no news. | 14:44.09 |
| chrisl | henrys: I don't think we reached a conclusion - we really don't have time to work on an alternative for the foreseeable future | 14:44.59 |
| kens | mvrhel_laptop : So the 2nd part of the query is, where the cmyk_map[sep_num].c/m/y/k values come from, in particular if these are affecxted by little CMS | 14:45.10 |
| henrys | tor8: We donât have an extra resource anymore for mupdf (fyi) | 14:45.20 |
| | chrisl: the deal was install gtk or no viewer. I so want to get rid of X11 but I realize that is rather draconian | 14:45.58 |
| rayjj | kens: using the InkSet+InkNames+NumberOfInks would let the separation contain the Ink name comment _and_ the CMYK (there is no spec for the InkName istself) | 14:46.06 |
| mvrhel_laptop | kens: from a color standpoint I don't have any issues with this. It is only giving the equivalent cmyk values as far as the alternate color space mapping defines it. no CM. This is an area where the user is going to have to be careful | 14:46.08 |
| tor8 | henrys: no more matt? okay. | 14:46.26 |
| mattchz | tor8: iâm on SOT now | 14:46.37 |
| kens | mvrhel_laptop : so where do these come from if the alternate space mapping was to (eg) RGB rahter than CMYK ? | 14:46.42 |
| tor8 | mattchz: my sympathies :) | 14:46.44 |
| rayjj | mvrhel_laptop: if the alternate is NOT CMYK, how does it get CMYK from, say, RGB ? | 14:46.47 |
| mattchz | tor8: thanks :-D | 14:46.51 |
| chrisl | henrys: yes, but the gtk front end isn't ready for "prime time" - it needs a fair amount of work before we could make it the default. Work we don't have time to do | 14:46.53 |
| henrys | mattchz is on to browner pastures ;-) | 14:47.05 |
| mattchz | lol | 14:47.12 |
| | iâve not stabbed myself violently yet, so I guess thatâs a good sign | 14:47.25 |
| rayjj | mvrhel_laptop: and if the alternate _is_ CMYK, does the input CMYK go through any CMS mapping (using the output profile mapping to CMYK) ? | 14:47.46 |
| | mvrhel_laptop: I can check that and define it. | 14:48.26 |
| mvrhel_laptop | rayjj and kens: so there should not be any CM in applying the alternate tint transform | 14:48.33 |
| kens | rayjj I'm inclined to think that maybe we should avoid the tags, since mlen is happy to have this on stdout. Perhaps we should simply control the emission of the equivalents on stdout with a device parameter ? | 14:48.34 |
| rayjj | kens: I recommend we hash this out in bug coments | 14:48.39 |
| mvrhel_laptop | that mapping is defined using the "dumb" color transforms | 14:48.43 |
| kens | Aha, so its PostScript default transforms. OK | 14:49.01 |
| mvrhel_laptop | however, | 14:49.05 |
| henrys | tor8: and I suspect robin_watts_mac will be at capacity when he returns. If you can cultivate a bounty community for the interactive stuff that would be worthwhile, I expect it is a lot easy to recruit for that then core pdf. | 14:49.15 |
| kens | rayjj That leads ot lengthy bug threads :-( | 14:49.16 |
| mvrhel_laptop | if the alternate tint transform is RGB, I suspect we may use CM to get to CMYK | 14:49.25 |
| | I need to check that | 14:49.29 |
| henrys | tor8: just make stuff bountiable or send me a list of potentials and Iâll do it. | 14:49.49 |
| kens | mvrhel_laptop : I suspect its not important to mlen, but I'd like to be able to comment the code so that we know where the CMYK is coming from, sooner or later someone will ask | 14:50.06 |
| mvrhel_laptop | right. let me check now | 14:50.18 |
| rayjj | kens: I agree about having a parameter to enable the extra (or althernate format) output is reasonable in case we have somebody relying on the current format. We _do_ have customers using tiffsep, iirc | 14:50.29 |
| henrys | chrisl: okay Iâm moving the X11 stuff to the someday blackhole on the agenda | 14:50.41 |
| tor8 | henrys: okay. I'm working on a new desktop viewer that should have feature parity with the android/ios apps so a lot of these interactive features can be easier to work on | 14:51.01 |
| chrisl | henrys: we'll get to it when SmartOffice is finished...... | 14:51.03 |
| kens | rayjj mlen's patch doesn't write to the TIFF, I misunderstood what he was doing, it writes to stdout. But only if its a debug build, which is probably not helpful | 14:51.13 |
| henrys | the only other thing I have is to ask michael to do a release of gsview with -dNOCACHE so I can look at printer output. | 14:51.21 |
| mvrhel_laptop | oh henrys: I will do that today | 14:51.36 |
| paulgardiner | tor8: what framework? | 14:51.37 |
| tor8 | paulgardiner: none :) | 14:51.48 |
| kens | rayjj so I'm happy enough with teh stdout output, though I'd suggest a parameter to enable it, so that people who use tiffsep aren't surprised by the extra output. | 14:52.04 |
| | and obviously move it from a debug print to a regular outptu print.... | 14:52.24 |
| henrys | mvrhel_laptop: I can capture the results over TCP-IP with wireshark so I can see exactly what windows is doing to the xps. | 14:52.26 |
| paulgardiner | tor8: how is that possible? :-S | 14:52.51 |
| mvrhel_laptop | oh henrys: did we have any pcl performance numbers on the raspberry pi? | 14:52.52 |
| tor8 | paulgardiner: I don't expect to need more than buttons, scroll bars and text input and it's easier to just do those than mess with heavy weight cross platform GUI toolkits | 14:52.53 |
| rayjj | kens: agreed to the first, but I would leave the output the same as previously (if it's on stderr, leave it there, since customers may be capturing stderr) | 14:53.10 |
| tor8 | paulgardiner: my "none" was tongue in cheek ... I'm using FreeGLUT to get an opengl window and basic input | 14:53.24 |
| henrys | mvrhel_laptop: I thought rayjj produced numbers for all the languages. | 14:53.36 |
| kens | rayjj dmprintf goes to stderr not stdoput ? | 14:53.37 |
| paulgardiner | Ah right. I see | 14:53.39 |
| tor8 | paulgardiner: opengl has the fastest possible pixmap-to-screen path in linux | 14:54.04 |
| rayjj | henrys: (all) I have the toolchain for the company C board sorted out and have built their "example" -- going to try downloading it to the board this AM | 14:54.24 |
| mvrhel_laptop | henrys: and rayjj: do you recall doing some PCL timings? | 14:54.30 |
| kens | rayjj building is progress :-) | 14:54.43 |
| henrys | mvrhel_laptop: Iâll search my email too, I remember we had bad numbers but numbers nonetheless | 14:55.24 |
| rayjj | mvrhel_laptop: I don't have any PCL numbers for the Pi. I could do some (instead of the C board work) | 14:55.36 |
| | and if someone tells me what files we should run | 14:55.58 |
| mvrhel_laptop | rayjj: that is where we need henrys | 14:56.08 |
| | what would be some good pcl files to test henrys? | 14:56.16 |
| henrys | rayjj: what did you run for ps and pdf? | 14:56.19 |
| mvrhel_laptop | we have ps and pdf | 14:56.25 |
| | that I had been showing in japan | 14:56.30 |
| | company M asked about PCL | 14:56.48 |
| kens | rayjj dmprintf goes to stdout and emprintf goes to stderr. As far as I can see dmprintf is enabled for release builds as well as debug builds. | 14:56.53 |
| rayjj | was that me or Robin that ran PS and PDF on the Pi? I don't recall doing it | 14:57.10 |
| mvrhel_laptop | I did it | 14:57.19 |
| rayjj | mvrhel_laptop: oh, thanks. I'm glad my memory isn't failing that badly :-) | 14:57.40 |
| henrys | do you need jeitta pcl files I can prepare the pcl from the applications . | 14:57.44 |
| | ? | 14:57.46 |
| mvrhel_laptop | rayjj: you helped me compare adobe cpsi with gs on a desktop machine | 14:57.50 |
| rayjj | mvrhel_laptop: right -- that I _can_ do | 14:58.06 |
| henrys | mvrhel_laptop: so you have the pi? | 14:58.14 |
| mvrhel_laptop | henrys: if you can make jeitta files reasonably sized. I recall we had issues with creating good pcl to test with | 14:58.35 |
| | henrys: I do have a pi | 14:58.41 |
| | have not touched it in about a year though... | 14:58.51 |
| rayjj | the problem with PCL files is that the ones from most drivers are bad perfromance wise (at least for us). | 14:59.08 |
| mvrhel_laptop | yes that was the issue we were having | 14:59.21 |
| | I almost think a text file is best to show | 14:59.38 |
| henrys | mvrhel_laptop: I can make them but they are slow. The output of the typical modern PCL driver doesnât do well with color wise. We are great mono | 14:59.42 |
| rayjj | For many we are better off with PXL files created by GS | 14:59.43 |
| mvrhel_laptop | at this stage | 14:59.45 |
| rayjj | the JEITA files have lots of non-text, iirc | 15:00.11 |
| henrys | rayjj: that I would doubt - PXL output from a driver is going to be much better than GS output. | 15:00.20 |
| mvrhel_laptop | lets do the first 100 pages of the PLRM or something like that | 15:00.27 |
| rayjj | henrys: if we convert PS to PXL, at least it won't have any ROPs | 15:00.56 |
| mvrhel_laptop | that gives them something that we all know . and should have good numbers | 15:01.03 |
| rayjj | the driver output seems to really abuse ROPS | 15:01.13 |
| henrys | rayjj: yeah but no fonts ugh | 15:01.14 |
| rayjj | henrys: if it's only the JEITA files, then trying both methods to produce the PCL is reasonable -- see which runs better into our pcl6 | 15:02.50 |
| henrys | okay well Iâll post jeitta pcl files from a recent Windows driver on casper. | 15:04.17 |
| chrisl | henrys: what about producing PCL on a Mac? | 15:04.47 |
| rayjj | mvrhel_laptop: can you send the PS and PDF numbers (and file names, and gs version, etc) that you collected ? (or just tell me the Subject if you already did) | 15:04.53 |
| mvrhel_laptop | rayjj: yes will do that now | 15:05.22 |
| | thanks! | 15:05.24 |
| rayjj | mvrhel_laptop: thanks. | 15:05.31 |
| | mvrhel_laptop: so do you want me to dust off my Pi and do the PCL timings, or do you have time to do it ? | 15:05.52 |
| mvrhel_laptop | rayjj: if you could do it for me, I would greatly appreciate it | 15:06.08 |
| henrys | chrisl: interesting question. I wonder if it is even possible to produce high level pcl on the mac, I thought it would convert postscript/pdf to PCL raster for a pcl device. | 15:06.20 |
| rayjj | henrys: OK with you ? It shouldn't take me off the C board for long. | 15:06.38 |
| henrys | using something cupsish | 15:06.39 |
| | rayjj: fine by me. | 15:07.05 |
| chrisl | henrys: yes, but Apple have a lot of customisations in cups, and don't use Ghostscript - so they might have fonts in the output, and not abuse rops | 15:07.20 |
| rayjj | henrys: well, you have a mac and know how to look at PCL :-) | 15:07.23 |
| henrys | rayjj: yes Iâll have a look | 15:07.47 |
| rayjj | henrys: were you going to make the PCL test files and put them on casper ? | 15:08.43 |
| mvrhel_laptop | rayjj: ok I sent you the file | 15:11.18 |
| | rayjj and kens: so gs does do color management to map from the alternate tint transform color space to the device output profile (which is CMYK) | 15:11.58 |
| | this occurs only for the spot colors | 15:12.16 |
| | i.e. device N and sep | 15:12.27 |
| kens | mvrhel_laptop : thanks I'll add that to the bug thread | 15:12.30 |
| | DFumb question, doe that happenfor a CMYK alternate too ? | 15:12.57 |
| mvrhel_laptop | interestingly kens. if the output profile is a DeviceN ICC profile, it uses the default CMYK profile since we dont want to map to DeviceN output. There is a comment in the code about this and for the user to beware. | 15:13.28 |
| kens | I'm assuming not | 15:13.29 |
| mvrhel_laptop | kens: yes it is used | 15:13.34 |
| kens | Oh, OK so I was wrong again :-) | 15:13.41 |
| mvrhel_laptop | kens: the alternate color space is going to be ICC based. It could be defined in the file, or it could be the default CMYK space | 15:14.41 |
| rayjj | mvrhel_laptop: if it uses the default CMYK profile, then CMYK in _probably_ gets recognized and takes the is_identitiy path (no transform) | 15:14.42 |
| mvrhel_laptop | rayjj: if both are the default then no mapping occurs | 15:14.59 |
| | since they match | 15:15.04 |
| | you could have a alternate color space that was ICC base (and CMYK) | 15:15.29 |
| rayjj | mvrhel_laptop: oh, that's right. Someone _could_ have used a different CMYK colorspace profile | 15:15.31 |
| mvrhel_laptop | rayjj: right and also as I said the alternate color space can be ICC based | 15:15.49 |
| | but CMYK based | 15:15.56 |
| | does that make sense | 15:16.03 |
| | i.e a CMYK ICC color space | 15:16.15 |
| | or an ICC color space with a profile that is CMYK | 15:16.25 |
| | that is how I should word that | 15:16.30 |
| kens | So if the alternate is /DeviceCMYK then no transform takes place. If the alternate is a ICCBased space wheren N=4 then some management will take place | 15:17.14 |
| mvrhel_laptop | kens: in case 1. if someone is using the default ICC profile as their output profile, no transform takes place. | 15:17.53 |
| | if they use something special, a transform will take place | 15:18.06 |
| kens | Well, I hope someone using something spacial will expect that :-) | 15:18.23 |
| mvrhel_laptop | yes | 15:18.27 |
| mlen | kens: +1 for the idea for device parameter :) I didn't have time to implement it that way | 15:18.33 |
| rayjj | mvrhel_laptop: oh, so it doesn't use the default CMYK profile, it uses whatever the device profile is ? | 15:18.40 |
| mvrhel_laptop | rayjj: what do you mean by "it" | 15:18.55 |
| | there are 2 profiles. the source and the destination | 15:19.17 |
| rayjj | mvrhel_laptop: sorry, the determination of the spot equivalent CMYK | 15:19.28 |
| mlen | kens: also I didn't find a useful function to write to stdout regardless of whether it was debug build or not | 15:19.40 |
| mvrhel_laptop | if the alternate tint transform is CMYK, then we use a source profile that is our defaultCMYK | 15:19.49 |
| rayjj | the question was is the destination profile used for getting the spot CMYK, the device profile or the default CMYK profile ? | 15:20.05 |
| mvrhel_laptop | we will always use the destination profile for the device as the output profile that we map to | 15:20.12 |
| kens | mlen, its OK dmprintf writes to stdout (I htin), and its not controlled by debug/release, I checked that | 15:20.13 |
| mvrhel_laptop | rayjj: it is the device profile | 15:20.23 |
| | except in the case where the device profile is a deviceN profile | 15:20.33 |
| | then we use the default CMYK profile | 15:20.41 |
| | that is an odd case though | 15:20.49 |
| rayjj | mvrhel_laptop: but if the device profile is not a CMYK profile ??? | 15:20.52 |
| mvrhel_laptop | rayjj: it has to be for tiffsep | 15:21.00 |
| kens | :-) | 15:21.09 |
| mvrhel_laptop | it has to be CMYK or DeviceN | 15:21.16 |
| rayjj | mvrhel_laptop: OK. | 15:21.17 |
| mvrhel_laptop | if you pick RGB as your device profile for tiffsep weird things will happen | 15:21.56 |
| kens | mlen do we have a Contributors Licence Agreement from you ? | 15:22.08 |
| rayjj | mvrhel_laptop: not surprised at that. | 15:22.23 |
| mvrhel_laptop | rayjj: did you get my email? | 15:22.33 |
| | and thanks again rayjj | 15:22.41 |
| | oh one more question for kens, rayjj, chrisl and everyone else | 15:23.20 |
| kens | ?? | 15:23.25 |
| mvrhel_laptop | I have to put some slides together for the linux open print summit | 15:23.34 |
| | I know I will talk about the color fixes that kens did to PDF write | 15:23.58 |
| kens | Oh oh..... | 15:24.07 |
| mvrhel_laptop | are there other things that we want mentioned | 15:24.12 |
| chrisl | I can't really think of anything | 15:24.46 |
| mvrhel_laptop | ok. well if anything comes to mind later, shoot me an email please | 15:25.19 |
| kens | I think that's all I've done that's new | 15:25.23 |
| chrisl | possibly mention that pswrite and co are dead, and ps2write is now the sole focus for Postscript output? | 15:25.54 |
| rayjj | mvrhel_laptop: what version of GS did you use for your timings (it doesn't say) | 15:26.04 |
| mvrhel_laptop | chrisl: yes that is a good idea | 15:26.07 |
| kens | chrisl I'm hoping nobody will notice :-) | 15:26.13 |
| mvrhel_laptop | rayjj: good question. | 15:26.18 |
| | these were done 1 year ago | 15:26.32 |
| | so what ever the august release was | 15:26.43 |
| | would be close | 15:26.52 |
| rayjj | mvrhel_laptop: and did you try PS files from the Windows PS driver, or just the ones post converted from the PDF using ps2write ? | 15:27.06 |
| mvrhel_laptop | rayjj: all the files were created using gs | 15:27.32 |
| rayjj | mvrhel_laptop: that's what I was guessing for the version. If I have time, I'll retest with head. | 15:27.38 |
| mvrhel_laptop | rayjj: that would be great | 15:27.49 |
| chrisl | mvrhel_laptop: possibly worth mentioning the saved-page functionality, also? | 15:27.55 |
| rayjj | mvrhel_laptop: you said "J*.pdf PDF files generated from JEITA files with application and Acrobat print driver" | 15:28.10 |
| mvrhel_laptop | chrisl: can you send me a small right up about that. I am not sure I know exactly what all the does... | 15:28.25 |
| | write-up | 15:28.29 |
| chrisl | mvrhel_laptop: I only know what rayjj told me to put in the News.htm file..... | 15:28.48 |
| | http://www.ghostscript.com/doc/9.14/News.htm | 15:29.04 |
| mvrhel_laptop | oh yes. thanks | 15:29.13 |
| | I will go over this | 15:29.22 |
| | thanks chrisl | 15:29.26 |
| rayjj | saved page is useful (if the printer has a disk) for re-ordering pages | 15:29.33 |
| mvrhel_laptop | oh the clist transparency stuff you did too rayjj | 15:29.52 |
| rayjj | it requires clist, but the clist files can be played back in arbitrary order | 15:29.55 |
| chrisl | mvrhel_laptop: The other one that might be worth mentioning is PSDocOptions and PSPageOptions - those have possible relevance for CUPS | 15:30.30 |
| rayjj | mvrhel_laptop: saved_pages can also provide for collated copies | 15:30.40 |
| mvrhel_laptop | ok. thanks | 15:31.24 |
| kens | I'd forgotten those options..... Probably worth mentioning those yes, it makes the PS otput configurable for specific device settings | 15:31.54 |
| rayjj | digs out his Pi ... | 15:32.37 |
| | mvrhel_laptop: do you have the PS and PDF files you ran laying around on casper or somewhere? | 15:33.27 |
| | have to run ome and get the Pi p/s ... | 15:40.31 |
| | mvrhel_laptop: if you locate the PS and PDF files, mention it here (I'll check the logs) or email. | 15:41.11 |
| mvrhel_laptop | rayjj: let me look | 15:42.04 |
| rayjj | henrys: same for you with the PCL files. If you can do the PLRM as well, that's the other one mvrhel_laptop timed | 15:42.34 |
| | henrys: mvrhel_laptop had timings for J9, J11, J12 and the first 100 pages of the PLRM | 15:43.43 |
| henrys | rayjj: I am capturing the output over TCP-IP so PLRM is a problem. Do you know how to print to a file in windows 8? It seems that feature was lost at some point in windows history. | 15:44.32 |
| rayjj | henrys: if you tell me what PCL driver to use, I can print to a file using Windows 7. It usually is an option in the print dialog, but you can also (under 7) install the printer to print to the FILE: port | 15:46.02 |
| | henrys: I don't know if 8 lets you do that | 15:46.13 |
| | henrys: if the port is FILE: then when it prints, it pops up the dialog asking where to save the output | 15:46.44 |
| | bbiaw. | 15:47.11 |
| kens2 | henrys if you create a printer then you can send it to FILE: | 15:52.52 |
| | As usual with Windows 89, nothing is easy..... | 15:53.04 |
| | open the charms bar by hovering the mous in the top right corner | 15:53.18 |
| | THen choose settings | 15:53.43 |
| | Control Panel | 15:53.48 |
| | View devices and pritners | 15:54.00 |
| | Right click the printer | 15:54.07 |
| | select printer properties | 15:54.16 |
| | Then the 'Ports' tab | 15:54.22 |
| | Pick the FILE: check box | 15:54.35 |
| henrys | okay so I have to create a new driver - I have one setup and there is nothing in the printer properties | 15:57.24 |
| kens2 | Did you right click the printer and selcect 'printer properties' from teh drop down list ? Not 'Properties' but 'Printer properties' | 15:59.08 |
| robin_watts_mac | moves to Santiago/Valparaiso. Back later. | 15:59.23 |
| kens2 | launches Windows 8 VM again | 16:00.19 |
| henrys | kens2: ahahâ¦. thank you much | 16:00.29 |
| kens2 | Ah No problem. | 16:00.36 |
| | Personally I find it incredibly annoying trying to find this stuff in Windows 8...... | 16:00.58 |
| henrys | kens2: the thing I notice most is the lack of ânetâ support. If you have a question about linux there are usually a handful of quality answers you can get with a quick google. | 16:29.21 |
| kens2 | Its hte way MS seem to be trying hard to hide stuff desktop users actually need that bugs me...... | 16:29.57 |
| henrys | kens2: and itâs gotten worse with the trajectory toward a mobile interface | 16:30.36 |
| kens2 | Yes, that seems to be the driver here, MS have forgotten that the vast majority of WIndows users don't have a touch screen. :-( | 16:31.09 |
| henrys | kens2: but once switched to file the âprinter properiesâ option goes away. How to switch it back ⦠hmm | 16:36.40 |
| kens2 | Mine still has a printer proerties in the right click context menu, even when its set to FILE | 16:37.11 |
| henrys | kens2: hmph let me start again with a new driver | 16:41.32 |
| kens2 | Windows 8, gotta love it.... | 16:41.44 |
| | Of course, I'm using 8.0, 8.1 might be different if you are using that | 16:41.59 |
| henrys | no Iâm in 8.0 I am using the latest HP driver which may be the source of the problem | 16:43.11 |
| kens2 | Umm, mine was an HP driver, I think, might not be the absolute latest one though | 16:43.47 |
| rayjj | henrys: why is capturing PLRM pages 1-100 using TCP/IP a problem? too big ? Note you can set the page range to print in the print dialog | 17:25.12 |
| henrys | rayjj: the file to print worked Iâll have the files after lunch | 17:34.42 |
| | rayjj: when I do the tcp capture it goes to the printer so no I donât want to print out 100 pages I donât think it would be a problem to capture it though. | 17:40.07 |
| rayjj | henrys: Oh, I ddn't understand that you actually snooped the stream to the printer | 17:42.52 |
| | unless the printer spools the stream to disk, in which case you can just take the paper tray out and let the stream collect :-) | 17:43.42 |
| | bbiab. Need more coffee. | 17:43.56 |
| henrys | rayjj: yes I feel more comfortable Iâm getting accurate results for example if I print to a file I donât know if some back and forth communication has taken place that might change the printer stream. | 17:44.25 |
| rayjj | OK, I have my Pi up in the net and can ssh into it :-) Got autoocnf installed and am getting ready to build pcl6 -- whew!! | 20:08.29 |
| | and still building... (on a disowned job, so I don't have to stick around) | 20:19.49 |
| | 35 minutes elapsed ... | 20:47.50 |
| | I took the lid off to let the heatsinks "breathe" | 20:48.36 |
| mvrhel_laptop | rayjj: great | 21:10.41 |
| henrys | rayjj: I found a new hp driver and Iâm going to see if it has better output. | 22:07.08 |
| rayjj | henrys: OK, let me know. | 22:38.44 |
| | I've built the pcl6 and am building gs | 22:38.59 |
| | it took 40 min to buld pcl6 :-/ | 22:39.32 |
| henrys | pcl is much faster to build than pdf no? | 22:40.13 |
| | ps and pdf | 22:40.23 |
| rayjj | henrys: I'll let you know in an hour or so | 22:40.45 |
| henrys | ;-( | 22:40.58 |
| rayjj | henrys: that's OK. I just (optimistically) tell myself that it's taking that long because it's optimizing ;-) | 22:42.49 |
| henrys | I wonder if we should build with 32 bit color index. Probably not what you want to hear. | 22:43.29 |
| rayjj | henrys: I'll collect the timings from these builds, then re-build and try again. | 22:44.24 |
| | henrys: did you tell me where the PCL files are (or are you still deciding what ones are best) | 22:44.54 |
| | ? | 22:44.59 |
| henrys | optimizing ;-) | 22:45.19 |
| rayjj | it's cool being able to access the Pi as a server :-) At least I don't have to sit in my (rather noisy) office where all the other servers are | 22:56.09 |
| | henrys: is it you or kens handling the reply about Unicode filenames from Sriram ? (they seem to be back at 9.07, so it probably didn't have default support for Unicode on Windoze) | 23:06.27 |
| henrys | I saw that and hoped marcosw would field that one before he left. | 23:07.34 |
| | rayjj: Iâll respond | 23:08.08 |
| | Forward 1 day (to 2014/08/06)>>> | |
IRC Logs