<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>UTF-8 on Artur Rios Lab</title><link>https://lab.artur-rios.tech/tags/utf-8/</link><description>Recent content in UTF-8 on Artur Rios Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 20 Oct 2026 17:00:00 +0000</lastBuildDate><atom:link href="https://lab.artur-rios.tech/tags/utf-8/index.xml" rel="self" type="application/rss+xml"/><item><title>What Is Text Encoding? From Telegraph Codes to Unicode and UTF-8</title><link>https://lab.artur-rios.tech/fundamentals/text-encoding/</link><pubDate>Tue, 20 Oct 2026 17:00:00 +0000</pubDate><guid>https://lab.artur-rios.tech/fundamentals/text-encoding/</guid><description>&lt;p&gt;A computer stores nothing but numbers. Every letter you read on a screen, every&#10;name in a database and every line of source code is held as a sequence of&#10;numbers, and something has to agree on which number means which character.&#10;That agreement is a &lt;strong&gt;text encoding&lt;/strong&gt;. When it works, nobody notices. When two&#10;programs disagree, &amp;ldquo;café&amp;rdquo; turns into &amp;ldquo;cafÃ©&amp;rdquo;, a customer&amp;rsquo;s name is rejected as&#10;invalid, or an emoji crashes a database insert. This article explains what a&#10;text encoding is, how the world got from telegraph codes to Unicode, how the&#10;modern encodings work bit by bit, and where text still goes wrong. The examples&#10;were run with Python 3.10 and Node.js 12, and their output is shown as printed.&lt;/p&gt;</description></item></channel></rss>