We ran into this issue a few months back and worked with a prince rep to figure out what was going on. We have some incorrectly labeled files on S3, this causes prince to think a file is of one type when it is actually another. Unfortunately do to some legacy system we don't have a quick fix our our issue. I'm just wondering if it there is any flag to pass prince for it to not trust the file's mime type and look it up using the file command or similar until we can depreciate or legacy systems.

Thanks,
Tys von Gaza

Example warning:
https://s3.amazonaws.com/documents.domain.com/logos/5742/image.gif?AWSAccessKeyId=key&Expires=1289334273&Signature=signature: warning: Could not load GIF file

The above file is actually a JPEG.

In the next release, Prince will basically ignore the MIME type and try to figure out what the image is by looking at it, the same as browsers do. If you like I can provide you with a temporary build until the final release is ready, just send me an email (mikeday@yeslogic.com) and let me know which platform you are running Prince on.