Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
in html files sent as attachments, non-breaking-spaces (typed in with alt_space) are transformed #600
Originally by JDuch@fulladsl.be on 2015-05-12 22:09:09 +0200
Wheras Simplemail does send the same file containing non-breaking blanks undistorted, YAM2.10 Dev does ,
Steps to reproduce
1.Insert the line
Inserted line should still be the same:
"NBSstartÃ�Â�Ã�Â Ã�Â�Ã�Â Ã�Â�Ã�Â Ã�Â�Ã�Â Ã�Â�Ã�Â Ã�Â�Ã�Â Ã�Â�Ã�Â Ã�Â�Ã�Â Ã�Â�Ã�Â Ã�Â�Ã�Â Ã�Â�Ã�Â Ã�Â�Ã�Â Ã�Â�Ã�Â NBSstop" when looked at with CED (in CED the blanks in the preceding line appear as squares)
Originally on 2015-05-13 13:15:20 +0200
Are you sure you really attached a file containing NBSP characters (0xa0)?
I just created an example text file and verified that it really contains NBSP characters and for me YAM correctly encodes it as quoted-printable and perfectly restores the file byte by byte after having received it again.
Originally by JDuch@fulladsl.be on 2015-05-14 18:55:48 +0200
I used your file "as is" and inserted in a html nbsp_test.html file, attached both to a yam mail addressed to myself, and saved the results as
Those files are uploade in nbsp_.lha
Originally by JDuch@fulladsl.be on 2015-05-18 15:41:30 +0200
Maybe because i am using Yam in French locale & with charset ISO-8859-15 ?
I noted that the raw sent message refers tot ISO-8859-1 not ISO-8859-15
Originally on 2015-05-19 08:32:54 +0200
Replying to JosDuchIt:
You can define different charsets for GUI and for writing mails. Usually the GUI charset matches your system charset and YAM will warn you otherwise. The charset for writing mails also defaults to the system charset, but this one can be adjusted without any restrictions.
All text attachments (i.e. *.txt, *.html, mails, etc) will get the "write mail charset" included in the Content-Type header. Unfortunately it is impossible to correctly detect the encoding of a text file, because nobody can tell you wether a character beyond 0x80 exists because it is a german umlaut, or wether it exists because it introduces a UTF8 sequence. That's why YAM must rely on the user settings. No matter which charset you are using, YAM will never reencode the attached file. It will just declare the file to be encoded in the selected write charset.
But as you can see YAM definitely correctly attached the file without changing any on the NBSP characters:
So the final question is wether we really have a problem/bug in YAM here or whether it is just a matter of misunderstanding and possibly wrong handling of the original file by several text editors?
Originally on 2015-05-19 16:07:12 +0200
Originally by JDuch@fulladsl.be on 2015-05-19 18:17:57 +0200
Replying to tboeckel:
Originally by JDuch@fulladsl.be on 2015-05-19 18:29:26 +0200
I think i understand now
I changet it to ISO-8859-15 too
Originally by JDuch@fulladsl.be on 2015-05-19 20:01:52 +0200
All i can tell is that now the attaced files do show the new YAM/write USO-8859-15 charset
Originally on 2015-05-21 07:28:17 +0200
I really have to ask again: do we still have a problem here or is this issue invalid? You never provided your original files, but just the received version of my files. Reading to you latest answer makes me think that the issue is solved. It would be nice if you would either confirm this or provide all necessary information to let me reproduce the problems you are facing.
Originally by JDuch@fulladsl.be on 2015-05-21 15:13:47 +0200
We really still have the same problem. Even after synchronising all char settings to ISO-8859-15 i reported : "same result"
In fact the test is still simpler:
In my last reaction, i interpreted this text
in the following way:
& i expressed the hope that you (ticket #600) would fix it.
Of course i can not be sure to be complete about what you need to reproduce the problem, as far as i am concerned, i don't know how to avoid it in these circumstances:
In fact i just changed all these to ISO-8859-1 & redid the test describe in this last post1)2)3): same result:
Visually the files are changed& contain the line "startÂ Â Â Â Â Â Â Â stop"
I am very puzzled if i would be the only one experiencing this.