YAM sending html files containing non-breaking blanks

I did note that html files sent as attachments with YAM do transform a string of nonbreaking blanks as some  containing strings
eg the line
"NBSstart             NBSstop"
when returned with mail addressed to me
appears as
"NBSstart             NBSstop" in CED the blanks here appear as a square
In IBrowse the line is presented as.
NBSstartÃfÂ,Ã, ÃfÂ,Ã, ÃfÂ,Ã, ÃfÂ,Ã, ÃfÂ,Ã, ÃfÂ,Ã, ÃfÂ,Ã, ÃfÂ,Ã, ÃfÂ,Ã, ÃfÂ,Ã, ÃfÂ,Ã, ÃfÂ,Ã, ÃfÂ,Ã, NBSstop

Of course i could use  , but in presenting math logic, just typing in nbsp with Alt_Blank is so much clearer.

Is this a YAM problem ?


Edit: it seems to be the case & was handed over to the YAM team as a "ticket"

@JosDuchIt

That's an encoding issue. the   is being converted into utf-8 at some point in the process.

Do you see it like this in code sent *to* you? Or when others recive code *from* you?

Try typing   rather than inserting the actual character?  

@broadblues
- of course inserting   will be sent properly
- i first noticed the problem when i did send a mail (with YAM) to my wife's PC. The attached file when downloaded & opened in a browser did show the transformed characters, not blanks
- checks i did :
1) sent the same file with simplemail to my wife's PC: here the attached file when downloaded is presented correctly in Chrome or Firefox
2) put the file on an USB stick & see what the PC makes of it. Chrome & Firefox do see the file correctly.
3) send the file from my wife's PC back to me (using hotmail)
The file can be seen correctly on my SAM

So i concluded it is a YAM problem & handed it over to the YAM team


http://yam.ch/ticket/600

@JosDuchIt

Looking at what YAM sends:

Quote:

That's perfectly formed quoted printable.

The problem is lthat your PC is decoding it as utf-8 even though it's clearly marked as ISO-8859-1 then as your html contains no encoding itself it displays the utf-8 characters as individual octets.

This is properly fixed by using   you *should not* include non ascii characters in an html document without setting the encoding.

@Broadblues
I understand what you are saying but do observe
- that the files sent to myself (yam as sender & receiver) when saved after reception are not viewed correctly on any browser on my system.
- when i do the same using simplemail the returned & saved files are exact copies of the original non-encoded ones. Simplemail is using base64 encoding though
Shouldn't yam decode properly when saving attachments? Is this a limitation of the "quoted-printable" encoding ?
Going to check if YAM has a settings for selecting the coding
edit: checked but did not find such setting
I noted though that whereas in YAM/settings/firststeps/charset is set to ISO-8859-15 the sent mail seems to use ISO-8859-1

----=_BOUNDARY.5efd37f068e04a7c.ed
Content-Type: text/plain; charset=ISO-8859-1;
name="nbsp_test.txt"
Content-Disposition: attachment;
filename="nbsp_test.txt";
size=17
Content-Transfer-Encoding: quoted-printable

start=A0=A0=A0=A0=A0=A0=A0=A0stop
--