<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Unicode on Red Leopard</title>
    <link>https://www.redleopard.com/tags/unicode/</link>
    <description>Recent content in Unicode on Red Leopard</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 28 Aug 2009 20:12:08 +0000</lastBuildDate>
    <atom:link href="https://www.redleopard.com/tags/unicode/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Unicode Backlash</title>
      <link>https://www.redleopard.com/2009/08/unicode-backlash/</link>
      <pubDate>Fri, 28 Aug 2009 20:12:08 +0000</pubDate>
      <guid>https://www.redleopard.com/2009/08/unicode-backlash/</guid>
      <description>&lt;p&gt;Yesterday, I stumbled upon a blog that made me laugh. The truth be told, I have a snarky side—my evil twin, if you will. I keep it in check. Mostly. Some of you who will understand. Some of you won’t. It’s a Gemini thing.&lt;/p&gt;
&lt;p&gt;My twin is fun but good luck putting it back in its cage. And believe me, for every dollar of fun you get, you’ll pay ten dollars in social disaster. Best to keep the twin in check.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Verdana Hates Pinyin</title>
      <link>https://www.redleopard.com/2009/08/verdana-hates-pinyin/</link>
      <pubDate>Sat, 08 Aug 2009 22:09:16 +0000</pubDate>
      <guid>https://www.redleopard.com/2009/08/verdana-hates-pinyin/</guid>
      <description>&lt;p&gt;I stumbled across an article on lostlaowai.com&lt;/p&gt;
&lt;p style=&#34;padding-left: 2em;&#34;&gt;
  &lt;a href=&#34;http://www.lostlaowai.com/survival-chinese&#34;&gt;www.lostlaowai.com/survival-chinese&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;which lead me to poke around the site a bit. At the above URL, I noticed that some of the combining diacritical marks (tone marks) used in writing pinyin were not rendering properly. I had not seen this problem before. It didn’t make sense.&lt;/p&gt;
&lt;p&gt;Things that don’t make sense bug me. And being something of a character geek, I couldn’t let it go. So I tried to reproduce the problem in a test example. I couldn’t. That’s when I discovered a quirky Mac OS X copy+paste issue. I sensed there was a problem but the truth was elusive. You can’t see that copy+paste changes the string characters unless you look at a binary dump of the file (which I did).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Character codes and encoding</title>
      <link>https://www.redleopard.com/2008/12/character-codes-and-encoding/</link>
      <pubDate>Thu, 11 Dec 2008 15:43:48 +0000</pubDate>
      <guid>https://www.redleopard.com/2008/12/character-codes-and-encoding/</guid>
      <description>&lt;p&gt;Character codes and encoding&lt;/p&gt;
&lt;p&gt;In the beginning, there was ASCII. (There were others, but we begin here with ASCII).&lt;/p&gt;
&lt;p&gt;7-bit ASCII in an 8-bit package. Using only the first seven bits of a byte, standard ASCII could not deal with diacritical marks (accents and funny dots in the vulgar vernacular). Therefore, the German word for later, später, would sometimes be transliterated into spaeter. I suspect this started in the days before computers when typewriters had only so many keys. You had to make do.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
