In an attempt to answer the questions that have appeared recently,
I've written a guide to fonts and Unicode support in NetSurf.
Fonts in NetSurf
NetSurf has support for displaying pages containing Unicode characters
that aren't normally available on RISC OS, for example accented Latin
letters, Greek, Cyrillic, Japanese, and various symbols.
The font choices let you pick a font for each of the five standard
families available to web authors (in CSS). The choices specify the
preferred font to use. If a character is not available in the chosen
font, but it's present in some other font that you have installed,
then NetSurf will automatically use it. There's no need to change the
font choices to view pages with characters that are not available in
the chosen font.
Note that you can only choose a font family. NetSurf will
automatically use weights from the family for bold and slanted text,
Installing more fonts
The fonts that come with RISC OS cover Latin (Homerton, Trinity,
Corpus), Greek (Sidney), and various symbols (Selwyn, Sidney). (On
RISC OS 3-4, only the "Latin 1" characters from the standard fonts,
which cover Western European languages, can be used by NetSurf).
If you want to display pages with other characters correctly, you'll
need to install fonts containing them. When a character is not present
in any available font, the Unicode character code will be displayed.¹
Any font supplied with a correctly designed "Encoding" file should
work. In practice, native fonts covering anything other than Latin 1
are rare. The solution is to convert TrueType fonts using TTF2f (this
currently produces fonts suitable for RISC OS 5 only).
After installing new fonts, NetSurf will need restarting so that it
Problems and unimplemented features
* The default font is always the sans-serif one.
* Printing on RISC OS 5 doesn't work, due to lack of support in the
Font Manager and printer drivers. Printing to Postscript printers on
RISC OS 3-4 is not correctly implemented in NetSurf.
* Substituted characters are taken from the first font that contains
them, even if a character which matches the weight or slant better
* Only two weights (regular and bold) are supported, even if a family
contains other weights. The algorithm that finds weights needs
improving, for example using the heuristics given in CSS 2.1 15.6.
* Drawfile export is broken.
* Right-to-left text (Hebrew, Arabic) is not implemented.
¹ If you see the codes 0091, 0092, 0096, or others starting 009, that
indicates that the page is not specifying the character set that it
is using correctly. Installing fonts won't help. We haven't yet
decided what the best way to work around this problem is.
Due to lack of time, we're finding it difficult to reply to bug
reports on this list, and keep track of what needs fixing. Therefore
we've decided to change the way we do things.
>From now on, please report bugs to the bug tracker on SourceForge
instead of to this list:
If you set up a SourceForge account, you'll get an email whenever
something changes on a bug that you reported, and you can also choose
to monitor other bugs. Otherwise you'll need to note your bug number
and check back for changes.
There is also a similar tracker on SourceForge for feature requests.
(Where AppNameRes is some path variable.) If I click on this link, NetSurf
presents the file as a download (with type "data") rather than rendering
the file in the browser window. Is this a bug - or am I just missing
I use WinSnap and have nticed that while dragging NetSurf windows around
works as expected, if re-sizing the window does not snap to the top of the
icon bar - is it possible to make this work?
Adam Richardson Carpe Diem
I may have I done something wrong but the previous page and next page
buttons in the history don't seem to work any more.
7th of Nov and the latest 20th Nov 20:45 editions.
Rugby Union in Manchester:- http://www.broughton-park.org.uk/
Could a small change be made to the !Run file, please.
Run <NetSurf$Dir>.!RunImage %*0 2><NetSurf$Dir>.stderr
Run <NetSurf$Dir>.!RunImage %*0 2><Choices$Write>.WWW.NetSurf.stderr
This will mean that NetSurf will run from a read-only share,
without having to modify the file for each new version.
A sig will appear here when normal service is resumed :)
On 20 Nov 2005, James Bursa wrote:
> From now on, please report bugs to the bug tracker on SourceForge
In file:/<NetSurf$Dir>/Docs/intro_en, the wording of the second
sentence under 'Current Status' needs to be amended.
> There is also a similar tracker on SourceForge for feature requests.
A link to this page would be helpful (under the Bug tracker link).
Yahoo! Model Search 2005 - Find the next catwalk superstars - http://uk.news.yahoo.com/hot/model-search/
The first entry on the page for slashdot.org is squeezed between the menu
and the right hand side of the screen. It used to start like this and then
put itself right.
David Wild using RISC OS on broadband
With the last three or four versions of Netsurf I have a problem with
I can get to one of the postings but trying to move on to the next causes
Netsurf to disappear from the icon bar.
David Wild using RISC OS on broadband
In message <20051128041518.3B5191206D(a)sc8-sf-spam2.sourceforge.net>
> From: Adrian Lees <adrian(a)aemulor.com>
> To: <netsurf-develop(a)lists.sourceforge.net>
> Subject: Re: [Netsurf-develop] Netsurf Bugs - Illegal Handle
> Date: Mon, 28 Nov 2005 00:43:56 +0000
> On Sun, 27 Nov 2005 you wrote:
>> Using Netsurf Test Build 25/11/05 00:00 on a Risc PC SA with Adjust
>> 4.39. I get: "Warning from NetSurf - An unexpected Window Manager
>> error occurred: Illegal window handle" when menu> page>export also
>> page>Save location.
> We believe this has just been fixed; please try the latest build
> and report back if it still fails.
I have just tried the latest build (28/11/05 00:30) and the problem
has indeed been fixed. Thank you to the team for their prompt action.
Martin Wynn, Newport, Shropshire.
On Sun, 27 Nov 2005 you wrote:
> Using Netsurf Test Build 25/11/05 00:00 on a Risc PC SA with Adjust
> 4.39. I get: "Warning from NetSurf - An unexpected Window Manager
> error occurred: Illegal window handle" when menu> page>export also
> page>Save location.
We believe this has just been fixed; please try the latest build
and report back if it still fails.