On 9/9/06, <b class="gmail_sendername">Marcin 'Qrczak' Kowalczyk</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
"Paul Prescod" <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> writes:<br><br>> text data cannot even be reliably processed on the desktop on which<br>> it was created (yes, even on Unix: look back in this thread).
<br><br>Where?</blockquote><div><br><a href="http://mail.python.org/pipermail/python-3000/2006-September/003492.html">http://mail.python.org/pipermail/python-3000/2006-September/003492.html</a> <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
New communication protocols and newly created file formats designed<br>for interchange will either specify the text encoding in metadata<br>(if files are expected to be edited by hand and it's still a near future),<br>or use UTF-8 exclusively. Simple file formats expected to be used only
<br>locally will continue to have the encoding implicit.<br><br>The system encoding of Unix boxes will more commonly be UTF-8 as time<br>passes.</blockquote><div><br>Okay, thanks for your view of where things are going. I think that it is clear that UTF-8 will replace iso8859-* on Unix over the next few years. It isn't as clear if it (or any other global encoding) will replace EUC.
<br><br> Paul Prescod<br><br></div></div>