<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
> <channel><title>Comments on: Unicode (used creatively) makes your Tweets go further</title> <atom:link href="http://www.globalbydesign.com/blog/2009/08/20/unicode-tweets/feed/" rel="self" type="application/rss+xml" /><link>http://www.globalbydesign.com/blog/2009/08/20/unicode-tweets/</link> <description>Adventures in web and mobile globalization</description> <lastBuildDate>Tue, 07 Feb 2012 18:38:36 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: F Wolff</title><link>http://www.globalbydesign.com/blog/2009/08/20/unicode-tweets/comment-page-1/#comment-31260</link> <dc:creator>F Wolff</dc:creator> <pubDate>Fri, 21 Aug 2009 08:31:16 +0000</pubDate> <guid
isPermaLink="false">http://www.globalbydesign.com/?p=2056#comment-31260</guid> <description>I guess this fits in with the idea that twitter is really only for people to say something, but not for anybody to actually read anything. Let&#039;s think about accessibility and what a screen reader will do with this.  I&#039;m wondering if inserting an RTL character in between will cause a surprise somewhere.
Of course, whereas all-ASCII messages can be encoded quite small in cell phones, anything with this character repertoir will actually end up being substantially longer, apart from device support in terms of fonts likely to be a worse than on a desktop.</description> <content:encoded><![CDATA[<p>I guess this fits in with the idea that twitter is really only for people to say something, but not for anybody to actually read anything. Let&#8217;s think about accessibility and what a screen reader will do with this.  I&#8217;m wondering if inserting an RTL character in between will cause a surprise somewhere.</p><p>Of course, whereas all-ASCII messages can be encoded quite small in cell phones, anything with this character repertoir will actually end up being substantially longer, apart from device support in terms of fonts likely to be a worse than on a desktop.</p> ]]></content:encoded> </item> <item><title>By: Neij</title><link>http://www.globalbydesign.com/blog/2009/08/20/unicode-tweets/comment-page-1/#comment-31220</link> <dc:creator>Neij</dc:creator> <pubDate>Thu, 20 Aug 2009 08:17:33 +0000</pubDate> <guid
isPermaLink="false">http://www.globalbydesign.com/?p=2056#comment-31220</guid> <description>Nice idea, but wouldn&#039;t this totally mess up Twitter&#039;s search function (and related useful stuff such as Twitterfall)? On the other hand I suppose using ad hoc abbrvtns would have the same effect...</description> <content:encoded><![CDATA[<p>Nice idea, but wouldn&#8217;t this totally mess up Twitter&#8217;s search function (and related useful stuff such as Twitterfall)? On the other hand I suppose using ad hoc abbrvtns would have the same effect&#8230;</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: basic (User agent is rejected)
Database Caching 1/6 queries in 0.004 seconds using disk: basic
Object Caching 444/445 objects using disk: basic

Served from: www.globalbydesign.com @ 2012-02-08 22:47:24 -->
