<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Agreed, UTF-8 would be preferable to ASCII.<div><br></div><div>Deborah Goldsmith</div><div>Apple Inc.</div><div><br><div><div>On Dec 27, 2012, at 10:28 AM, Mariano Absatz - el Baby <<a href="mailto:baby@baby.com.ar">baby@baby.com.ar</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Dec 13, 2012 at 10:23 PM, Paul Eggert <span dir="ltr"><<a href="mailto:eggert@cs.ucla.edu" target="_blank">eggert@cs.ucla.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Thanks for catching these problems. Two proposed patches<br>
are attached. The first fixes the problems by going back to ASCII.<br>
The second puts in a check for this problem, so that non-ASCII<br>
bytes like that don't slip into future releases. At some point<br>
we may well want to add non-ASCII characters, but they should<br>
be UTF-8 I expect. I've pushed these proposed patches into<br>
the unofficial experimental repository at github.<br>
</blockquote></div><br></div><div class="gmail_extra">FWIW, as a Spanish speaker (and possibly the author of the mail messages in Spanish which got converted into Latin-1 encoded comments) I vow for UTF-8 encoding rather than mutilation.<br>
</div><div class="gmail_extra"><br clear="all"><div>--<br>Mariano Absatz - El Baby<br><a href="http://www.clueless.com.ar/" target="_blank">www.clueless.com.ar</a><br><br></div>
</div></div>
</blockquote></div><br></div></body></html>