dave.r...@gmail.com
unread,Feb 27, 2015, 3:17:23 PM2/27/15Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to qz-p...@googlegroups.com
We are in the process of evaluating the QZ-Print plugin solution for use in our web based applications.
Our applications run in various hardware environments (e.g. desktops, laptops, tablets) with many browsers (e.g. Chrome, Firefox, Safari, Internet Explorer) and under various software environments (e.g. Windows, Mac OS, iOS, Android).
We have three types of printers to which output needs to be sent: standard printer with 8.5 x 11 in paper, thermal receipt printers with 80mm paper roll (e.g. EPSON, POSX, Star), and label printers with various sized labels (e.g. Zebra GK420d).
The content that needs to be sent to these printers has been carefully crafted via HTML and CSS. Things are working correctly when the browser print operation is invoked. However, we want to bypass the browser print invocation and send the printer output programatically. This will enable us to reduce the number of clicks our users experience when printing something.)
We have been conducting some tests using the free version of your product using the sample.html code as a model.
Up to a point, the printHTML example in the QZ-Print sample.html code meets our needs. However, the comment in that code indicates that only "plain HTML 1.0" can be managed by this routine. We have conducted tests which reveal that the following CSS elements are not processed properly:
float: left
display: inline-block
transform-origin: left bottom
transform: rotate(90deg) translate(-50px,0px)
Is there any possibility that the printHTML approach is more fully implemented in the "professional" version of your product?
Will the printHTML5 approach illustrated in your sample.html code be likely to handle these additional CSS elements?
The fundamental question here is this: will the latest version of the "professional" release of your product properly handle the presentation of printer output that is specified within a web page using HTML and CSS? More specifically, can we send as input a string that contains HTML and CSS code and produce as output the proper result on the appropriate printer?