>penguin would shrink the result to fit its screen.
>I declared A5 and Letter paper, media type stationery, and an output bin called face-up.
You can (and should!) define exact dimensions of your screen in `media-size-supported`. It will probably be a non-standard IPP name, that's why you should define that in `media-supported` as `om_NNNmmxYYYmm` or `oe_NNNinxYYYin`
That way you don't need to scale the incoming data, the PC will format it exactly to the dimensions of the screen.
Both PWG Raster and Apple Raster support 1-bit-per-pixel mode (instead of 8-bit-per-pixel you use), that's why the input could be 8 times less in size. Use `print-color-mode-{supported,default}=bi-level` instead of `monochrome` for that. And also tune `urf-supported`'s `W` option, use `W1` for this case.
This is why I like it here. Somebody does irrefutably incredible work outside of their comfort zone, and somebody else goes "yeah actually I was born in that zone. Moulded by it. Here's how to improve it" (in a positive way)
Oh no, I wasn't, and that's definitely not my comfort zone. I mess with the printers and printing stack due to anger, not because I like it.
It's bugs on bugs, with bugs chasing bugs! So little developers, so complex stack with 25 years of technical debt, and little community around because it's not a sexy technology to be involved in.
That's why I have to dive deep and fix my bugs myself if I want to make it work properly as I would like it to. I also ended up making my own print server device, because China did not make a proper one for some reason for all these years.
Very cool. I was expecting to learn about the ins and outs of ink, printheads etc but instead learned "How to build a paper that acts like a printer" which turned out much more entertaining.
In Linux it's pretty easy to create such things with cups. A while ago I did a cups backend for my Fujitsu Quaderno A4 [1]. It is super useful to be able to just open any document, in any program that supports printing, and then just "print" it to my device.
Unfortunately printing support seems to go out of fashion, at least in macOS land.
Lately I needed a quick printout of a markdown document. I could have used TextEdit for the raw text, but I wanted the styling too. Learned that neither VSCode, Xcode nor Obsidian can print. (There is a community plugin for Obsidian.)
One of the great things about having an open platform like the Xteink is that it should uncover loads of novel and unsatisfied use cases. Eg, this could be paired with a mobile phone to act as a secondary display much better suited to outdoor applications in bright sunlight.
working on an daily life ePub generator (because I want to stick to CrossPoint) with the opposite goal, namely use the phone as little as possible, but I admit I would also like to tinker with an additional temporary display, at least for typing
How is that open source? There’s not a single line of code. No CAD. Nothing. Sure, there’s a “coming soon” CrowdSupply link, which I guess is more than a KickStarter. But open source?
Fair enough but I trust CrowdSupply to keep them in check. I bought quite a few projects via CS and never been disappointed. They have too much trust from the community not to follow up, it's their most important differentiator versus KickStarter and other crowdfunding platforms.
Pretty cool work! And it’s nice to see printer discovery works through the standard mDNS!
Regarding the size of the page being sent to the printer, I remember reading that printers used to be postscript interpreters and the result of that program would be the page.
Perhaps that would trade ram for compute, but might be more complex in the end.
I've wanted something like this for a long time to print recipes that I'm about to cook. I don't want my phone in the kitchen getting gunk on it, so I'll usually print on paper, get the gunk on the paper, and then throw it out.
I'm not going to create a recipe PDF and load it on an e-reader. That's too much work. But I will happily press control-P on a recipe web page and select the eink display as the target.
I'd like my e-reader to show up as a printer, and when I print something on it it actually gets saved as a pdf on the reader. Like in the article, but multi-page pdf.
I often do 'print to A5 pdf => copy pdf to e-reader'. Would be nice to do that in one step from any program that can print.
> I was thinking of this, but rendering PDF takes a lot out of a 400KB RAM'd device. It also needs a ton of things to actually work which the ROM can't hold.
PDF is very, very complicated standard which can't be handled properly on tiny MCUs with reasonable performance and spec conformance:
- 4 font formats
- 9 image formats
- blending with transparency
- different colorspaces, each image could use its own on the page
- different dithering algorithms, each image with its own
- the page can have elements from another pages (global elements)
This is only a small part from the top of my head.
Common simple home printers absolutely should not accept regular PDF as an input: thanks to Apple and IETF we now have Apple Raster and PWG Raster for printers, as a part of AirPrint and IPP Everywhere/Mopria driverless printing standards, which are very similar but have slightly different options and headers. It's a simple raster input for printers specifically.
Some companies, such as HP, invented a "raster PDF": PCLm / PCLms. Don't be confused by the name, it's a regular standard-conforming PDF which contain nothing but a full-page JPEG on each page, and don't use any other features. It's created only to be able to open "printed page" (driver output) in a standard PDF viewer on a PC for debugging or business logging needs, but otherwise it's like a regular JPEG with additional per-page metadata.
I was thinking of this, but rendering PDF takes a lot out of a 400KB RAM'd device. It also needs a ton of things to actually work which the ROM can't hold.
I've been seeing the Xteink a lot lately. Should I get an X3 or an X4? I don't really know why I want it, but I have an eInk addiction, so I just need it.
I bought an x4 a month or so ago, zero regrets. It sounds hyperbolic but it’s finally been the thing to actually decouple me from my phone. Whenever I’m out and about, bored, I just slide it out and pick up where I left off reading last. It’s a nicer reading experience on my kobo but the portability and.. frankly charm just can’t be beat.
>penguin would shrink the result to fit its screen. >I declared A5 and Letter paper, media type stationery, and an output bin called face-up.
You can (and should!) define exact dimensions of your screen in `media-size-supported`. It will probably be a non-standard IPP name, that's why you should define that in `media-supported` as `om_NNNmmxYYYmm` or `oe_NNNinxYYYin`
That way you don't need to scale the incoming data, the PC will format it exactly to the dimensions of the screen.
Both PWG Raster and Apple Raster support 1-bit-per-pixel mode (instead of 8-bit-per-pixel you use), that's why the input could be 8 times less in size. Use `print-color-mode-{supported,default}=bi-level` instead of `monochrome` for that. And also tune `urf-supported`'s `W` option, use `W1` for this case.
The screen/dithering could be ass in 1-bit mode, see https://github.com/OpenPrinting/libcupsfilters/pull/160 where I added more dithering options (Linux-only though, Apple seems to abandon their CUPS).
This is why I like it here. Somebody does irrefutably incredible work outside of their comfort zone, and somebody else goes "yeah actually I was born in that zone. Moulded by it. Here's how to improve it" (in a positive way)
Oh no, I wasn't, and that's definitely not my comfort zone. I mess with the printers and printing stack due to anger, not because I like it.
It's bugs on bugs, with bugs chasing bugs! So little developers, so complex stack with 25 years of technical debt, and little community around because it's not a sexy technology to be involved in.
That's why I have to dive deep and fix my bugs myself if I want to make it work properly as I would like it to. I also ended up making my own print server device, because China did not make a proper one for some reason for all these years.
Anger is the only valid emotion when dealing with printers.
That's even cooler
Same feeling when family or friends ask me for help with Micros word about formatting, tables or inserting pictures in the last 25 years….
lovely, this would save me a bunch of memory during transformation and dithering. Will do!
> Use `print-color-mode-{supported,default}=bi-level` instead of `monochrome` for that
The last time I checked (a year ago), 1bpp was suddenly supported only by Windows. IIRC, monochrome is REQUIRED, while bi-level is OPTIONAL in RFC.
Not sure how things stand now, though. Ever since then, I've just been carrying Floyd–Steinberg dithering around.
Very cool. I was expecting to learn about the ins and outs of ink, printheads etc but instead learned "How to build a paper that acts like a printer" which turned out much more entertaining.
Wanted ideas on how to build an ink printer that is untraceable. For privacy reasons.
glad you liked it!
This would be a neat API for a digital photo frame - just print photos to it and they appear on the screen.
yes!!
In Linux it's pretty easy to create such things with cups. A while ago I did a cups backend for my Fujitsu Quaderno A4 [1]. It is super useful to be able to just open any document, in any program that supports printing, and then just "print" it to my device.
[1] https://github.com/cristobaltapia/dpt-rp1-cups
> any program that supports printing
Unfortunately printing support seems to go out of fashion, at least in macOS land.
Lately I needed a quick printout of a markdown document. I could have used TextEdit for the raw text, but I wanted the styling too. Learned that neither VSCode, Xcode nor Obsidian can print. (There is a community plugin for Obsidian.)
LOL. TIL you can’t print from VSCode.
printing has never really been a thing from text editors I think.
Used to be that printing a text file was just `cat myfile.txt > /dev/lp0` .
It has been a while since I printed a plain text file, but I guess there's still a similar command available with some research.
TextEdit.app supports printing, so does Notepad.exe (unless they removed that recently).
I've done the same from a raspberry pi to a receipt printer, just piping to lp0
vim/nvim at least have :print
Or Obsidian
Good article.
One of the great things about having an open platform like the Xteink is that it should uncover loads of novel and unsatisfied use cases. Eg, this could be paired with a mobile phone to act as a secondary display much better suited to outdoor applications in bright sunlight.
working on an daily life ePub generator (because I want to stick to CrossPoint) with the opposite goal, namely use the phone as little as possible, but I admit I would also like to tinker with an additional temporary display, at least for typing
Emulating a network printer to send pages to an e-ink screen is such a clever hack. Every OS already has the print dialog built in.
Just like print-to-pdf is (one of many) peeves of adobe's
Good job, but I’m left wanting to know how to build a printer.
If a DIY plotter would do, this site has a long list of different projects
https://mattwidmann.net/notes/pen-plotters/
What if I want a cabinet sized rotating head printer that can print carbonpaper triplets, sounds a machinegun, and has LP0 ON FIRE error message
I'd say it's an eco-friendly printer
There is an open source one https://www.opentools.studio
How is that open source? There’s not a single line of code. No CAD. Nothing. Sure, there’s a “coming soon” CrowdSupply link, which I guess is more than a KickStarter. But open source?
Fair enough but I trust CrowdSupply to keep them in check. I bought quite a few projects via CS and never been disappointed. They have too much trust from the community not to follow up, it's their most important differentiator versus KickStarter and other crowdfunding platforms.
Ah sorry, I thought they were already open source. They say they will open source it once they finalize the design, but yeah, not there yet.
Nice. I keep wondering if these devices would play nicer with DjVu rather than pdfs and raster formats?
https://djvu.sourceforge.net/
Pretty cool work! And it’s nice to see printer discovery works through the standard mDNS!
Regarding the size of the page being sent to the printer, I remember reading that printers used to be postscript interpreters and the result of that program would be the page.
Perhaps that would trade ram for compute, but might be more complex in the end.
This is amazing!!! It just makes sense. And its just how you would want to use a e reader.
if it looks like a paper, it should act like a paper
You can even fold it, once!
It's also not effective against rock
Funny. But... paper covers rock.
Jan Ken Po!
Love this!
I don't understand the purpose. What am I missing?
The author "prints" to the eink display. Why not load say the pdf directly?
I've wanted something like this for a long time to print recipes that I'm about to cook. I don't want my phone in the kitchen getting gunk on it, so I'll usually print on paper, get the gunk on the paper, and then throw it out.
I'm not going to create a recipe PDF and load it on an e-reader. That's too much work. But I will happily press control-P on a recipe web page and select the eink display as the target.
Right! I like this usecase very much. For uses existing software infra to perform the required task.
I wonder now what else we've reinvented when it comes to sending data...
I am no cook, but you my friend are cooking something here
From the 4th line in the article:
> But getting stuff onto it was tedious. I had to join its hotspot and open a little upload website in my browser. Yuck.
Anyway, very creative, I like the idea a lot.
I'd like my e-reader to show up as a printer, and when I print something on it it actually gets saved as a pdf on the reader. Like in the article, but multi-page pdf.
I often do 'print to A5 pdf => copy pdf to e-reader'. Would be nice to do that in one step from any program that can print.
> I was thinking of this, but rendering PDF takes a lot out of a 400KB RAM'd device. It also needs a ton of things to actually work which the ROM can't hold.
> Kindles have a ton of RAM, this one didn't.
It's an e-reader. According to the specs it has native support for PDF.
It's an esp32 MCU, even if it can somehow run the PDF render pipeline, it won't be more ideal than just accept the raw byte stream and display.
I love the concept, but I wonder why he wasn’t printing to PDF. Can this device not render PDFs?
PDF is very, very complicated standard which can't be handled properly on tiny MCUs with reasonable performance and spec conformance:
This is only a small part from the top of my head.Common simple home printers absolutely should not accept regular PDF as an input: thanks to Apple and IETF we now have Apple Raster and PWG Raster for printers, as a part of AirPrint and IPP Everywhere/Mopria driverless printing standards, which are very similar but have slightly different options and headers. It's a simple raster input for printers specifically.
Some companies, such as HP, invented a "raster PDF": PCLm / PCLms. Don't be confused by the name, it's a regular standard-conforming PDF which contain nothing but a full-page JPEG on each page, and don't use any other features. It's created only to be able to open "printed page" (driver output) in a standard PDF viewer on a PC for debugging or business logging needs, but otherwise it's like a regular JPEG with additional per-page metadata.
This thing is an e-reader with 16GB of flash and an SD slot. It has native support for PDF.
https://cdn.shopify.com/s/files/1/0759/9344/8689/files/X3-EN...
check page 3. even I was surprised
First I see GIF and PNG missing.
CrossPoint at least only support ePub and BMP so they could have printed to a directory of BMPs.
I was thinking of this, but rendering PDF takes a lot out of a 400KB RAM'd device. It also needs a ton of things to actually work which the ROM can't hold.
Kindles have a ton of RAM, this one didn't.
I'm sure there's a super trimmed down linux pdf reader that could be ported over
Probably not. It doesn't appear to have enough ram. I'm not sure the CPU is up to that either.
I've been seeing the Xteink a lot lately. Should I get an X3 or an X4? I don't really know why I want it, but I have an eInk addiction, so I just need it.
I've owned all of them and the answer is the X4 Pro IMO. It has a backlight, which is the only thing I really missed on the others.
It's funny that X3 is a successor of X4. Only downside is that X4 has a USB-C port and X3 doesn't
What about the back light? Are they otherwise identical?
X3 isn't backlit, but the battery lasts 7 days. So, it's pretty good for me
I bought an x4 a month or so ago, zero regrets. It sounds hyperbolic but it’s finally been the thing to actually decouple me from my phone. Whenever I’m out and about, bored, I just slide it out and pick up where I left off reading last. It’s a nicer reading experience on my kobo but the portability and.. frankly charm just can’t be beat.
This is a fantastic idea!
Very cool. I'll be updating to this fork
Thanks. It's rough around the edges, so PRs are open, and there's a recipe in the repo if you want to build your own apps.
We finally have PADDs from Star Trek!
Wow!! I didn't think of that.
Outstanding! This is so...correct.