<feed xmlns='http://www.w3.org/2005/Atom'>
<title>guile-email/tests/multipart-email-with-a-8bit-encoding-and-non-utf8-charset-part, branch v0.2.0</title>
<subtitle>Guile email parser</subtitle>
<id>http://git.systemreboot.net/guile-email/atom?h=v0.2.0</id>
<link rel='self' href='http://git.systemreboot.net/guile-email/atom?h=v0.2.0'/>
<link rel='alternate' type='text/html' href='http://git.systemreboot.net/guile-email/'/>
<updated>2019-07-28T06:43:43+00:00</updated>
<entry>
<title>email: Support email with mixed encoding of characters.</title>
<updated>2019-07-28T06:43:43+00:00</updated>
<author>
<name>Arun Isaac</name>
</author>
<published>2019-07-25T20:23:22+00:00</published>
<link rel='alternate' type='text/html' href='http://git.systemreboot.net/guile-email/commit/?id=ac83c2a00c13702bc365cd0f3074239fa63d743f'/>
<id>urn:sha1:ac83c2a00c13702bc365cd0f3074239fa63d743f</id>
<content type='text'>
Prior to this, parse-email would accept email in the form of a
string. A string is constrained to use the same encoding for all its
characters whereas an email can have characters encoded using
different encoding schemes. Therefore, it is more correct that
parse-email deals with bytevectors instead of strings.

* email/utils.scm (read-bytes-till): New function.
* email/email.scm (body-&gt;mime-entities, email-&gt;headers+body,
decode-body): Deal with emails as bytevectors instead of strings.
(parse-mime-entity): Rename text argument to bv.
(parse-email, parse-email-body): Overload to handle input in the form
of a string or bytevector.
* doc/guile-email.texi (Parsing e-mail): Document overloading of
parse-email and parse-email-body.
* tests/email.scm ("handle truncated multipart message gracefully"):
Deal in bytevectors instead of strings.
("email with 8 bit encoding and non UTF-8 charset", "multipart email
with a 8 bit encoding and non UTF-8 charset part"): New tests.
* tests/email-with-8bit-encoding-and-non-utf8-charset,
tests/multipart-email-with-a-8bit-encoding-and-non-utf8-charset-part:
New files.

Reported-by: Jack Hill &lt;jackhill@jackhill.us&gt;
</content>
</entry>
</feed>
