Bonjour :) On Wed, Aug 01, 2012 at 09:48:56AM +0200, Hans Hagen wrote:
On 31-7-2012 14:18, Tobias Mueller wrote:
I'd like ConTeXt to raise an error if it can't find an image when using \externalfigure. I really don't want to check a potentially big document for missing images manually and while I could grep the log myself in an additional post processing step, I really want ConTeXt to do raise the error for me, not a potentially broken script written by me.
often in the process of writing a missing (pending ) image is no reason for an abort
Hm. I consider it a serious and fatal error if I requested an image to be included and it not being available. I would want to know how much space the image occupies, where it is placed, whether it makes words wrap correctly. And that's only in the development process of document. During "deployment" it is a much bigger problem for me. I use to generate my documents on a server (i.e. after committing to my favourite version control system) and have them automatically published. Obviously, I want the document generated by the server to look the very same. And I am very good at accidentally not checking in dependencies to my VCS. So the server side might in fact lack the necessary images. And I wouldn't want to embarras myself by having a document missing images. So a failure in the build process would help me a lot.
So my question is: How can I make ConTeXt raise an error on a non found image?
Currently it's not possible. Too sad. Looking forward to later this year then.
aborting a run would also mean that the partial pdf should be removed. I don't think it is necessary. Just having the program not returning a 0 exit code would help at least me for now.
Cheers, Tobi