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.
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.
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?
> 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 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.
>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.)
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.
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.
Brian_K_White | 11 hours ago
andyfilms1 | 10 hours ago
[OP] cat-whisperer | 10 hours ago
jarboot | 10 hours ago
[OP] cat-whisperer | 10 hours ago
nomel | 10 hours ago
[OP] cat-whisperer | 9 hours ago
valleyer | 9 hours ago
sudo_cowsay | 9 hours ago
stavros | 10 hours ago
[OP] cat-whisperer | 10 hours ago
stavros | 9 hours ago
[OP] cat-whisperer | 9 hours ago
a2dam | 10 hours ago
hamaluik | 8 hours ago
sho_hn | 9 hours ago
joshmarinacci | 9 hours ago
[OP] cat-whisperer | 9 hours ago
Kindles have a ton of RAM, this one didn't.
bluGill | 9 hours ago
ValdikSS | 8 hours ago
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.
ghostly_s | 8 hours ago
[OP] cat-whisperer | 7 hours ago
check page 3. even I was surprised
silon42 | 3 hours ago
ks2048 | 9 hours ago
[OP] cat-whisperer | 9 hours ago
tdeck | 6 hours ago
https://mattwidmann.net/notes/pen-plotters/
voxelghost | 3 hours ago
d--b | 5 hours ago
zxexz | 2 hours ago
d--b | an hour ago
greazy | 9 hours ago
The author "prints" to the eink display. Why not load say the pdf directly?
[OP] cat-whisperer | 9 hours ago
> Kindles have a ton of RAM, this one didn't.
ghostly_s | 8 hours ago
mrheosuper | 7 hours ago
stdatomic | 9 hours ago
> 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.
sowbug | 5 hours ago
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.
[OP] cat-whisperer | 4 hours ago
greazy | an hour ago
I wonder now what else we've reinvented when it comes to sending data...
maybewhenthesun | 2 hours ago
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.
NDlurker | 9 hours ago
[OP] cat-whisperer | 9 hours ago
ValdikSS | 8 hours ago
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).
[OP] cat-whisperer | 8 hours ago
Neywiny | 8 hours ago
ValdikSS | 7 hours ago
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.
edoceo | 5 hours ago
quijoteuniv | 3 hours ago
lopis | 3 hours ago
darkvision77 | 2 hours ago
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.
alternativeworl | 8 hours ago
[OP] cat-whisperer | 7 hours ago
a3w | 13 minutes ago
e12e | 4 hours ago
https://djvu.sourceforge.net/
tapia | 4 hours ago
[1] https://github.com/cristobaltapia/dpt-rp1-cups
IdiotSavage | 4 hours ago
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.)
rrr_oh_man | 3 hours ago
simonjgreen | 3 hours ago
maybewhenthesun | 2 hours ago
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.
voidUpdate | an hour ago
jiehong | 3 hours ago
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.
kitd | 2 hours ago
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.
yeasin-arafat | an hour ago
pimterry | an hour ago
[OP] cat-whisperer | an hour ago
Wilson2000 | 40 minutes ago