-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Raw Printing in printnode increases the size of the content by 33% approx #10
Comments
Hi Vasudharsai,
If printing RAW documents the content is sent directly to the printer. Normal printing options like "fit to page" or "page size" generally don't have a effect.
To increase the size of your content you'll want to have a look at how to do that in the RAW printing language you are using. I'm afraid PrintNode can't help with the content creation side of the printing process.
Thanks,
Peter
…--- original message ---
On November 15, 2018, 8:39 PM UTC [email protected] wrote:
I'm printing 4x1 labels and trying both raw_uri and raw_base64 and that prints out the label with size of the content increased by 33% approx. Below is how I'm creating PrintJob
my_printjob_info = PrintNode::PrintJob.new(printer_id, 'PrintJob_OE4', 'raw_base64','InventorySticker_363467.txt', 'PrintNode-OE4') #using raw_base_64
my_printjob_info = PrintNode::PrintJob.new(printer_id.to_i, 'PrintJob_OE4', 'raw_uri',uri, 'PrintNode-OE4') # uri is the url in my application through which the file could be downloaded.
Please advice. Thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
--- end of original message ---
|
Not sure we are talking about the same thing but for base64 : the ratio of output bytes to input bytes is 4:3 (33% overhead). So that would be completely normal. Cf https://en.wikipedia.org/wiki/Base64 |
Sorry Vasudharsai I misunderstood your question. Quentin's reply is both accurate and a lot more helpful.
Base64 encoding is used so that arbitrary binary data can be safely encoded in a JSON HTTP request body. This does make the API request to POST /printjobs more inefficient from a bandwidth point of view but these inefficiencies stop there. When the client software downloads any content it downloads a base64 decoded version without any base64 encoding overhead.
…--- original message ---
On June 14, 2019, 6:49 PM UTC [email protected] wrote:
Not sure we are talking about the same thing but for base64 : the ratio of output bytes to input bytes is 4:3 (33% overhead). So that would be completely normal.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
--- end of original message ---
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm printing 4x1 labels and trying both raw_uri and raw_base64 and that prints out the label with size of the content increased by 33% approx. Below is how I'm creating PrintJob
my_printjob_info = PrintNode::PrintJob.new(printer_id, 'PrintJob_OE4', 'raw_base64','InventorySticker_363467.txt', 'PrintNode-OE4') #using raw_base_64
my_printjob_info = PrintNode::PrintJob.new(printer_id.to_i, 'PrintJob_OE4', 'raw_uri',uri, 'PrintNode-OE4') # uri is the url in my application through which the file could be downloaded.
Please advice. Thanks
The text was updated successfully, but these errors were encountered: