<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ci-Cd on Caleb Christensen</title><link>https://calebc42.com/tags/ci-cd/</link><description>Recent content in Ci-Cd on Caleb Christensen</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 06 May 2026 17:57:26 -0600</lastBuildDate><atom:link href="https://calebc42.com/tags/ci-cd/index.xml" rel="self" type="application/rss+xml"/><item><title> Solving the "Blurry Line" Problem: Engineering a Python CLI for E-Ink Devices</title><link>https://calebc42.com/posts/eink-template-gen/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://calebc42.com/posts/eink-template-gen/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;I love my Supernote Manta. It’s a fantastic e-ink writing tablet. But like many e-ink devices (reMarkable, Boox), it suffers from a specific hardware constraint: &lt;strong&gt;&lt;strong&gt;no sub-pixel anti-aliasing&lt;/strong&gt;&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;If you take a standard PDF template —say, a ruled notebook page generated by a generic tool— and load it onto the device, the lines often look gray, fuzzy, or inconsistent. This happens because the lines land on fractional pixel coordinates (e.g., \(y = 10.4\)), forcing the display controller to dither the pixels. On a crisp 300 DPI e-ink screen, this blur is immediately noticeable and reduces the &amp;ldquo;paper-like&amp;rdquo; contrast.&lt;/p&gt;</description></item></channel></rss>