Filename error if no extention

Hi,

Our business software sends the printjob to the queue without an extention. I can't change this.

I've discovered that the PDF-document name is incorrect when the printed file has no extention. I've reproduced this with a Word document (just strip the extention yourself and reload it in Word). Using the REDMON-variable does not help. Attached are links to two screenshots.

 

Please advise.

Kind regards,

Roel

 

Printer queue: http://i51.tinypic.com/t4xyf6.png

Result on disk: http://i55.tinypic.com/2d9cuv8.png

If the document in PDF-queue has no extention (.doc), de filename of the generated PDF is missing the last character. Please fix this bug. I'm unable to apply your software in my organisation at this moment.

Kind regards,

Roel 

This happens only if the first and\\or last character is a bracket. Try it out. And it was by design because PDFCreator and some old versions of Ghostscript can't handle if the internal postscript file has bracket for the title at the beginning or end. So PDFCreator removed these brackets. But this problem was fixed in one of last versions. I did some test and found that we can remove this workaround.

I think this is what you want and need.

That would be great! Thank you for your time and effort.

Kind regards,

Roel

It would be great if you could test it.

 Hi Frank,

I've tested it with the latest release 1.2.2. 'this is an (test).rtf' produces the pdf-file 'this is an (test.pdf'
It fits your statement that the bracket is cousing the problem, and not the absence of the extention.

I'm not able to change the filename of the documents that I want to send to PDF-Forge. But in your post you mention you can remove the workaround. This would help me use your product.

Kind regards,

Roel


 

 Hi Frank,

Do you need any input from me, or can you remove the workaround in the next release?

Kind regards,

Roel

The new 1.2.3 release solves my problem.

Thank you!

 Hi Frank,

Do you need any input from me, or can you remove the workaround in the next release?

Kind regards,

Roel

  Hi Frank,

Do you need any input from me, or can you remove the workaround in the next release?

Kind regards,

Roel