Urgent.News

What's breaking now, across thousands of outlets.

Tech

PDF Rendering in browsers

Why was the certificate blank? A user sent me a screenshot of a signed document. The signature was there. The certificate page behind it was empty. Not broken, not garbled. Just a clean white page with nothing on it, like the PDF gave up halfway through. Worked fine on my machine, obviously. It always does. How the preview works You can't hand a browser a raw PDF and call it a day (not when the…

A user reported a signed document with an empty certificate page, which appeared as a blank white page when viewed in a browser. This issue arose because the PDF rendering process in the Alpine container, used by the application, did not have the necessary fonts installed. Alpine containers are lightweight and minimal, often lacking fonts, which led to the pdf rendering tool pdftoppm failing to find a substitute font and rendering a blank page instead.

The cause of this was the Alpine distribution, which is designed to have minimal dependencies and come with very few fonts by default. When the pdftoppm tool tried to render the document, it could not locate any fonts to use, resulting in a blank page. The solution was to add Liberation fonts to the Dockerfile, as they are a drop-in replacement for the original 14 base fonts and maintain the document's layout and appearance.

Additionally, the application displayed typed signatures in a handwriting-like font called Dancing Script, but the generated PDF displayed these signatures in Helvetica Oblique, a completely different font. This discrepancy between what users saw on the screen and what was stored in the PDF led to confusion and potential legal issues, as the document was not what the users expected.

To address this, the developers included Dancing Script within the PDF itself, effectively embedding the font directly into the file. This fix ensured that the document displayed exactly what users saw on the screen, maintaining the integrity of the document as described by the application's pitch of "the document is exactly what you saw."

This experience underscored the importance of considering font dependencies when building and deploying applications, especially those that generate PDF documents.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

What are your goals for the week? #194

What are your goals for the week? What are you building this week? What do you want to learn? What events are you attending this week? This Week's Goals. Job Search. Network Apply Project work.

  • Job search, networking, and applying are this week's goals
  • Side projects and learning Co-Pilot are on the agenda
  • CSS Battles completion and Slack goal-setting thread encouraged

A fundação esquecida do RAG: Por que você deve estudar Recuperação de Informação (Information Retrieval)

Se você leu os últimos artigos desta série, percebeu um padrão: tentar resolver problemas de RAG (Retrieval-Augmented Generation) apenas trocando o modelo de embedding ou injetando mais dinheiro em…

  • RAG issues stem from over-reliance on complex architectures and expensive infrastructure
  • Information Retrieval (IR) offers classical search engine solutions to RAG problems
  • IR concepts like BM25 and Precision at K provide cost-effective, reliable search engine fundamentals

Six things reported green and were lying

Red gets attention. It's loud, it blocks the merge, somebody looks at it. Green gets a glance and a merge. In one working session on 2026-08-26 I went looking for false greens in my own project and…

  • Six false green assessments found in verification system
  • Checker tool returned zero due to incorrect delimiter
  • Comparison passed when both files did not exist

Begin with control; the real win is turning it into daily practice

To be fair, "we have a QMS" is the easiest checkbox in a notified‑body audit. The hard part is that regulators, auditors and — most importantly — frontline engineers do not care about your checkbox.

  • Companies start with control through policies and SOPs, but it's insufficient alone.
  • Auditors focus on system effectiveness, not paperwork; traceability is critical.

Arrêtez de choisir une méthode Agile. Choisissez une taille de promesse.

Version originale en anglais : https://dev.to/karkael/stop-picking-a-method-pick-a-promise-size-3956 Commençons par le débat auquel je ne crois plus : Scrum contre Kanban. C'est un débat de vitrine.

  • Experimented with Scrum, Kanban, and Strong Ownership methods
  • Changed only the size of the promise, not methodology
  • Four-person team with lead architect and parallel UX team

More from Monday 31 August →