Newline Printing

[MatthiasLohr]

Hi,

first, thanks for this great work! I now getting much more out of my label printer as before (where I used the device without PC :D). Now I'm addicted to print labels! :D

One thing: I experimented a bit with the QR code feature, I tried to print a VCARD QR code. However, for me, it looks like that newlines causing problems and always get printed as \n. Also, when having a 12mm laben band in the LabelManager 280, it is possible to print 2 lines directly with the device. This seems not to be supported by now, or am I missing something?

Best regards
Matthias

[maresb]

Hey @MatthiasLohr, do you still have your label printer? I just got a PR which implements a fancy GUI in #54, although I doubt it fixes this particular bug. If possible, would you be willing to test the new GUI with your printer? (My printer is unfortunately broken.)

You can install the testing version with

pip install git+https://github.com/MooVx/dymoprint@master

and then you run dymoprint_gui.

[MatthiasLohr]

I checked, see #54.

Printing two lines works, printing vcard QR codes doesn't.

Anyway, both should also be supported just by CLI, imho.

[maresb]

I might be a bit confused...

Running dymoprint "line 1" "line 2" should produce the label:

Is this what you mean by printing two lines from the CLI?

And the vcard QR issue... that has to do with the fact that some of the fields (presumably address) have newlines which aren't properly encoded?

[MatthiasLohr]

Oh, my bad! Somehow I tought dymoprint "line 1" "line 2" to print to labels, one after the other... But yes, works for me!

Then still the encoding issue with vcards remain - or in general the question how to place newlines in QR codes.

[maresb]

Great! I'm sorry I didn't answer your question earlier. I didn't read carefully enough.

Regarding newlines in QR codes from the command line, how exactly are you trying to enter them? With bash I'd try

dymoprint 'newline
character'

which should theoretically create a single "line" containing a newline character in the middle.

Maybe we need to improve the README with some tips like this, once we figure out what works.