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
While looking at #3223 I noticed that text/plain never actually invokes the Encoding Standard itself. The text/plain algorithm has two callers and one of those does call the Encoding Standard, but the other one always UTF-8 encodes, which would mismatch with any charset fields.
It doesn't seem quite right. And if it is right we should have a note there about the strangeness.
While looking at #3223 I noticed that text/plain never actually invokes the Encoding Standard itself. The text/plain algorithm has two callers and one of those does call the Encoding Standard, but the other one always UTF-8 encodes, which would mismatch with any charset fields.
It doesn't seem quite right. And if it is right we should have a note there about the strangeness.
It might be worth fixing #2223 first.
The text was updated successfully, but these errors were encountered: