<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>I18n on vanityURLs</title><link>https://vanityurls.link/en/tags/i18n/</link><description>Recent content in I18n on vanityURLs</description><generator>Hugo</generator><language>en-CA</language><lastBuildDate>Wed, 03 Jun 2026 14:44:13 -0400</lastBuildDate><atom:link href="https://vanityurls.link/en/tags/i18n/index.xml" rel="self" type="application/rss+xml"/><item><title>Accents, IDN, and short-link slugs</title><link>https://vanityurls.link/en/blog/accents-idn-and-short-link-slugs/</link><pubDate>Mon, 01 Jun 2026 00:00:00 +0000</pubDate><guid>https://vanityurls.link/en/blog/accents-idn-and-short-link-slugs/</guid><description>&lt;p&gt;Accents belong in people names, page copy, titles, and destination websites. They do not belong in vanityURLs short-link slugs.&lt;/p&gt;
&lt;p&gt;That sounds stricter than the modern web really is. Browsers can show internationalized domain names. URLs can carry UTF-8 characters. Search engines can crawl paths with accents. People share links in many languages every day.&lt;/p&gt;
&lt;p&gt;The problem is not whether the internet can represent accents. It can. The problem is whether a short-link slug remains easy to type, review, compare, log, and defend when the same visible word can have more than one technical representation.&lt;/p&gt;</description></item></channel></rss>