<?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: Comic Update: The HTML5 Suggestion Box</title>
	<atom:link href="http://cssquirrel.com/blog/2009/07/20/comic-update-the-html5-suggestion-box/feed/" rel="self" type="application/rss+xml" />
	<link>http://cssquirrel.com/blog/2009/07/20/comic-update-the-html5-suggestion-box/</link>
	<description>opinions and news on web design</description>
	<lastBuildDate>Thu, 17 May 2012 05:41:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dave Vogt</title>
		<link>http://cssquirrel.com/blog/2009/07/20/comic-update-the-html5-suggestion-box/comment-page-1/#comment-27003</link>
		<dc:creator>Dave Vogt</dc:creator>
		<pubDate>Wed, 09 Sep 2009 14:53:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=385#comment-27003</guid>
		<description>Sorry for commenting on something so old.

140 isn&#039;t properly a character count. We regard it as such because as speakers of English we stick to the ascii range. Twitter allows 140 bytes per tweet. You&#039;d be limited to slightly fewer characters if you&#039;re using multibyte characters (twitter expects utf-8), although at that rate you&#039;d still be able to manage Amelia Bedelia in kanji, if not War and Peace.</description>
		<content:encoded><![CDATA[<p>Sorry for commenting on something so old.</p>
<p>140 isn&#8217;t properly a character count. We regard it as such because as speakers of English we stick to the ascii range. Twitter allows 140 bytes per tweet. You&#8217;d be limited to slightly fewer characters if you&#8217;re using multibyte characters (twitter expects utf-8), although at that rate you&#8217;d still be able to manage Amelia Bedelia in kanji, if not War and Peace.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: msikma</title>
		<link>http://cssquirrel.com/blog/2009/07/20/comic-update-the-html5-suggestion-box/comment-page-1/#comment-26571</link>
		<dc:creator>msikma</dc:creator>
		<pubDate>Wed, 22 Jul 2009 17:22:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=385#comment-26571</guid>
		<description>Nope. Twitter limits you to 140 characters, regardless of which they are or how many bytes it takes to encode them.</description>
		<content:encoded><![CDATA[<p>Nope. Twitter limits you to 140 characters, regardless of which they are or how many bytes it takes to encode them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Kozakewich</title>
		<link>http://cssquirrel.com/blog/2009/07/20/comic-update-the-html5-suggestion-box/comment-page-1/#comment-26562</link>
		<dc:creator>Michael Kozakewich</dc:creator>
		<pubDate>Tue, 21 Jul 2009 15:14:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=385#comment-26562</guid>
		<description>Don&#039;t japanese/chinese characters take two bytes each? If so, would they be limited to 80 characters?

I took a couple looks at the mailing list, and one thing that immediately comes to mind is, &quot;Wow, they need Google Wave.&quot; Everyone is copy/pasting everyone else&#039;s emails in full, and then inserting their own annotations.
It would also be good if they could thread the list. It seems it&#039;s only one email at a time. I&#039;ll see if there are options.
At this moment in time, I&#039;ve got other things to do.</description>
		<content:encoded><![CDATA[<p>Don&#8217;t japanese/chinese characters take two bytes each? If so, would they be limited to 80 characters?</p>
<p>I took a couple looks at the mailing list, and one thing that immediately comes to mind is, &#8220;Wow, they need Google Wave.&#8221; Everyone is copy/pasting everyone else&#8217;s emails in full, and then inserting their own annotations.<br />
It would also be good if they could thread the list. It seems it&#8217;s only one email at a time. I&#8217;ll see if there are options.<br />
At this moment in time, I&#8217;ve got other things to do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: msikma</title>
		<link>http://cssquirrel.com/blog/2009/07/20/comic-update-the-html5-suggestion-box/comment-page-1/#comment-26553</link>
		<dc:creator>msikma</dc:creator>
		<pubDate>Mon, 20 Jul 2009 21:22:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=385#comment-26553</guid>
		<description>I have little to add to what has been said on the W3C, seen as how my experience with their official channels is limited to one suggestion sent to one of the CSS 3 editors (which was rejected).

The issue of Twitter&#039;s 140-character limit being unfair to some languages is an interesting one too. Maybe we should do some research on the subject by making a number of &quot;standard&quot; tweets in English and asking people to translate them without regard to character limits.

Japanese is entered by activating an IME (Input Method Editor) and then just typing Latin letters; they get substituted for kanji semi-automatically if desired. If I wanted to type the word for bird (鳥), I&#039;d hit the hotkey for activating Japanese input, then type &quot;tori&quot; (とり), then press space to see the menu of matching kanji (鳥 is the most common, so it&#039;s the first).</description>
		<content:encoded><![CDATA[<p>I have little to add to what has been said on the W3C, seen as how my experience with their official channels is limited to one suggestion sent to one of the CSS 3 editors (which was rejected).</p>
<p>The issue of Twitter&#8217;s 140-character limit being unfair to some languages is an interesting one too. Maybe we should do some research on the subject by making a number of &#8220;standard&#8221; tweets in English and asking people to translate them without regard to character limits.</p>
<p>Japanese is entered by activating an IME (Input Method Editor) and then just typing Latin letters; they get substituted for kanji semi-automatically if desired. If I wanted to type the word for bird (鳥), I&#8217;d hit the hotkey for activating Japanese input, then type &#8220;tori&#8221; (とり), then press space to see the menu of matching kanji (鳥 is the most common, so it&#8217;s the first).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Dowdell</title>
		<link>http://cssquirrel.com/blog/2009/07/20/comic-update-the-html5-suggestion-box/comment-page-1/#comment-26552</link>
		<dc:creator>John Dowdell</dc:creator>
		<pubDate>Mon, 20 Jul 2009 20:41:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=385#comment-26552</guid>
		<description>(please &#039;scuse me for veering so radically off-topic.... ;-)

You&#039;re right about the kanji being available in Japanese tweets, but inflections and prepositions are handled by hiragana, and foreign words handled by katakana, and that&#039;s where the size-advantage is lost.

Korean is interesting, because each character is an entire syllable... I haven&#039;t benchmarked, but Chinese is the most compact I&#039;ve seen, Korean may be second-most compact, and Japanese and English may be at rough parity, depending on the level of informality and abbreviation of the speech.

Meanwhile, pity the Germans.... ;-)</description>
		<content:encoded><![CDATA[<p>(please &#8216;scuse me for veering so radically off-topic&#8230;. ;-)</p>
<p>You&#8217;re right about the kanji being available in Japanese tweets, but inflections and prepositions are handled by hiragana, and foreign words handled by katakana, and that&#8217;s where the size-advantage is lost.</p>
<p>Korean is interesting, because each character is an entire syllable&#8230; I haven&#8217;t benchmarked, but Chinese is the most compact I&#8217;ve seen, Korean may be second-most compact, and Japanese and English may be at rough parity, depending on the level of informality and abbreviation of the speech.</p>
<p>Meanwhile, pity the Germans&#8230;. ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kyle Weems</title>
		<link>http://cssquirrel.com/blog/2009/07/20/comic-update-the-html5-suggestion-box/comment-page-1/#comment-26551</link>
		<dc:creator>Kyle Weems</dc:creator>
		<pubDate>Mon, 20 Jul 2009 20:36:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=385#comment-26551</guid>
		<description>@JD - My understanding is Japanese also includes kanji, and as a result, allows for 140 words under such a circumstance. I have no clue, I&#039;ll admit, as to whether kanji sees much use by the Japanese in desktop computer situations (I can&#039;t personally imagine how much of a pain enabling the ability to type all those characters is).</description>
		<content:encoded><![CDATA[<p>@JD &#8211; My understanding is Japanese also includes kanji, and as a result, allows for 140 words under such a circumstance. I have no clue, I&#8217;ll admit, as to whether kanji sees much use by the Japanese in desktop computer situations (I can&#8217;t personally imagine how much of a pain enabling the ability to type all those characters is).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Dowdell</title>
		<link>http://cssquirrel.com/blog/2009/07/20/comic-update-the-html5-suggestion-box/comment-page-1/#comment-26550</link>
		<dc:creator>John Dowdell</dc:creator>
		<pubDate>Mon, 20 Jul 2009 20:33:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=385#comment-26550</guid>
		<description>Japanese tweets aren&#039;t particularly compact. Chinese tweets, though, can convey an amazing amount of information... 140 *words*, essentially.

jd/adobe</description>
		<content:encoded><![CDATA[<p>Japanese tweets aren&#8217;t particularly compact. Chinese tweets, though, can convey an amazing amount of information&#8230; 140 *words*, essentially.</p>
<p>jd/adobe</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mattur</title>
		<link>http://cssquirrel.com/blog/2009/07/20/comic-update-the-html5-suggestion-box/comment-page-1/#comment-26549</link>
		<dc:creator>mattur</dc:creator>
		<pubDate>Mon, 20 Jul 2009 20:27:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=385#comment-26549</guid>
		<description>You left out the bit where Ian Hickson of the HTML-WG replied to an email from the chair of the PFWG, and the chair ignored his email, then bizarrely accused Hixie of ignoring her email, then when pressed, finally replied saying the PFWG don&#039;t reply to emails from individuals. Teh funnies!

Self-appointed &#039;concerned&#039; individuals: &quot;We PROPOSE more collaboration between the WAI and the HTML-WG&quot;

Hixie and Ruby: &quot;How about, as a start, um, replying to our emails?&quot;

Self-appointed &#039;concerned&#039; individuals: &quot;How dare you! Must you be so arrogant?&quot;

I don&#039;t entirely disagree with the (admittedly rather egotastic) proposal. I do think it was sent to the wrong working group.</description>
		<content:encoded><![CDATA[<p>You left out the bit where Ian Hickson of the HTML-WG replied to an email from the chair of the PFWG, and the chair ignored his email, then bizarrely accused Hixie of ignoring her email, then when pressed, finally replied saying the PFWG don&#8217;t reply to emails from individuals. Teh funnies!</p>
<p>Self-appointed &#8216;concerned&#8217; individuals: &#8220;We PROPOSE more collaboration between the WAI and the HTML-WG&#8221;</p>
<p>Hixie and Ruby: &#8220;How about, as a start, um, replying to our emails?&#8221;</p>
<p>Self-appointed &#8216;concerned&#8217; individuals: &#8220;How dare you! Must you be so arrogant?&#8221;</p>
<p>I don&#8217;t entirely disagree with the (admittedly rather egotastic) proposal. I do think it was sent to the wrong working group.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Foliot</title>
		<link>http://cssquirrel.com/blog/2009/07/20/comic-update-the-html5-suggestion-box/comment-page-1/#comment-26547</link>
		<dc:creator>John Foliot</dc:creator>
		<pubDate>Mon, 20 Jul 2009 18:52:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=385#comment-26547</guid>
		<description>@Bruce: Funny Bruce, I *did* sit in my bedroom for near an hour composing a response for Sam, who apparently does not take the Formal Proposal seriously enough to address the content - instead he&#039;s &quot;disappointed&quot; (welcome to the club Sam).  If enough people believe that the request is legitimate and worth implementing, please say so by emailing the public-html mailing list (public-html-request@w3.org) or if you are unable to do that, feel free to forward your comments to me and i will pass them on.

@Adrienne: A few points.  

1) To my mind (and others) the W3C *is* the professional body you seek - it is unfortunate that WHAT WG continues to run in parallel, but there you have it.  Within the W3C there are numerous groups that focus on a specific area of interest/expertise (accessibility, web fonts, RDFa, etc.), and if you feel you have contributions to make to any of those groups, please do so.  By policy, most of these groups have &#039;official&#039; channels for commentary - for example the web accessibility initiative has the Protocols and Formats Working Group: http://www.w3.org/WAI/PF/Overview.html who have just announced the creation of a Task Force to look at the very real issues surrounding the accessibility of the canvas element: http://lists.w3.org/Archives/Public/public-html/2009Jul/0562.html The real issue however is that the current editor does not feel bound to take the contributions of these expert groups with any more &#039;weight&#039; than the average Joe off the street (with no offense to the Joes out there who may very well be qualified to comment on any particular subject)

2) Communication via listserve - yes, it might seem clunky in the world of twitter and on-line instant chat, but how else can you accommodate a diverse and global body of contributors?  Many of the active participants that I communicate with (in the area of web accessibility) live in such regions as Norway, UK, Germany and Australia - all in different time-zones.  Listserves provide threaded, search-able archives that allow for such asynchronous discussion: if you have a better means to ensure inclusiveness then speak up; what I (and others) abhor however is the current practice that the WHAT WG authors group uses, which is IRC - it has it&#039;s uses, but is hardly an inclusive environment - unless of course you are a vampire and need no sleep .</description>
		<content:encoded><![CDATA[<p>@Bruce: Funny Bruce, I *did* sit in my bedroom for near an hour composing a response for Sam, who apparently does not take the Formal Proposal seriously enough to address the content &#8211; instead he&#8217;s &#8220;disappointed&#8221; (welcome to the club Sam).  If enough people believe that the request is legitimate and worth implementing, please say so by emailing the public-html mailing list (public-html-request@w3.org) or if you are unable to do that, feel free to forward your comments to me and i will pass them on.</p>
<p>@Adrienne: A few points.  </p>
<p>1) To my mind (and others) the W3C *is* the professional body you seek &#8211; it is unfortunate that WHAT WG continues to run in parallel, but there you have it.  Within the W3C there are numerous groups that focus on a specific area of interest/expertise (accessibility, web fonts, RDFa, etc.), and if you feel you have contributions to make to any of those groups, please do so.  By policy, most of these groups have &#8216;official&#8217; channels for commentary &#8211; for example the web accessibility initiative has the Protocols and Formats Working Group: <a href="http://www.w3.org/WAI/PF/Overview.html" rel="nofollow">http://www.w3.org/WAI/PF/Overview.html</a> who have just announced the creation of a Task Force to look at the very real issues surrounding the accessibility of the canvas element: <a href="http://lists.w3.org/Archives/Public/public-html/2009Jul/0562.html" rel="nofollow">http://lists.w3.org/Archives/Public/public-html/2009Jul/0562.html</a> The real issue however is that the current editor does not feel bound to take the contributions of these expert groups with any more &#8216;weight&#8217; than the average Joe off the street (with no offense to the Joes out there who may very well be qualified to comment on any particular subject)</p>
<p>2) Communication via listserve &#8211; yes, it might seem clunky in the world of twitter and on-line instant chat, but how else can you accommodate a diverse and global body of contributors?  Many of the active participants that I communicate with (in the area of web accessibility) live in such regions as Norway, UK, Germany and Australia &#8211; all in different time-zones.  Listserves provide threaded, search-able archives that allow for such asynchronous discussion: if you have a better means to ensure inclusiveness then speak up; what I (and others) abhor however is the current practice that the WHAT WG authors group uses, which is IRC &#8211; it has it&#8217;s uses, but is hardly an inclusive environment &#8211; unless of course you are a vampire and need no sleep .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrienne Adams</title>
		<link>http://cssquirrel.com/blog/2009/07/20/comic-update-the-html5-suggestion-box/comment-page-1/#comment-26546</link>
		<dc:creator>Adrienne Adams</dc:creator>
		<pubDate>Mon, 20 Jul 2009 18:16:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.cssquirrel.com/?p=385#comment-26546</guid>
		<description>Getting involved in writing standards requires more time, I think, than most working professionals can afford to spend. From my rather sporadic attention to the HTML5 issue I&#039;ve noticed what seems to me to be a fatal flaw in the standards-creation process: the lack of true professional organizations for web designers/developers, through which we can participate in the process.

If one looks at the history of other standards bodies, e.g. ANSI (founded by engineering societies) and MARC 21 (created by librarians), professional organizations played an important role in the process of creating standards. It seems that with web standards, the most influential voices are those of the browser manufacturers, who have the resources and motivation to control the standards creation process. 

What if web designers had an organization like the AIGA? It might be harder then for those who currently control the working group to shrug off the proposals of individuals, if those individuals could leverage the clout &amp; prestige of a professional organization. Such an organization could also devote resources to streamlining the avenues through which its members could participate in and influence the standards-creation process. The current system is (I think) needlessly bloated,  overloaded with numerous and confusing entry points (&quot;HTML5 WG? Or the WHAT WG?&quot; Incubator groups?) and hampered by an archaic communication system (an email &lt;em&gt;listserv,&lt;/em&gt; for godssake) and arcane language.

I think we&#039;re reaching a crisis point with web standards. If this disconnect between the standards bodies and the actual users of web standards continues, we might see more designers/developers abandoning the headache altogether and relying upon proprietary (but more predictable &amp; stable) platforms upon which to work.</description>
		<content:encoded><![CDATA[<p>Getting involved in writing standards requires more time, I think, than most working professionals can afford to spend. From my rather sporadic attention to the HTML5 issue I&#8217;ve noticed what seems to me to be a fatal flaw in the standards-creation process: the lack of true professional organizations for web designers/developers, through which we can participate in the process.</p>
<p>If one looks at the history of other standards bodies, e.g. ANSI (founded by engineering societies) and MARC 21 (created by librarians), professional organizations played an important role in the process of creating standards. It seems that with web standards, the most influential voices are those of the browser manufacturers, who have the resources and motivation to control the standards creation process. </p>
<p>What if web designers had an organization like the AIGA? It might be harder then for those who currently control the working group to shrug off the proposals of individuals, if those individuals could leverage the clout &amp; prestige of a professional organization. Such an organization could also devote resources to streamlining the avenues through which its members could participate in and influence the standards-creation process. The current system is (I think) needlessly bloated,  overloaded with numerous and confusing entry points (&#8220;HTML5 WG? Or the WHAT WG?&#8221; Incubator groups?) and hampered by an archaic communication system (an email <em>listserv,</em> for godssake) and arcane language.</p>
<p>I think we&#8217;re reaching a crisis point with web standards. If this disconnect between the standards bodies and the actual users of web standards continues, we might see more designers/developers abandoning the headache altogether and relying upon proprietary (but more predictable &amp; stable) platforms upon which to work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

