<div class="gmail_quote">On Wed, Jan 28, 2009 at 2:35 AM, Křištof Želechovski <span dir="ltr"><<a href="mailto:kkz@mimuw.edu.pl">kkz@mimuw.edu.pl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="PL" link="blue" vlink="blue">
<div>
<div class="Ih2E3d"><p style="margin-left:35.4pt"><font size="2" face="Tahoma"><span lang="EN-US" style="font-size:10.0pt;font-family:Tahoma"><b><span style="font-weight:bold"><span class="Apple-style-span" style="color: rgb(0, 0, 128); font-family: Arial; font-weight: normal;"><span class="Apple-style-span" style="color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-size: 16px; ">No, the _original_ use
was to turn it on on fields where it would otherwise have been on.</span><br></span></span></b></span></font></p></div><div><div><div class="Ih2E3d">
<p><font size="2" color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy"> </span></font></p>
</div><p><font size="2" color="navy" face="Arial"><span lang="EN-US" style="font-size:10.0pt;font-family:Arial;color:navy">I do not understand. If spell
checking would be on, why turn it on explicitly?</span></font></p></div></div></div></div></blockquote><div>I mistyped. The last word should have been "off".</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="PL" link="blue" vlink="blue"><div><div><div><div class="Ih2E3d">
</div><p><font size="2" color="navy" face="Arial"><span lang="EN-US" style="font-size:10.0pt;font-family:Arial;color:navy">If the control is not
expected to contain a private language, it should be subject to spell checking.</span></font></p></div></div></div></div></blockquote><div>This thread has already had multiple examples of cases where this is untrue. Spelling quizzes, address fields, etc. And even if it were true, it's not the way browsers behave today (e.g. Firefox does not spellcheck single-line fields, precisely to avoid a lot of cases like this), and changing those defaults to be something non-annoying, using complex heuristics, is significantly harder (in terms of your time/money cost below) compared to supporting the attribute.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div lang="PL" link="blue" vlink="blue"><div><div><div><p><font size="2" color="navy" face="Arial"><span lang="EN-US" style="font-size:10.0pt;font-family:Arial;color:navy"></span></font></p>
</div><div class="Ih2E3d">
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div link="blue" vlink="blue">
<div>
<p style="margin-left:35.4pt"><font size="2" color="navy" face="Arial"><span lang="EN-US" style="font-size:10.0pt;font-family:Arial;color:navy">
Avoiding an additional attribute is a gain,</span></font></p>
</div>
</div>
</blockquote>
</div><div>
<p style="margin-left:35.4pt"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">Why? </span></font></p>
<p><font size="2" color="navy" face="Arial"><span lang="EN-US" style="font-size:10.0pt;font-family:Arial;color:navy">Because adding an
additional attribute costs time and money.</span></font></p></div></div></div></div></blockquote><div>To whom? What tradeoff are you making? Keying spellchecking off language support costs engineering time too, for the UA. And for a web author. All changes have costs. The point here seems like a vague principle rather than a specific application. </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div lang="PL" link="blue" vlink="blue"><div><div><div class="Ih2E3d"><blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div link="blue" vlink="blue"><div>
</div>
</div>
</blockquote>
</div><div><div class="Ih2E3d">
<p style="margin-left:35.4pt"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">Which no one will ever
use, because users aren't going to take the trouble to declare such a thing
when human recipients can just _read the text_. After all, WE have
built-in language detectors in our heads. </span></font></p>
</div><p><font size="2" color="navy" face="Arial"><span lang="EN-US" style="font-size:10.0pt;font-family:Arial;color:navy">We disagree here but
further discussion is void unless you have the resources necessary to perform
an investigation of the subject.</span></font></p></div></div></div></div></blockquote><div>If you need data to prove that people will not make the effort to explicitly tell recipients what languages their messages are in, I offer you the entire history of written communication, where people don't say "By the way this is in English!" at the top of each letter. </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div lang="PL" link="blue" vlink="blue"><div><div><div><div class="Ih2E3d">
</div><p><font size="2" color="navy" face="Arial"><span lang="EN-US" style="font-size:10.0pt;font-family:Arial;color:navy">Users entering text in a
foreign language cause trouble to the forum moderators who have to discipline
them. Thus, the software could accommodate to the needs of the moderator, so
that the poster gets warned before posting, not admonished afterwards. This is
more convenient and less work for everyone. Providing an indication what
language is recommended by forum users is good, because most users would take
that into account (for fear of getting plonked, if not for good manners).</span></font></p></div></div></div></div></blockquote><div>How is this relevant to a discussion about spellchecking? If you want UA-based language detection facilities that are, say, accessible from JS, that may be a reasonable request, but like much of this discussion, it seems tangential.</div>
<div><br></div><div>PK</div></div>