Urgent.News

What's breaking now, across thousands of outlets.

Tech

Why styled text turns into a little square (tofu): font fallback and Unicode

You paste a name in bold italics in the profile, it appears perfect on your cell phone, and a friend warns that he only sees a row of squares. Nothing is wrong with the text. The problem is that his device couldn't draw those characters. This post explains why and shows two code traps that usually appear together. What is tofu The empty square is called tofu,…

Translated from Portuguese Read in Portuguese

A article discusses the issue of text rendering on different devices, particularly when using stylized fonts. When a device cannot render a certain character, it is replaced with a blank square called "tofu". The article explains that stylized text generators do not install fonts, but rather use Unicode characters that appear as bold, italic, or gothic letters.

However, these characters can cause issues with character counting and font rendering. The article provides two pitfalls to avoid: using ".length" to count characters, which can lead to incorrect counts, and not having a fallback font, which can result in tofu appearing. It also provides tips for accessible text rendering, including using a generic font family and not relying on stylized text for important information.

Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Designing a reverse proxy that survives a Plex SSRF

Designing a reverse proxy that survives a Plex SSRF Most guidance for CVE-2026-96655 ends at "upgrade to 1.43.3.10861". That is correct and sufficient for many owners.

  • Server-side request forgery in Plex mitigated using reverse proxy
  • Endpoint exploitation via /video/:/transcode/universal path parameter
  • Patching vulnerability is most comprehensive solution

Treating Safety as a Brake Is How Teams Fall Behind at Agent Speed

When software delivery accelerates, adding another approval before merge, another check before deployment, or a longer wait before release can feel like the responsible thing to do.

  • Treating safety as a brake slows down software delivery
  • Controls should be placed where risks originate, clearly defined, and timed carefully
  • Effective safeguards govern specific decisions, mitigate risk, and adapt to production data

Privacy Budgets for Email Verification

Email verification is often treated as a small feature: send a message, wait for a link, and mark the address as confirmed. In a real web application, it is also a data pipeline.

More from Friday 23 October →