View Revisions: Issue #2549
[ Back to Issue ]
| Summary | 0002549: Rendering of UTF-8 when <meta> attributes not semicolon separated | ||
|---|---|---|---|
| Revision | 2017-07-14 12:36 by Bernard Boase | ||
| Description | Looking in detail at some recent HTML email attachments (received in Messenger Pro), Netsurf's rendering of them seems to have a dependence on the coding of the <meta content=""> tag. When this tag is present and includes: content="text/html charset=utf-8" any non-ASCII characters are rendered as the three bytes of their UTF-8 encoding, whereas if the two attributes are separated by semicolon: content="text/html; charset=utf-8" the rendering (using Unicode font DejaVu) looks correct. |
||
| Revision | 2017-09-09 09:33 by kinnison | ||
| Description | Looking in detail at some recent HTML email attachments (received in Messenger Pro), Netsurf's rendering of them seems to have a dependence on the coding of the <meta content=""> tag. When this tag is present and includes: content="text/html charset=utf-8" any non-ASCII characters are rendered as the three bytes of their UTF-8 encoding, whereas if the two attributes are separated by semicolon: content="text/html; charset=utf-8" the rendering (using Unicode font DejaVu) looks correct. |
||