In article <50768756a5t...@netsurf-browser.org>, Michael Drake <t...@netsurf-browser.org> wrote: > In article <507685eb29rh.li...@phone.coop>, Russell > Hafter - Lists <rh.li...@phone.coop> wrote:
> > But while that may be a reason, it does not explain the > > need for font scanning *to me*. Sorry. > Try reading the description of what RUfl does here: > http://www.netsurf-browser.org/projects/rufl/ Thanks. I read at the end: "RUfl manages to do all this efficiently by maintaining cached lookup tables containing various mappings." So, would I be correct in thinking that NetSurf, and only NetSurf, needs to do this font scanning, because it has the laudable aim of filling the gaps in RISC OS unicode abilities? Other RISC OS browsers ignore the problem, while other platforms assume that full unicode support is there in the first place? And the the scanning, among other things, creates the lookup tables? -- Russell Hafter - Mailing Lists rh.li...@phone.coop Need a hotel? <http://www.hrs.de/?client=en__MT&customerId=416873103> (NB This link needs Firefox to work)
