MantisBT - NetSurf
View Issue Details
0002549NetSurf[All Projects] Generalpublic2017-07-14 11:362017-10-16 22:37
ReporterBernard Boase 
Assigned ToDaniel Silverstone 
PrioritynormalSeveritytweakReproducibilityalways
StatusclosedResolutionfixed 
PlatformRISC OSOSRISC OSOS Version5.22, 5.23
Product Version 
Target Version3.7Fixed in Version3.7 
Fixed in CI build #4174
Reported in CI build #4135
URL of problem pagen/a
Summary0002549: Rendering of UTF-8 when <meta> attributes not semicolon separated
DescriptionLooking 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.
Steps To ReproduceInsert or delete a separating semicolon in above example.
Additional InformationQuery posted to netsurf-users@netsurf-browser.org forum 14-Jul-2017 in case others have relevant comments.
TagsNo tags attached.
Attached Files

Notes
(0001572)
Bernard Boase   
2017-07-14 12:05   
A particular HTML email attachment that shows this effect includes headers:

   Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
   X-Mailer: Apple Mail (2.3273)

Could Apple's omission of the semicolon be contrary to standards?
(0001578)
Daniel Silverstone   
2017-09-09 08:33   
Bernard,

Could you please provide me with the exact HTML tags present? E.g. is it

    <meta http-equiv="Content-Type" content="text/html charset=utf8">

or is it

    <meta content="text/html charset=utf8">

?
(0001579)
Daniel Silverstone   
2017-09-09 09:02   
I've pushed a change to hubbub to try and cope with this anyway.
(0001580)
Daniel Silverstone   
2017-09-09 09:32   
Updated hubbub now seems to resolve this.
(0001655)
Vincent Sanders   
2017-10-16 22:37   
Thankyou for your report, this has been resolved in the 3.7 release

Issue History
2017-07-14 11:36Bernard BoaseNew Issue
2017-07-14 12:05Bernard BoaseNote Added: 0001572
2017-09-09 08:33Daniel SilverstoneAssigned To => Daniel Silverstone
2017-09-09 08:33Daniel SilverstoneStatusnew => acknowledged
2017-09-09 08:33Daniel SilverstoneCategoryRISC OS-specific => General
2017-09-09 08:33Daniel SilverstoneDescription Updatedbug_revision_view_page.php?rev_id=1963#r1963
2017-09-09 08:33Daniel SilverstoneNote Added: 0001578
2017-09-09 09:02Daniel SilverstoneNote Added: 0001579
2017-09-09 09:03Daniel SilverstoneStatusacknowledged => confirmed
2017-09-09 09:32Daniel SilverstoneTarget Version => 3.7
2017-09-09 09:32Daniel SilverstoneFixed in CI build # => 4174
2017-09-09 09:32Daniel SilverstoneStatusconfirmed => resolved
2017-09-09 09:32Daniel SilverstoneResolutionopen => fixed
2017-09-09 09:32Daniel SilverstoneFixed in Version => 3.7
2017-09-09 09:32Daniel SilverstoneNote Added: 0001580
2017-10-16 22:37Vincent SandersStatusresolved => closed
2017-10-16 22:37Vincent SandersNote Added: 0001655