You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking through decode_header in the Git source, it looks like there are several possible encodings. Currently, we only support quoted-printable UTF-8 and ignore anything else (implemented in #25.)
To support arbitrary encodings, I think we need to:
Identify the encoding from the text between the first =? and the next ?
Use the q? or b? to determine if the content until the next =? is encoded as quoted-printable or base64
Looking through
decode_header
in the Git source, it looks like there are several possible encodings. Currently, we only support quoted-printable UTF-8 and ignore anything else (implemented in #25.)To support arbitrary encodings, I think we need to:
=?
and the next?
q?
orb?
to determine if the content until the next=?
is encoded asquoted-printable
orbase64
ianaindex.MIME
to look up the encodingThe text was updated successfully, but these errors were encountered: