Re: Problem with stdout

Ken Sharp <[email protected]> Wed, 28 Mar 2018 15:50:38 +0100
Newsgroups gmane.comp.printing.ghostscript.devel
Message-ID <[email protected]>
Hello Kevin,

At 10:30 28/03/2018 +0000, Kevin Schmitz wrote:

>I hope that I am on the right mailing list, as otherwise I have not found 
>a suitable "channel" to solve my problem.

Yes here is fine, you can also catch us on the #ghostscript IRC channel on 
freenode.net. There's usually someone around but we mainly work business 
hours Monday to Friday and we're based in different time zones, so there 
can be times when nobody is around.

The IRC channel is logged and the developers read the logs, so you can 
always leave a question and check back later (the logs are public so you 
can see if someone replied)

If someone is online and awake you'll get a more immediate response there.


>I am writing an application in C++(Visual Studio 2017) for Windows 10 with 
>Ghostscript *.23 and I am not able to write an output in stdout.
>
>
>
>But if I choose""-sOutputFile=myfile.jpeg" instead of 
>"-sOutputFile=%stdout", then everything works fine. I also used the 
>following variants:

You haven't said which device you are using, I'm inferring its one of the 
JPEG devices based simply on the output filename.

I need to dig into the device code a little, but at an initial fist glance 
it looks like the device simply doesn't support writing to stdout. Since, 
unlike the TIFF devices, I don't think the JPEG devices need to be able to 
seek through the output file and modify it, there's probably no reason why 
it shouldn't support output to stdout, but I will need to run through the 
code a bit to find out.

So this is a 'holding' email just to let you know its been received and I 
(or someone) will look at it.

In passing, I notice you are working for a commercial company and I'd ask 
you to quickly peruse the licence (which you should have received with your 
copy of Ghostscript) just to assure yourselves that your proposed usage 
conforms to the provisions of the AGPL. We'd hate to waste your time 
working on this if the open source licence isn't going to be suitable for 
you and you don't want to pursue a commercial licence.


                 Regards,


                     Ken Sharp