diff options
Diffstat (limited to 'doc/guile-email.texi')
-rw-r--r-- | doc/guile-email.texi | 34 |
1 files changed, 27 insertions, 7 deletions
diff --git a/doc/guile-email.texi b/doc/guile-email.texi index b606021..70a4e28 100644 --- a/doc/guile-email.texi +++ b/doc/guile-email.texi @@ -53,22 +53,42 @@ RF2047 and RFC2049. @node Parsing e-mail @chapter Parsing e-mail -@deffn {Scheme Procedure} parse-email email -Parse string @var{email} and return result as an <email> record. -@end deffn +@deftypefn {Scheme Procedure} parse-email (bytevector @var{email}) +@deftypefnx {Scheme Procedure} parse-email (string @var{email}) +Parse bytevector @var{email} and return result as an @code{<email>} +record. + +Parse string @var{email} and return result as an @code{<email>} +record. +@end deftypefn @deffn {Scheme Procedure} parse-email-headers headers Parse string @var{headers} as email headers and return an association list of header keys and values. @end deffn -@deffn {Scheme Procedure} parse-email-body headers body -Parse @var{body} as email body where @var{headers} is an association -list of header keys and values as returned by +@deftypefn {Scheme Procedure} parse-email-body (string @var{headers}) (bytevector @var{body}) +@deftypefnx {Scheme Procedure} parse-email-body (string @var{headers}) (string @var{body}) +Parse bytevector @var{body} as email body where @var{headers} is an +association list of header keys and values as returned by @code{parse-email-headers}. Return a list of <mime-entity> records if the body is a multipart message. Else, return a single <mime-entity> record. -@end deffn + +Parse string @var{body} as email body where @var{headers} is an +association list of header keys and values as returned by +@code{parse-email-headers}. Return a list of <mime-entity> records if +the body is a multipart message. Else, return a single <mime-entity> +record. +@end deftypefn + +Note that while an email can have characters encoded using different +schemes, a string is constrained to have all characters encoded using +the same scheme. Therefore, passing a string to @code{parse-email} or +@code{parse-email-body} will not always produce correct results. Hence, +this variant of @code{parse-email} and @code{parse-email-body} will be +deprecated in the future. This variant is only provided in the interest +of backward compatibility. @node Encoding and Decoding @chapter Encoding and Decoding |