So, suppose we don't ship Ghostscript ourselves, but instead have our software check its availability and, in case if it is absent, suggest how to obtain it short explanatory text and link to their download page. In case if it is installed, the program would use the Ghostscript API. To me it sounds legal, as Artifex says something like "you are not allowed to ship GS if your application doesn't meet so-and-so conditions". Would anybody care to share an opinion on this? IANAL, but as long as you do not distribute Ghostscript, you do not make any copies of the program or parts of it, and you do not build any "derived work" from it, Artifex has no legal foothold against you.
They obviously cannot charge you for designing your program in a way it can run an arbitrary command line utility with a configurable name and configurable parameters for PDF conversion. And I am pretty sure they cannot charge you for making the default configuration matching the signature of the current Ghostscript version.
Everything else happens by the user of the software - whatever conversion utility he installs is up to him - it is his responsibility, not yours, to use only legally obtained software for this task. And downloading, installing and just using the current Ghostscript version is perfectly legal, it is explictly allowed, encouraged and free of charge by the distributor.
So in short, what you have in mind IMHO obeys the license conditions of the current Ghostscript version. It sounds to me like you are just choosing to 'integrate' your product with Ghostscript, giving people the choice to use it or not. It's up to them to legally obtain a copy of Ghostscript. We do that with many products including a PDF printer similar to Ghostscript the one we use has to be paid for if our customers want to use it. We tell our customers that we integrate with it and it's up to them to buy it.
The company who sell it can't really complain, if anything we are promoting their product by encoraging our users to buy theirs as well. It's very similar with Ghostscript, all you are doing is integrating with it and promoting it, it's up to the customer to download it, and it's up to Ghostscript to decide if they are licensed to do that for free or to pay for it.
Many products integrate with many other products all the time and as long as they are not shipping those third-party products to their customers, they don't have to worry about licencing. As a bigger example We don't have to worry about the licensing of that even though our application is only designed to work with MSSQL and doesn't work without it. The main thing is probably making sure it's clear to your customers, before they buy your product, which features rely on software you don't provide.
Otherwise your customer could have a case against you if they think you supply everything they need. Sign up to join this community. Whether we add this capability will be largely dependent on community demand for the feature. See Enabling OCR for more details. For a list of open issues, or to report problems, please visit bugs. Incompatible changes Included below are incompatible changes from recent releases the specific release in question listed in parentheses.
We include these, for now, as we are aware that not everyone upgrades with every release. This will affect developers and maintainers of Ghostscript devices. Firstly, and most importantly, the way device-specific "procs" are specified has been rewritten to make it we think!
It is possible, but not guaranteed that a GSView update might be forthcoming to resolve this. Hence, as part of improving security we limited access to these operators, originally using the -dSAFER feature. Firstly, as mentioned in the 9. This is a change in behaviour compared to the old code which, on Windows, was case in sensitive.
For a list of open issues, or to report problems, please visit bugs. Incompatible changes Included below are incompatible changes from recent releases the specific release in question listed in parentheses.
We include these, for now, as we are aware that not everyone upgrades with every release. As a result Microsoft Windows XP and earlier are no longer supported by these binaries. This does not imply we are or will start relying upon features only available in VS, so the nmake Makefiles will continue to allow older Visual Studio versions back to VS to build Ghostscript.
Hence, as part of improving security, we limited access to these operators, originally using the -dSAFER feature. Firstly, as mentioned in the 9. This is a change in behaviour compared to the old code which, on Windows, was case in sensitive.
This is in recognition of changes in Windows behaviour, in that it now supports although does not enforce case sensitivity.
0コメント