Hi Clive,
Good point about the fallibility of Wikipedia, but they might be right. A quick look at the Adobe forum reveals that there have been multiple changes to what Acrobat does with fonts since 1993, and some of it has been further complicated by Microsoft.
My understanding (feel free to put me right) is that:
- PDF's generated by Richard's program do not contain an embedded font. Instead they contain a font name and expect the client's PDF Reader to provide the actual font.
- Adobe Acrobat has a number of standard fonts 'built-in'. If the pdf file calls for one of them all will be well. But there is the possibility that the list of standard fonts built into Acrobat has changed over time, or the font name is wrong, so that the named font can't be found. (There is also the possibility that Thor is using a third party pdf reader, with a slightly different font set.)
- If the PDF Reader fails to find the named font within the built-in set, it looks for the font on the host system. This opens up the possibility of the named font not being available at all, or on the system but in some way incompatible.
Thor's bug is interesting in that he gets blank pages. It implies that the document is being correctly populated but the font is empty, i.e all the characters produce white-space.
All supposition so far but I think the proposition could be tested by seeing if Thor gets readable text by using a font other than Helvetica, and/or by showing that a libharu program using Helvetica also produces blank pages on his computer.
I'm never quite sure if debugging programs is an interesting puzzle or a boring pain in the butt!
Dave