<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Encoding on Defender TD5</title><link>https://td5.390er.de/kategorien/encoding/</link><description>Recent content in Encoding on Defender TD5</description><generator>Hugo</generator><language>de</language><lastBuildDate>Sat, 25 Jul 2026 09:04:51 +0200</lastBuildDate><atom:link href="https://td5.390er.de/kategorien/encoding/index.xml" rel="self" type="application/rss+xml"/><item><title>Five Question Marks: An Encoding Bug and the Plausible Wrong Answer</title><link>https://td5.390er.de/claudebridge/five-question-marks-encoding-bug/</link><pubDate>Sat, 25 Jul 2026 09:04:51 +0200</pubDate><guid>https://td5.390er.de/claudebridge/five-question-marks-encoding-bug/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Someone types &lt;code&gt;äöüÄÖÜß&lt;/code&gt; into a text field in Netscape Navigator 3, running under System 7.6.1. What arrives on the server is &lt;code&gt;?????? &lt;/code&gt;. Seven characters in, seven question marks out. The explanation seems obvious — and the obvious explanation is wrong.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This is a short account of an encoding bug in &lt;a href="https://td5.390er.de/claudebridge/claudebridge-2-0-on-a-1996-macintosh/"&gt;ClaudeBridge 2.0&lt;/a&gt;, and of the detour taken while fixing it. The detour is the interesting part: the wrong fix looked like progress.&lt;/p&gt;</description></item></channel></rss>