On Sun, Dec 16, 2012 at 04:07:25PM +0000, Chris Gransden wrote:
> In article <20121216154023.GL15360@kyllikki.org>,
> Vincent Sanders <vince@netsurf-browser.org> wrote:
> > OK, the CI system just built #740 with a spidermonkey 1.8.5 library
> > with the JIT disabled as suggested by Chris Gransden. Can this be
> > tried by someone with access to RISC OS? and please be aware this may
> > well behave very badly indeed.
>
> It get stuck in a infinite loop as soon as a web page is opened. Alt-break
> is the only way to quit.
>
bother, oh well. any posibility of a log to maybe debug it? anyway I
will sort out switching to the 1.7.0 build for now.
> Chris.
>
>
>
--
Regards Vincent
http://www.kyllikki.org/
Sunday, 16 December 2012
Re: RISC OS Javascript support
In article <20121216154023.GL15360@kyllikki.org>,
Vincent Sanders <vince@netsurf-browser.org> wrote:
> OK, the CI system just built #740 with a spidermonkey 1.8.5 library
> with the JIT disabled as suggested by Chris Gransden. Can this be
> tried by someone with access to RISC OS? and please be aware this may
> well behave very badly indeed.
It get stuck in a infinite loop as soon as a web page is opened. Alt-break
is the only way to quit.
Chris.
Vincent Sanders <vince@netsurf-browser.org> wrote:
> OK, the CI system just built #740 with a spidermonkey 1.8.5 library
> with the JIT disabled as suggested by Chris Gransden. Can this be
> tried by someone with access to RISC OS? and please be aware this may
> well behave very badly indeed.
It get stuck in a infinite loop as soon as a web page is opened. Alt-break
is the only way to quit.
Chris.
Re: RISC OS Javascript support
OK, the CI system just built #740 with a spidermonkey 1.8.5 library
with the JIT disabled as suggested by Chris Gransden. Can this be
tried by someone with access to RISC OS? and please be aware this may
well behave very badly indeed.
If this fails I have now successfully built 1.7.0 for RISC OS (though
not run tested) so the possibility of using an older known working
version exists.
Please remember to enable javascript via the nice shiny new
configuration interface Steve Fryatt has provided.
--
Regards Vincent
http://www.kyllikki.org/
with the JIT disabled as suggested by Chris Gransden. Can this be
tried by someone with access to RISC OS? and please be aware this may
well behave very badly indeed.
If this fails I have now successfully built 1.7.0 for RISC OS (though
not run tested) so the possibility of using an older known working
version exists.
Please remember to enable javascript via the nice shiny new
configuration interface Steve Fryatt has provided.
--
Regards Vincent
http://www.kyllikki.org/
Re: Javascript and Fonts
On 16 Dec 2012 John Rickman Iyonix <rickman@argonet.co.uk> wrote:
> Peter Young wrote
>>> Looks more complete on linux raspberry Pi Chromium Chromium browser.
>>> On RISC OS the accented characters appear as hex couplets.
>> It's all Greek here (and Greek to me!) on an ARMini, RISC OS 5.19.
>> Perhaps you don't have the necessary font?
> Probably:-( I have DoulosSIL which I thought was a comprehensive
> Unicode font. But among other things, it does not appear to have a
> glyph for: " Greek Small Letter Iota with acute accent U+03AF "
> What font are you using?
I'm using Cyberbit here, It's a freeware TTF font that I converted to
RISC OS format using !TTF2f, which app as far as I remember ran on my
late Iyo; it certainly runs on this ARMini. From my hazy memory,
DoulosSIL mainly deals with diacritics of languages like Czech, though
this might be my mistake. I don't think it's a full Unicode font,
anyway. Cyberbit has omissions, where occasionally characters appear
as hex couplets, but is pretty wide-ranging.
With best wishes,
Peter.
--
Peter Young (zfc Ta) and family
Prestbury, Cheltenham, Glos. GL52, England
http://pnyoung.orpheusweb.co.uk
pnyoung@ormail.co.uk
> Peter Young wrote
>>> Looks more complete on linux raspberry Pi Chromium Chromium browser.
>>> On RISC OS the accented characters appear as hex couplets.
>> It's all Greek here (and Greek to me!) on an ARMini, RISC OS 5.19.
>> Perhaps you don't have the necessary font?
> Probably:-( I have DoulosSIL which I thought was a comprehensive
> Unicode font. But among other things, it does not appear to have a
> glyph for: " Greek Small Letter Iota with acute accent U+03AF "
> What font are you using?
I'm using Cyberbit here, It's a freeware TTF font that I converted to
RISC OS format using !TTF2f, which app as far as I remember ran on my
late Iyo; it certainly runs on this ARMini. From my hazy memory,
DoulosSIL mainly deals with diacritics of languages like Czech, though
this might be my mistake. I don't think it's a full Unicode font,
anyway. Cyberbit has omissions, where occasionally characters appear
as hex couplets, but is pretty wide-ranging.
With best wishes,
Peter.
--
Peter Young (zfc Ta) and family
Prestbury, Cheltenham, Glos. GL52, England
http://pnyoung.orpheusweb.co.uk
pnyoung@ormail.co.uk
Re: RISC OS Javascript support
On Sun, 16 Dec 2012 13:45:46 +0000, Vincent Sanders wrote:
> > 1.7 doesn't need NSPR
> I must have misunderstood what teh DIST variable points at then? but
> thats perfectly possible ;-)
IIRC it needs NSPR if you build it as threaded, but you don't need to
do that.
> well I would be very interested in a diff against the distribution
> archive anyway. If I can get the NetSurf toolchain package building
> spidermonkey for your platform we can get the CI builds (and by
> extension future release builds) to generate output with JavaScript
> support for your platform
Attached.
Chris
> > 1.7 doesn't need NSPR
> I must have misunderstood what teh DIST variable points at then? but
> thats perfectly possible ;-)
IIRC it needs NSPR if you build it as threaded, but you don't need to
do that.
> well I would be very interested in a diff against the distribution
> archive anyway. If I can get the NetSurf toolchain package building
> spidermonkey for your platform we can get the CI builds (and by
> extension future release builds) to generate output with JavaScript
> support for your platform
Attached.
Chris
Re: Javascript and Fonts
In message <c66cfdfe52.iyojohn@rickman.argonet.co.uk> you wrote:
> Peter Young wrote
>
> >> Looks more complete on linux raspberry Pi Chromium Chromium browser.
> >> On RISC OS the accented characters appear as hex couplets.
>
> > It's all Greek here (and Greek to me!) on an ARMini, RISC OS 5.19.
> > Perhaps you don't have the necessary font?
>
> Probably:-( I have DoulosSIL which I thought was a comprehensive
> Unicode font. But among other things, it does not appear to have a
> glyph for: " Greek Small Letter Iota with acute accent U+03AF "
>
> What font are you using?
That is part of what I am trying to find out! I have not added any
fonts to the Raspberry Pi RISC OS distro so I presume it is one of
the new fonts it provides in !Fonts. Maybe FreeMono, FreeSans, .... .
I tried altering the names of some of these, to see if I could get
RUfl to make different choices of font - after all there are probably
masses of installed fonts for NetSurf to choose from when it is asked
to display a particular glyph - but, when I rebooted, NetSurf bottled
out with an error message about not being able to initialize the
Unicode fonts.
My problems concern \pi and \mu being rendered bold. It would be
nice if RUfl_cache held its data in text form. Then a) we could
read it to see which font was being used for which glyph, and b)
we could edit it to get some control over how NetSurf shows text.
Or at least, I presume so. Glad to be corrected if I have this
upside down, by somebody knows how RUfl works.
--
Gavin Wraith (gavin@wra1th.plus.com)
Home page: http://www.wra1th.plus.com/
> Peter Young wrote
>
> >> Looks more complete on linux raspberry Pi Chromium Chromium browser.
> >> On RISC OS the accented characters appear as hex couplets.
>
> > It's all Greek here (and Greek to me!) on an ARMini, RISC OS 5.19.
> > Perhaps you don't have the necessary font?
>
> Probably:-( I have DoulosSIL which I thought was a comprehensive
> Unicode font. But among other things, it does not appear to have a
> glyph for: " Greek Small Letter Iota with acute accent U+03AF "
>
> What font are you using?
That is part of what I am trying to find out! I have not added any
fonts to the Raspberry Pi RISC OS distro so I presume it is one of
the new fonts it provides in !Fonts. Maybe FreeMono, FreeSans, .... .
I tried altering the names of some of these, to see if I could get
RUfl to make different choices of font - after all there are probably
masses of installed fonts for NetSurf to choose from when it is asked
to display a particular glyph - but, when I rebooted, NetSurf bottled
out with an error message about not being able to initialize the
Unicode fonts.
My problems concern \pi and \mu being rendered bold. It would be
nice if RUfl_cache held its data in text form. Then a) we could
read it to see which font was being used for which glyph, and b)
we could edit it to get some control over how NetSurf shows text.
Or at least, I presume so. Glad to be corrected if I have this
upside down, by somebody knows how RUfl works.
--
Gavin Wraith (gavin@wra1th.plus.com)
Home page: http://www.wra1th.plus.com/
Re: RISC OS Javascript support
On Sun, Dec 16, 2012 at 01:18:52PM +0000, Chris Young wrote:
> On Sun, 16 Dec 2012 11:44:53 +0000, Vincent Sanders wrote:
>
> > I spent a few hours on this yestarday. The 1.7.0 download [1] is not
> > autoconf and I was unable to persuade it to cross compile with our
> > toolchain let alone with the nspr. If you have a recipie that would be
> > great...
>
> 1.7 doesn't need NSPR, that's one of the advantages of using it (I'm
> still watching a couple of Bugzillas for NSPR to be removed from newer
> Spidermonkey, it should be easier to get that to work then).
I must have misunderstood what teh DIST variable points at then? but
thats perfectly possible ;-)
>
> I have an archive with a hand-crafted makefile, although I have a
> feeling there are a couple of executables that it has to build in
> order to build the library, that I ended up having to build manually,
> so it'll need some tweaking. I can send it to you if you want it (it
> has all the AmigaOS changes too, but they are all #ifdef'd XP_AMIGA so
> won't affect RISC OS)
>
well I would be very interested in a diff against the distribution
archive anyway. If I can get the NetSurf toolchain package building
spidermonkey for your platform we can get the CI builds (and by
extension future release builds) to generate output with JavaScript
support for your platform
> Chris
>
>
--
Regards Vincent
http://www.kyllikki.org/
> On Sun, 16 Dec 2012 11:44:53 +0000, Vincent Sanders wrote:
>
> > I spent a few hours on this yestarday. The 1.7.0 download [1] is not
> > autoconf and I was unable to persuade it to cross compile with our
> > toolchain let alone with the nspr. If you have a recipie that would be
> > great...
>
> 1.7 doesn't need NSPR, that's one of the advantages of using it (I'm
> still watching a couple of Bugzillas for NSPR to be removed from newer
> Spidermonkey, it should be easier to get that to work then).
I must have misunderstood what teh DIST variable points at then? but
thats perfectly possible ;-)
>
> I have an archive with a hand-crafted makefile, although I have a
> feeling there are a couple of executables that it has to build in
> order to build the library, that I ended up having to build manually,
> so it'll need some tweaking. I can send it to you if you want it (it
> has all the AmigaOS changes too, but they are all #ifdef'd XP_AMIGA so
> won't affect RISC OS)
>
well I would be very interested in a diff against the distribution
archive anyway. If I can get the NetSurf toolchain package building
spidermonkey for your platform we can get the CI builds (and by
extension future release builds) to generate output with JavaScript
support for your platform
> Chris
>
>
--
Regards Vincent
http://www.kyllikki.org/
Subscribe to:
Posts (Atom)