[DVIPDFMx] Re: latest change to pdfnames.c

[Jin-Hwan Cho]

On Jun 17, 2008, at 4:28 PM, Matthias Franz wrote:

> why did you turn off the warning message in pdfnames.c (unless
> we are in verbose mode)? It might indicate a serious problem
> in the DVI file.

I remember that I got some annoying warning messages which were
due to (maybe) a bug in hyperref.sty. The bug was in the routine of
captions of Figures and Tables.

I thought that ordinary people do not want to see warning messages
because they cannot do anything. However, as a matter of fact, it would
be better to fix the bug in hyperref.sty.

I do not mind if you want to restore the original code for this case.
Actually, I should try to report the bug to the author of hyperref.sty,
but I didn't . I don't know why. Maybe I forgot.

> I've come across this situation (multiply defined object reference)
> when I concatenated DVI files with dviconcat while using hyperref.
> Here the problem is not serious. But another question comes up:
>
> What should we do if an object reference is redefined? Currently
> we discard the new value (BTW, there is a memory leak, i.e., no
> pdf_release_obj). If you think of the situation where DVI files are
> concatenated, it might be better to replace the old value.

It would be better to support both ways. How? I have no idea yet.
In many cases, I also wanted to replace the previous value, but we
should think about the compatibility to the previous versions.

Why don't you make a new special or a new option which supports
replacing?

Best regards, ChoF.