2020-07-13 04:01 BST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0002710NetSurfLayoutpublic2020-05-27 09:14
ReporterHarriet Bazley 
Assigned To 
StatusclosedResolutionno change required 
PlatformIyonixOSRISC OSOS Version5.22
Product Version3.10 
Target VersionFixed in Version 
Summary0002710: Preformatted text fails to align
Descriptionwtr.in is designed to provide weather forecasts formatted with ASCII art suitable for terminal display. But the display doesn't line up correctly when viewing the site in Netsurf - the characters become more and more misaligned, as can be seen by the increasing distortion in what are intended to be vertical lines. The 'boxes' around the dates are always massively to the left of where they should be. Evidently the characters aren't all being rendered at the same width, despite the 'pre' tag which the website expects to achieve this.
Steps To ReproduceRequest a weather report from the site, e.g. http://wttr.in/London?u
Additional InformationIf you export the page as text, the resulting file *is* aligned as expected (save for Netsurf's valiant attempt at a meaningful rendition for the right arrow character, which comes out as two characters wide - preferable under normal circumstances to a question mark, but causing a slight problem here).
If you ask Netsurf to display the PNG version (using, for example, the URL http://wttr.in/London.png?u ) then the intended display is obtained.
TagsNo tags attached.
Fixed in CI build #
Reported in CI build #4885
URL of problem pagehttp://wttr.in/London?u
Attached Files


Harriet Bazley


Harriet Bazley (reporter)

London/html - source which generated screen shot above.
Harriet Bazley


Harriet Bazley (reporter)

London/txt - result of exporting page as plain text
Michael Drake


Michael Drake (administrator)

It looks like you're using a font like Corpus(?) as the monospace font that doesn't have a wide Unicode coverage. For the wind direction arrows it will be substituting the glyph from some other font which has the glyph. But it won't be the same monospace width as the Corpus font.

Try changing the monospace font in Choices to one with a wide Unicode coverage.

You may be able to convert one with:


-Issue History
Date Modified Username Field Change
2019-10-12 00:41 Harriet Bazley New Issue
2019-10-12 00:41 Harriet Bazley File Added: screen.png
2019-10-12 00:42 Harriet Bazley File Added: London.html
2019-10-12 00:42 Harriet Bazley Note Added: 0002101
2019-10-12 00:42 Harriet Bazley File Added: London.txt
2019-10-12 00:42 Harriet Bazley Note Added: 0002102
2019-10-15 13:45 Vincent Sanders Status new => acknowledged
2019-10-15 13:45 Vincent Sanders Product Version => 3.10
2019-10-15 13:45 Vincent Sanders Steps to Reproduce Updated View Revisions
2019-10-15 13:45 Vincent Sanders Additional Information Updated View Revisions
2019-11-29 21:02 Michael Drake Note Added: 0002140
2019-11-29 21:03 Michael Drake Status acknowledged => resolved
2019-11-29 21:03 Michael Drake Resolution open => no change required
2020-05-27 09:14 Vincent Sanders Status resolved => closed
+Issue History