In message <69802b7754.Andrew-Pin@xxxxxxxxxxxx> Andrew Pinder <Andrew.Pinder@xxxxxxxxxxxxx> wrote: > In message <b0d4217754.John@xxxxxxxxxxxxxxxxxxxxx> > on 16 Dec 2014 John Norris <jrn@xxxxxxxxxxxxxxxxx> wrote: >> You may well be right but I don't see how it's relevant to my case >> where I am using a PCL driver, not a PostScript driver, to print pdf >> files - unless the implication of what you are saying is that text in >> the pdf file is already inherently flawed by the use of PS2 drivers to >> create it in such a way that it can be viewed but not printed. Given >> that the Pi will happily print such files complete with text, whereas >> the Pandaboard won't, suggests that the cause of the problem cannot >> rest wholly with the PS drivers. Re-reading the above I see I have, once again, written beyond my level of knowledge. In my case, trying to print pdf files via PCL to a non-PostScript printer, the PS driver issue is largely if not completely irrelevant. This is because even if a PS driver problem were in some way responsible for my own pdf files printing without text it wouldn't be relevant to pdf files generated by others, for example using Acrobat on a PC. Yet these too print without text from my PandaRO (but print correctly from my Pi and RiscPC). > I have a vague recollection that problems have been caused by text > needing to be converted to paths in order to print to PostScript. Or > am I muddling things up? No I don't think you are muddling things up as if I convert text in, say, a Drawfile to path before creating a pdf file then the text prints OK. However that doesn't help much with 'non-graphics' text in a pdf file. John Norris --- To alter your preferences or leave the group, visit //www.freelists.org/list/armini-support List-related queries to info@xxxxxxxxxxxx