[dvipdfmx] dvipdfmx: wrong exit status

[Shunsaku Hirata]

It's OK to change the dvipdfmx behavior when an image is
not found.

But dvipdfmx also continues processing when there is an
unprocessed special command, e.g., due to  syntax error.
In this case too the output may not be as the user expects.

For inconsistent font metrics problems, missing glyphs, and
in various other situations, dvipdfmx just gives a warning but
not aborts with bad status. All these situations can result in
an inconsistent output.

Maybe I need to reconsider how much dvipdfmx can tolerate.
I will consider this later again.


Thanks,
Shunsaku Hirata

2021年1月5日(火) 7:26 Karl Berry <karl at freefriends.org>:
>
> Hi Shunsaku,
>
>     I think this is the same behavior as dvipdfm and also as dvips.
>
> Huh. I didn't realize. Well, the behavior when acting as dvipdfm
> shouldn't be changed, but I think I'll try to change dvips. I see no
> reason why a missing image shouldn't be an error there as well.
>
>     I don't know why but there must be a reason for choosing
>     such behavior.
>
> I don't think so. Just random. "I can still generate an output file, so
> let's output successfully." No ...
>
>     If there are not so many practical benefits I'd rather choose
>     leaving this unchanged.
>
> The reason I think (x)dvipdfmx is the most important place to exit with
> bad status when an image isn't found is because of its function as the
> backend for xetex. If XeTeX found the image and xdvipdfmx didn't,
> something is badly awry with the user's search paths (or something), and
> they wouldn't necessarily realize this unless they actually looked at
> the output page.
>
> Wdyt? --thanks, karl.