On Sep 1, 2005, at 12:13 AM, Ralf Stubner wrote:
Well, the /ideal/ person to fix this bug would be the author of
dvipdfm.
However, dvipdfm is licensed under GPL, so it is possible to fix this
bug, if one knows what has to be done. I have no idea what is causing
these problems, though. :-(
If you have the source code of DVIPDFM, check the file "pdfobj.c".
In the line 631, the function pdf_check_name() checks the validity
of the character "#". However, the variable "valid_chars" does not
contain "#".
Of course. Can dvipdfmx be used as a drop-in-replacement for
dvipdfm,
even if you don't process CJK files? Are there any disadvantages?
If that where possible, it would be ideal, since dvipdfm seems to be
pretty dead upstream. My personal experiences with dvipdfmx for non
CJK
texts has been pretty good, but I haven't made any extensive tests.
For more than 3 years, DVIPDFMx have been extensively tested by many
users. There might be some bugs which are not found yet. But the authors
of DVIPDFMx try to fix immediately if reported to them.
Best, ChoF.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
