There is a potential NULL pointer usage if second attempt to allocate storage for user's groups fails. There is no check for calloc status.
Love how easy it is to setup and get running. Only thing is how hard would it be to add functionality to print to differnt folder locations based on different print queues?
Example would be someone needs to print to a community share for one queue and another group needs to print to another community share in landscape.
Hello guys, this is a GREAT project.
However I dare to ask for a truly minor feature, which I think would be very useful to a lot of people out there, and so easy to implement. As far as I can tell, cups-pdf writes PDF files using the name of the job/file/whatever... This is good BUT a problem arises when a file with that name already exists. Why not to add a suffix like (1), (2), (3), (4), ecc. in that case, so that one can print many different documents with the same name without bothering about older files being overwritten? There is a lot of crappy windows software that behaves like that, which would greatly benefit a simple feature like this. Regards.
Are there any plans to preserve the hyperlinks in a PDF such as when called to print an HTML page from a browser such as Firefox? I would ask for an option that could be turned on or off. In OpenOffice.org, the export to PDF does preserve the hyperlinks. Thank you.
An open, cross-platform journaling program.
A scientific plotting package.