Quote:
Originally Posted by chrisix
As I told, it stops without any error, and the pdf at which one it stops is random. I think it has something to do with the unixutlis, your script is clean and I don't see any reason for stopping.
|
If you look at the script and run the commands just one by one does it then work?
Its really wierd because if the pdf doesn't contain an ISBN number the script will print the name of the PDF and then process the next one, printing the name and move on. One thing that might cause this is a pdf file which isn't strictly conforming to the specs.
We have an application which import a pdf which is first split into single pages and the application which generates this multipage pdf generates an invalid pdf. (MS reporting service)
Quote:
When I have a lot of time I will try to rewrite your script with windows powershell if it is possible 
|
That thought crossed my mind too but I'm a little more proficient with unix commands then with powershell.
Regards,
Joop