email - WLMail displays messages correctly on screen, but prints  where there is =C2=A0 for some messages
2014-07
There are many questions online related to this. And I understand that =C2=A0
stands for non-breaking space when it appears within a mime part with type: Content-Type: text/html; charset=UTF-8
My user uses Windows Live Mail Version 2012 (Build 16.4.3508.0205) on Win 7. The problematic emails tend to have "MsoNormal" as a tell tale sign in message source.
- When the problematic mail is viewed on screen thru WLMail, no problems.
- When the problematic mail is printed on paper or to PDF, via WLMail, the  do appear.
- When the problematic mail is viewed in browser or printed via Gmail web interface, no problems.
"Use default encoding for all incoming messages" is NOT checked.
The problematic and good messages both have Content-Type: text/html; charset=UTF-8
.
The only difference I can see is that "MsoNormal" (tell-tale signs that an MS MUA was used by the other party) are present in the problematic messages.
Another clue is that the problematic messages tend to be those that have been authored in MS Outlook/WLMail, and then replied-to by a Gmail-web user, and then received by the WLMail user.
I'd like to use hunspell
form the command line to spell check a few text files.
The files are utf-8 encoded and contain some umlauts and other strange characters.
Some words show up like this
verlä�~_lich
instead of this
verläßlich
I told hunspell to read the files as utf-8 with -i utf-8
.
I tried to switch the encoding in gnome-terminal.
I tried it in xterm
and xterm -u8
. No success.
It is not a font issue because when I type the strange characters in the terminal they show up fine.
How can I get the strange characters to show up?
What is the command you are using to run hunspell?
hunspell −d de_DE -i UTF-8 filename
If no luck there,
SET UTF-8
...should go in your affix file. In your case your affix file is probably de_DE.aff.
The default if none is specified is
/usr/share/myspell/default.aff
Hope this helps!