![]() If you printed text, you could tell the printer to print text "xyz" in font TimesNewRoman (or whatever) and the printer would calculate all the dots for you (which meant the printer had to know the font, or you had to download the font to the printer ahead of time). Obviously if you did this the amount of data going to the printer would be a lot more and could choke the printer. For example, in HPGL (or PCL) you could give a command that would basically says "please print this bitmap, and here is the raster data" followed by a gigantic blob of binary data. You could also embed a bitmap as binary data. So, you could send your print out in either of those two languages and the printer would convert your code to dots on the page. In the old days, there were two main types of printers: HP printers that understood HPGL and Postscript printers. I understand the way it worked in the "old days", and am trying to understand the more complex modern world. In other words, what happens when the user tells my application they want to print something. I am trying to understand my options for communicating programmatically with a printer to get something printed from application software. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |