<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <link>http://www.mathworks.com/matlabcentral/newsreader/view_thread/237663</link>
    <title>MATLAB Central Newsreader - 3Dginput</title>
    <description>Feed for thread: 3Dginput</description>
    <language>en-us</language>
    <copyright>&amp;copy;1994-2012 by MathWorks, Inc.</copyright>
    <webmaster>webmaster@mathworks.com</webmaster>
    <generator>MATLAB Central Newsreader</generator>
    <docs>http://blogs.law.harvard.edu/tech/rss</docs>
    <ttl>60</ttl>
    <image>
      <title>MathWorks</title>
      <url>http://www.mathworks.com/images/membrane_icon.gif</url>
    </image>
    <item>
      <pubDate>Thu, 16 Oct 2008 14:50:36 -0400</pubDate>
      <title>3Dginput</title>
      <link>http://www.mathworks.com/matlabcentral/newsreader/view_thread/237663#605707</link>
      <author>Mahdieh </author>
      <description>Hi all,&lt;br&gt;
&lt;br&gt;
where can I get the 3Dginput function that is mentioned in some of the posts??&lt;br&gt;
&lt;br&gt;
Thanks</description>
    </item>
    <item>
      <pubDate>Thu, 16 Oct 2008 16:26:13 -0400</pubDate>
      <title>Re: 3Dginput</title>
      <link>http://www.mathworks.com/matlabcentral/newsreader/view_thread/237663#605727</link>
      <author>Walter Roberson</author>
      <description>Mahdieh wrote:&lt;br&gt;
&lt;br&gt;
&amp;gt; where can I get the 3Dginput function that is mentioned in some of the posts??&lt;br&gt;
&lt;br&gt;
There is no function named 3Dginput, just ginput without the 3D.&lt;br&gt;
&lt;br&gt;
The reason you have seen 3Dginput is that Google Groups does MIME quoted-printable&lt;br&gt;
encoding of characters outside the range of printable US-ASCII. For example,&lt;br&gt;
capital A with the grave accent (`) is character number 192, which is hex C0,&lt;br&gt;
the encoding for which is equal-sign Cee zero . So if someone happens to post&lt;br&gt;
that character from google groups, you would see =C0 in the posting. But in&lt;br&gt;
order for this encoding scheme to work, there has to be a way to represent&lt;br&gt;
the equal-sign itself. equal-sign is character 61, hex 3D, so everywhere&lt;br&gt;
there was a -real- equal-sign in a posting, google groups replaces it with&lt;br&gt;
equal-sign three Dee, =3D so that it can then use the equal-sign everywhere&lt;br&gt;
else to signal an encoded character. If the original text happened to include&lt;br&gt;
equal-sign ginput as in coords=ginput(2); then google groups would encode&lt;br&gt;
the equal-sign as =3D, resulting in coords=3Dginput(2);&lt;br&gt;
&lt;br&gt;
It's a lousy encoding scheme for computer programming languages or &lt;br&gt;
mathematical equations, but it is an international standard. Really,&lt;br&gt;
though, Google Groups should not be using it for anything sent to Usenet,&lt;br&gt;
as Usenet standard predate the scheme... but trying to get Google to budge&lt;br&gt;
on anything like this is -nearly- hopeless.</description>
    </item>
  </channel>
</rss>

