<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 11"><meta name="Originator" content="Microsoft Word 11"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5Crhahn%5CLocal%20Settings%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml"><style>
<!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;
mso-font-alt:宋体;
mso-font-charset:134;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:3 135135232 16 0 262145 0;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;
mso-font-charset:134;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:3 135135232 16 0 262145 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:SimSun;}
h2
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-pagination:widow-orphan;
mso-outline-level:2;
font-size:18.0pt;
font-family:"Times New Roman";
font-weight:bold;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;
text-underline:single;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:SimSun;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.25in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style>
<p class="MsoNormal" style="text-align: center;" align="center"><span style="font-size: 11pt; font-family: Arial;">===========================================<br>
L O W L A N D S - L - 11 February 2009 - Volume 02<span style="color: rgb(102, 102, 102);"><br>
-------------------------------------------------------------------------<br>
Please set the encoding mode to Unicode (UTF-8).<br>
If viewing this in a web browser, please click on<br>
the html toggle at the bottom of the archived page <br>
and switch your browser's character encoding to Unicode.</span><br>
===========================================</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"><br>
From: R. F. Hahn <<a href="mailto:sassisch@yahoo.com" target="_blank">sassisch@yahoo.com</a>>
<br>
Subject: Technica<br>
<br>
Folks,<br>
<br>
Susan Smith of LINGUIST kindly investigated the character encoding matter. Please
find a copy of her message below.<br>
<br>
There is a possibility that all that needs to happen is for me to change the
encoding mode when I send (bundled) postings to the Listserv. I have specified Unicode
(UTF-8) for outgoing mail in Gmail, and this is what the "instructions" say:</span></p>
<h2 style="margin-left: 40px; color: rgb(0, 0, 153);">Sending with UTF-8 encoding</h2>
<p style="margin-left: 40px; color: rgb(0, 0, 153);" class="MsoNormal">Each time you send a message, Gmail automatically selects an
appropriate encoding for the language(s) in which you've composed your mail.
It's possible, however, that the recipient may not be able to properly view the
message you've sent. </p>
<p style="margin-left: 40px;"><span style="color: rgb(0, 0, 153);">If your contacts are having trouble viewing messages you've sent them, we
recommend using 'UTF-8' (Unicode) for all outgoing mail. UTF-8 is a standard
encoding that's accepted by many email clients. </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;">On the
basis of this and Susan's information, are any of
you able to come up with a solution, including simple instructions for
subscribers if required?<br>
<br>
Thanks for thinking about it and for your support in general.<br>
<br>
Reinhard/Ron<br>
Seattle, USA<br>
<br>
***<br>
<br>
Hi Ron,<br>
It seems that this problem is probably due to something outside our control -
we haven't made any changes to the character encoding we're using for Listserv,
and our other lists are fine. Apparently, the way a message is encoded
can be changed at several different points - when it is sent, when it passes
through different mail servers, and when it is received. Some mail
programs let you pick settings for both how you send your messages and how you
receive them. From what Luc said about how his character transfer
encoding setting was changing so frequently, it might be some kind of change
his email provider was making, maybe testing out some different formats.
He could try contacting them. He could also try changing the
settings in his mail client, if it has those options. Thunderbird lets me
pick what encoding I view a message with.<br>
<br>
As I've been reading up on this topic, the character transfer encoding controls
how various character encodings are translated, and if you don't specify what
you want, the mail server may apply some default setting. This can also
mix things up. I found this page which illustrates the complexity of the
issue: <a href="http://download.oracle.com/docs/cd/A97336_01/new.102/a86653/ch23.htm" target="_blank">http://download.oracle.com/docs/cd/A97336_01/new.102/a86653/ch23.htm</a><br>
<br>
The messages you've sent me from the list look fine in with Western ISO-8859-1
and UTF-8 encoding, but they get the same broken characters as I can see in the
web archives when I switch to Windows 1251 (the web archives look ok though
when I follow the directions you've put at the top, to view as html and switch
to UTF-8). Some of the other options I have, like Turkish ISO-8859-9,
also result in broken characters. How do messages that people post
interact with this gmail address, if at all? It looks like they are just
posting directly to the list, like normal, but I wanted to check. The encoding
problems in the archives must be a result of the encoding with which people are
sending them, or something that is happening en-route, but they don't seem to
be related to Listerv, as I said earlier. Maybe you could ask your
subscribers to check all their mail settings and ensure that they are sending
(and reading) messages in UTF-8?<br>
<br>
I'm sorry I can't be more helpful - this character encoding problem is quite
hard to pin down, it turns out, because of all the many points along an email's
path where it can be affected. If I figure anything else out about this,
though, I'll let you know.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"><br>
Best,<br>
Susan</span></p>
<p style="margin: 0in 0in 0.0001pt;"><span style="font-size: 11pt; font-family: Arial;"> </span></p>
•
<p>
==============================END===================================
<p>
* Please submit postings to lowlands-l@listserv.linguistlist.org.
<p>
* Postings will be displayed unedited in digest form.
<p>
* Please display only the relevant parts of quotes in your replies.
<p>
* Commands for automated functions (including "signoff lowlands-l")
<p>
are to be sent to listserv@listserv.linguistlist.org or at
<p>
http://linguistlist.org/subscribing/sub-lowlands-l.html.
<p>
*********************************************************************