We have an application that replaces spaces with "%20" in the file name to make it a valid URL. The issue is that it appears that novaPDF see's the %2 as a parameter and mis-behaves. It tries to replace the %2 with whatever seems to be available in the command that was used to call it. This issue can be replicated by simply putting %1, or %2 in the file name of a pdf document, opening it and trying to print it to the novaPDF virtual printer. We are currently only using one parameter ( %1 ) as the file name to be sent to the receiving program. We are using version 8.
Has anybody experienced this, and is there a solution?
Have questions about novaPDF (desktop or server), or having problems using it? Ask here for help.
2 posts • Page 1 of 1