On Fri, 11 Jul 2014, David Bremner wrote:
> Austin Clements writes:
>
>> +This returns the content of the given part as a multibyte Lisp
>
> What does "multibyte" mean here? utf8? current encoding?
Elisp has two kinds of stings: "unibyte strings" and "multibyte
strings".
https://www.gnu.org/
On Fri, 11 Jul 2014, David Bremner wrote:
> Austin Clements writes:
>
>> +This returns the content of the given part as a multibyte Lisp
>
> What does "multibyte" mean here? utf8? current encoding?
Elisp has two kinds of stings: "unibyte strings" and "multibyte
strings".
https://www.gnu.org/
Austin Clements writes:
> +This returns the content of the given part as a multibyte Lisp
What does "multibyte" mean here? utf8? current encoding?
> +string after performing content transfer decoding and any
> +necessary charset decoding. It is an error to use this for
> +non-text/* parts."
>
Austin Clements writes:
> +This returns the content of the given part as a multibyte Lisp
What does "multibyte" mean here? utf8? current encoding?
> +string after performing content transfer decoding and any
> +necessary charset decoding. It is an error to use this for
> +non-text/* parts."
>
`notmuch-get-bodypart-content' could do two very different things,
depending on conditions: for text/* parts other than text/html, it
would return the part content as a multibyte Lisp string *after*
charset conversion, while for other parts (including text/html), it
would return binary part content
`notmuch-get-bodypart-content' could do two very different things,
depending on conditions: for text/* parts other than text/html, it
would return the part content as a multibyte Lisp string *after*
charset conversion, while for other parts (including text/html), it
would return binary part content
