<?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: Scaling Ubiquity to 60+ Languages: We Need Your Help</title>
	<atom:link href="http://www.azarask.in/blog/post/scaling-ubiquity-to-60-languages-we-need-your-help/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.azarask.in/blog/post/scaling-ubiquity-to-60-languages-we-need-your-help/</link>
	<description>-- aza &#124; ɐzɐ --</description>
	<lastBuildDate>Wed, 08 Feb 2012 10:25:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Lavern Innocent</title>
		<link>http://www.azarask.in/blog/post/scaling-ubiquity-to-60-languages-we-need-your-help/comment-page-1/#comment-15237</link>
		<dc:creator>Lavern Innocent</dc:creator>
		<pubDate>Tue, 18 Oct 2011 23:19:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=366#comment-15237</guid>
		<description>I have found only two posts in your blog. this is really disappointing matter. i hope you will more active about your blog.</description>
		<content:encoded><![CDATA[<p>I have found only two posts in your blog. this is really disappointing matter. i hope you will more active about your blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: şahinnparadisegelenekselramazancoşkusu</title>
		<link>http://www.azarask.in/blog/post/scaling-ubiquity-to-60-languages-we-need-your-help/comment-page-1/#comment-14883</link>
		<dc:creator>şahinnparadisegelenekselramazancoşkusu</dc:creator>
		<pubDate>Tue, 30 Aug 2011 03:21:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=366#comment-14883</guid>
		<description>which has ever been carried out which approaches this magnitude.</description>
		<content:encoded><![CDATA[<p>which has ever been carried out which approaches this magnitude.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pellet mill manufacturer</title>
		<link>http://www.azarask.in/blog/post/scaling-ubiquity-to-60-languages-we-need-your-help/comment-page-1/#comment-14820</link>
		<dc:creator>pellet mill manufacturer</dc:creator>
		<pubDate>Tue, 23 Aug 2011 03:30:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=366#comment-14820</guid>
		<description>that I have an account on twitter, that sending a file to twitter requires turning it into an URL, that images can get uploaded to an image site like flickr or numerous others, and that I have an account on flickr.</description>
		<content:encoded><![CDATA[<p>that I have an account on twitter, that sending a file to twitter requires turning it into an URL, that images can get uploaded to an image site like flickr or numerous others, and that I have an account on flickr.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: basur</title>
		<link>http://www.azarask.in/blog/post/scaling-ubiquity-to-60-languages-we-need-your-help/comment-page-1/#comment-12125</link>
		<dc:creator>basur</dc:creator>
		<pubDate>Tue, 26 Oct 2010 08:54:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=366#comment-12125</guid>
		<description>However, as you described, nobody would want to write that way for Ubiquity. The “verbing” convention in English doesn’t follow English grammar rules any more than a similar convention would in Portuguese.</description>
		<content:encoded><![CDATA[<p>However, as you described, nobody would want to write that way for Ubiquity. The “verbing” convention in English doesn’t follow English grammar rules any more than a similar convention would in Portuguese.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sex</title>
		<link>http://www.azarask.in/blog/post/scaling-ubiquity-to-60-languages-we-need-your-help/comment-page-1/#comment-11372</link>
		<dc:creator>Sex</dc:creator>
		<pubDate>Tue, 07 Sep 2010 02:06:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=366#comment-11372</guid>
		<description>Letting the browser understand our native tongues is a bold and daunting task, but also tremendously exciting and rewarding one.</description>
		<content:encoded><![CDATA[<p>Letting the browser understand our native tongues is a bold and daunting task, but also tremendously exciting and rewarding one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: porno</title>
		<link>http://www.azarask.in/blog/post/scaling-ubiquity-to-60-languages-we-need-your-help/comment-page-1/#comment-11268</link>
		<dc:creator>porno</dc:creator>
		<pubDate>Sun, 05 Sep 2010 23:53:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=366#comment-11268</guid>
		<description>Letting the browser understand our native tongues is a bold and daunting task, but also tremendously exciting and rewarding one. ^^</description>
		<content:encoded><![CDATA[<p>Letting the browser understand our native tongues is a bold and daunting task, but also tremendously exciting and rewarding one. ^^</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zayıflama Lida Fx15 Ve Biber Hapı Zlfvbh</title>
		<link>http://www.azarask.in/blog/post/scaling-ubiquity-to-60-languages-we-need-your-help/comment-page-1/#comment-10271</link>
		<dc:creator>Zayıflama Lida Fx15 Ve Biber Hapı Zlfvbh</dc:creator>
		<pubDate>Wed, 21 Jul 2010 22:49:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=366#comment-10271</guid>
		<description>Thanks for the introduction Aza.

Letting the browser understand our native tongues is a bold and daunting task, but also tremendously exciting and rewarding one. ^^

I look forward to working with all of you on this bold initiative!</description>
		<content:encoded><![CDATA[<p>Thanks for the introduction Aza.</p>
<p>Letting the browser understand our native tongues is a bold and daunting task, but also tremendously exciting and rewarding one. ^^</p>
<p>I look forward to working with all of you on this bold initiative!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Kaiser</title>
		<link>http://www.azarask.in/blog/post/scaling-ubiquity-to-60-languages-we-need-your-help/comment-page-1/#comment-3975</link>
		<dc:creator>Robert Kaiser</dc:creator>
		<pubDate>Wed, 18 Feb 2009 18:50:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=366#comment-3975</guid>
		<description>The largest challenge I see for bringing such an interface to my native language German (which is probably among the more simple languages for that) is that the command form of a sentence having different order than the normal sentence, but I expect that users naturally will try to use either of them when typing in ubiquity.
While in English &quot;search Google for &#039;foo&#039;&quot; is both the command and a normal sentence (infinitive construction actually), in German &quot;Suche &#039;foo&#039; mit Google&quot; is the command form and &quot;&#039;foo&#039; mit Google suchen&quot; is the infinitive construction that probably as much people would enter naturally, not to speak of different prepositions they may chose instead of &quot;mit&quot; or a passive construct that may be as natural (&quot;Google nach &#039;foo&#039; durchsuchen&quot;).
The major challenge for German is that there are very often many ways to say the same thing and people will (try to) use either of those ways.</description>
		<content:encoded><![CDATA[<p>The largest challenge I see for bringing such an interface to my native language German (which is probably among the more simple languages for that) is that the command form of a sentence having different order than the normal sentence, but I expect that users naturally will try to use either of them when typing in ubiquity.<br />
While in English &#8220;search Google for &#8216;foo&#8217;&#8221; is both the command and a normal sentence (infinitive construction actually), in German &#8220;Suche &#8216;foo&#8217; mit Google&#8221; is the command form and &#8220;&#8216;foo&#8217; mit Google suchen&#8221; is the infinitive construction that probably as much people would enter naturally, not to speak of different prepositions they may chose instead of &#8220;mit&#8221; or a passive construct that may be as natural (&#8220;Google nach &#8216;foo&#8217; durchsuchen&#8221;).<br />
The major challenge for German is that there are very often many ways to say the same thing and people will (try to) use either of those ways.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://www.azarask.in/blog/post/scaling-ubiquity-to-60-languages-we-need-your-help/comment-page-1/#comment-3967</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Wed, 18 Feb 2009 02:02:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=366#comment-3967</guid>
		<description>UBIQUITY IS FREAKING AWESOME! Just felt I needed to tell someone that.</description>
		<content:encoded><![CDATA[<p>UBIQUITY IS FREAKING AWESOME! Just felt I needed to tell someone that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edgar Gonçalves</title>
		<link>http://www.azarask.in/blog/post/scaling-ubiquity-to-60-languages-we-need-your-help/comment-page-1/#comment-3966</link>
		<dc:creator>Edgar Gonçalves</dc:creator>
		<pubDate>Wed, 18 Feb 2009 01:17:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=366#comment-3966</guid>
		<description>Hmm, let me comment on some discussed items:
1. &quot;I don’t really see why Portuguese makes verbing any less natural than English does.&quot;
 - My point here is that most web applications have names that can resemble english verbs. &quot;Flickr screenshot&quot; can be seen as &quot;flickr a screenshot&quot;, and understood as &quot;send the screenshot to flickr&quot;. The same with &quot;Twitter #world&quot;, it can be mentally processed in english as &quot;Twitter (the current text selection) to the hashtag #world&quot;. (Sorry for making the same webapps as examples, but this way we avoid extra confusion). In Portuguese, the phonetic similarity of those names with grammatically viable verbs isn&#039;t that easy to make. For instance, all verbs (in their infinitive form) end up with &quot;ar&quot;, &quot;er&quot; or &quot;ir&quot;. Other terminations just seem odd, foreign-like, and don&#039;t integrate well with the language without starting to sound too technical. But other than that I know the sentence structure isn&#039;t correct in English, either. However, somehow it &quot;sounds&quot; right, and that&#039;s what my mind is looking for. (Note that my examples are only between English vs. Portuguese. I&#039;m sure there may be far more difficult comparisons to make with other languages.)

2. &quot;It *becomes* natural when you stop the inner grammarian in you from trying to “correct” it.&quot;
 - I strongly agree. This is what I mean with the teen shortened language. If it is practical, we become used to it, it becomes natural. I&#039;m ok with it, I even expect it!

3.  &quot;I’d rather tell Ubiquity what I want rather than how to get it&quot;
 - That&#039;s also ok for me. in fact, I already use Ubiquity that way with the &quot;map&quot; command, for instance. But for this to happen I think we have to cut on some command freedom. I have a command called buxfer-add that makes a transaction on Buxfer. It&#039;s syntax is &quot;BUXFER-ADD amount IN description&quot;. I realize now this is a bad syntax, and it&#039;s on my to-do to change it. A better way to achieve this is to make a command for the webapp &quot;buxfer&quot;, registered to the action &quot;spend&quot; (e.g.), with a numeric direct (i.e., unnamed) complement and a &quot;described as&quot; complement. This way Ubiquity could offer me the Buxfer option (or make it default, or some other choices I can&#039;t envision now), when I start typing &quot;spend&quot;. This could work well in portuguese, too: &quot;gasta 65€ em hotel&quot;. The translation work is, as a side-effect of removing syntax freedom, made easy for everyone. We only have to translate the &quot;doing&quot; action words, and the complement introduction prepositions (e.g. &quot;to&quot;, &quot;in&quot;, &quot;as&quot;, ...). Do you have other plans, does this idea fail and fall down miserably on something I&#039;m missing now?

4. &quot;I’ll gladly sacrifice as much of the “natural” part of language as I can get away with not typing, as long as Ubiquity can figure out what I mean.&quot;
 - Ahh, that for me is vital in Ubiquity. take away its autocomplete, and ubiquity looses a fan. But I&#039;m not sacrificing anything. One of the most interesting thing about the (current version of) Ubiquity for me is that it builds a description of the command we&#039;re going to perform, so that we can read it, and know we&#039;re not making a mistake. And this description comes up in natural language. So if I type &quot;shot #badw&quot; I can always read the sentence &quot;send the current secreenshot link to the hashtag #badwebdesign via Twitter&quot;. Long live preview messages for the bridge between shortcut madness and intelligible thinking flow!

That said, thank you for commenting my comment. One side-question. Are you Mitcho, Aza, an Ubiquity user/fan/developer? I&#039;m talking simply as a user/fan, just giving my 2 cents, and hoping to help moving forwards. And just to make it clear (my first comment may lacked that), I believe translating Ubiquity and get it closer to more and more people is not only noble, an interesting problem, but also a public service: everyone should be able to be more productive!</description>
		<content:encoded><![CDATA[<p>Hmm, let me comment on some discussed items:<br />
1. &#8220;I don’t really see why Portuguese makes verbing any less natural than English does.&#8221;<br />
 &#8211; My point here is that most web applications have names that can resemble english verbs. &#8220;Flickr screenshot&#8221; can be seen as &#8220;flickr a screenshot&#8221;, and understood as &#8220;send the screenshot to flickr&#8221;. The same with &#8220;Twitter #world&#8221;, it can be mentally processed in english as &#8220;Twitter (the current text selection) to the hashtag #world&#8221;. (Sorry for making the same webapps as examples, but this way we avoid extra confusion). In Portuguese, the phonetic similarity of those names with grammatically viable verbs isn&#8217;t that easy to make. For instance, all verbs (in their infinitive form) end up with &#8220;ar&#8221;, &#8220;er&#8221; or &#8220;ir&#8221;. Other terminations just seem odd, foreign-like, and don&#8217;t integrate well with the language without starting to sound too technical. But other than that I know the sentence structure isn&#8217;t correct in English, either. However, somehow it &#8220;sounds&#8221; right, and that&#8217;s what my mind is looking for. (Note that my examples are only between English vs. Portuguese. I&#8217;m sure there may be far more difficult comparisons to make with other languages.)</p>
<p>2. &#8220;It *becomes* natural when you stop the inner grammarian in you from trying to “correct” it.&#8221;<br />
 &#8211; I strongly agree. This is what I mean with the teen shortened language. If it is practical, we become used to it, it becomes natural. I&#8217;m ok with it, I even expect it!</p>
<p>3.  &#8220;I’d rather tell Ubiquity what I want rather than how to get it&#8221;<br />
 &#8211; That&#8217;s also ok for me. in fact, I already use Ubiquity that way with the &#8220;map&#8221; command, for instance. But for this to happen I think we have to cut on some command freedom. I have a command called buxfer-add that makes a transaction on Buxfer. It&#8217;s syntax is &#8220;BUXFER-ADD amount IN description&#8221;. I realize now this is a bad syntax, and it&#8217;s on my to-do to change it. A better way to achieve this is to make a command for the webapp &#8220;buxfer&#8221;, registered to the action &#8220;spend&#8221; (e.g.), with a numeric direct (i.e., unnamed) complement and a &#8220;described as&#8221; complement. This way Ubiquity could offer me the Buxfer option (or make it default, or some other choices I can&#8217;t envision now), when I start typing &#8220;spend&#8221;. This could work well in portuguese, too: &#8220;gasta 65€ em hotel&#8221;. The translation work is, as a side-effect of removing syntax freedom, made easy for everyone. We only have to translate the &#8220;doing&#8221; action words, and the complement introduction prepositions (e.g. &#8220;to&#8221;, &#8220;in&#8221;, &#8220;as&#8221;, &#8230;). Do you have other plans, does this idea fail and fall down miserably on something I&#8217;m missing now?</p>
<p>4. &#8220;I’ll gladly sacrifice as much of the “natural” part of language as I can get away with not typing, as long as Ubiquity can figure out what I mean.&#8221;<br />
 &#8211; Ahh, that for me is vital in Ubiquity. take away its autocomplete, and ubiquity looses a fan. But I&#8217;m not sacrificing anything. One of the most interesting thing about the (current version of) Ubiquity for me is that it builds a description of the command we&#8217;re going to perform, so that we can read it, and know we&#8217;re not making a mistake. And this description comes up in natural language. So if I type &#8220;shot #badw&#8221; I can always read the sentence &#8220;send the current secreenshot link to the hashtag #badwebdesign via Twitter&#8221;. Long live preview messages for the bridge between shortcut madness and intelligible thinking flow!</p>
<p>That said, thank you for commenting my comment. One side-question. Are you Mitcho, Aza, an Ubiquity user/fan/developer? I&#8217;m talking simply as a user/fan, just giving my 2 cents, and hoping to help moving forwards. And just to make it clear (my first comment may lacked that), I believe translating Ubiquity and get it closer to more and more people is not only noble, an interesting problem, but also a public service: everyone should be able to be more productive!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

