[texhax] Problem with Adobe Reader 8

tom sgouros tomfool at as220.org
Thu Nov 1 16:21:30 CET 2007

Hello all:

I have been corresponding with an Adobe QC engineer about this.  He
tells me that this bug is already in their bug system, but there does
not seem to be an action plan to fix it.  Somewhat edited, here's his

> turns out not to be a new bug, I found a couple about it already in the db.
> it appears that the bug in question is actually in the underlying type
> library, which is shared, so if you have the chance, get it filed
> against Illustrator too, I notice that it won't import properly,  I'll
> file it here, but internal bugs get more attention when they are
> mirrored in externally generated bugs. plus, bugs against the creative
> suite seem to get more traction. 
> the more people who can file similar bugs at this web page:
> <http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&product=46>
> the more likely something is to get fixed.  this is the reporting page
> for all adobe products.  if you can get the whole mailing list to file
> individual bugs, that might do it.  plus the new bug system allows
> some customer voting to go on.  (though I'm not entirely sure how it
> works...) 
> spread the address around.  just make sure that the bugs are well
> written and clear. the easier it is for some one in house to reproduce
> the bug from a clear explanation, the more likely the bug is not
> ignored.  It's currently my month to monitor <snip> and the number of
> bugs I have to ditch because they are unintelligible is pretty high. 


> the upshot is unless there is more pressure from customers, or
> someone can convince them that it's really acrobat's fault and not a
> faulty but up-until-recently-tolerated ghostscript problem it doesn't
> look like anything is going to be done.
> I've added the bug files to the existing bug in the db, but I am not a
> viable source of pressure to get something like this
> changed...

Some follow up:

> all of the above really. the bug refers to "ligatures being replaced
> by spaces when displaying pdfs generated by ghostscript."

> probably worth noting in the report that it displays properly in
> other current pdf display applications.

> to help narrow it down, you can also point out that the ligatures
> fail to import into illustrator 13, (noticed that yesterday) don't
> know if it's also true of photoshop, I don't currently have a new
> version installed to try it on.


 tomfool at as220 dot org

More information about the texhax mailing list