Re: boxconvert

2014-09-25 Thread Brian Jordan
In article 35e23c4c54@abbeypress.net,
   Jim Nagel nets...@abbeypress.co.uk wrote:
 What means the boxconvert error that Netsurf 3.2 gives for this 
 site?   http://glastonbury.bocabar.co.uk/

 (Using Ro 5.18 on Iyonix).

It was broken this morning, now it is mended.

NetSurf 3.3 (Dev CI #2123)

-- 
_

Brian Jordan
Virtual RPC-AdjustSA on Windows 8.1 Pro
RISC OS 6.20
_


---
This email is free from viruses and malware because avast! Antivirus protection 
is active.
http://www.avast.com




boxconvert

2014-09-24 Thread Jim Nagel
What means the boxconvert error that Netsurf 3.2 gives for this 
site?   http://glastonbury.bocabar.co.uk/

(Using Ro 5.18 on Iyonix).

-- 
Jim Nagel   www.archivemag.co.uk
|| See you at the show?  www.riscoslondonshow.co.uk   Oct 25




Re: Boxconvert

2014-09-24 Thread Jim Nagel
Funny that Richard Porter and I should come across the same problem 
almost simultaneously.

Chris Young wrote on 21 Aug:
 Can you consistently create the error on a particular page? Do you
 have a log file?

I named a site in my post just minutes ago.  Here's my log:
www.abbeypress.net/TEMP/NSlog140916.zip  (1.3meg)


-- 
Jim Nagelwww.archivemag.co.uk



Re: boxconvert

2014-09-24 Thread Cristopher Dewhurst
In message 35e23c4c54@abbeypress.net
  Jim Nagel nets...@abbeypress.co.uk wrote:

 What means the boxconvert error that Netsurf 3.2 gives for this
 site?   http://glastonbury.bocabar.co.uk/

 (Using Ro 5.18 on Iyonix).

I also get said boxconvert warning using RO Pi 5.21

Not an expert in HTML but seems that a call to html-marquee in the 
following extract is the offending code (I viewed the source in 
Firefox):

style type=text/css
.html-marquee {height:35px;width:730px;background-image:url(http://);f 
ont-family:Arial;font-size:12px;color:#FAD306;font-weight:bold;border-width:0;bo
 
rder-style:none;}
/style
/p
h2
marquee class=html-marquee direction=right behavior=slide 
scrollamount=9
We are now open on sunday evenings until 10pmbr /
/marquee



-- 
Chris



Boxconvert

2014-08-21 Thread Richard Porter
I got a warning from NetSurf - Boxconvert

What is boxconvert?

-- 
Richard Porterhttp://www.minijem.plus.com/
Skype: minijem2   mailto:r...@minijem.plus.com
I don't want a user experience - I just want stuff that works.



Re: Boxconvert

2014-08-21 Thread Chris Young
On Thu, 21 Aug 2014 23:12:19 +0100, Richard Porter wrote:

 I got a warning from NetSurf - Boxconvert
 
 What is boxconvert?

It means NetSurf hasn't been able to parse an HTML box (I'm not
entirely sure what the definion of a box is).  I suspect the plain
English version of this error has somehow gone missing.

Can you consistently create the error on a particular page? Do you
have a log file?

Chris



BoxConvert?

2014-06-11 Thread Richard Torrens (lists)
I can confirm that the latest build allows the page to display.

What Netsurf should do with the line
a href=http://!--#echo var=HTTP_HOST --!--#echo var=DOCUMENT_URI
--Top of page/a
I leave to others ... it's never going to do the right thing locally, so
as long as it doesn't stop display I think it's unimportant what happens.

-- 
Richard Torrens.
http://www.Torrens.org.uk for genealogy, natural history, wild food, walks, cats
and more!



Re: BoxConvert?

2014-06-11 Thread Rob Kendrick
On Wed, Jun 11, 2014 at 07:57:03AM +0100, Richard Torrens (lists) wrote:
 I can confirm that the latest build allows the page to display.
 
 What Netsurf should do with the line
 a href=http://!--#echo var=HTTP_HOST --!--#echo var=DOCUMENT_URI
 --Top of page/a
 I leave to others ... it's never going to do the right thing locally, so
 as long as it doesn't stop display I think it's unimportant what happens.

One wonders what's wrong with a #top anchor, anyway.

B.



Re: BoxConvert?

2014-06-09 Thread Daniel Silverstone
On Sun, Jun 08, 2014 at 12:18:49 +0100, Bob Latham wrote:
 So I emailed Daniel to his email address with the file, no reply.

Yeah, sorry, I was on holiday and have since been preparing for a university
exam despite having a full time job.  It's hard to keep up with what is spare
time fun for me in the meantime.

 He also asked me for something in cgi. Err what?

I was after enough to reproduce the issue.

 And the config file from Cherokee for which I've asked what's the file
 name and where it may be in the structure but had no reply.

If you don't know then perhaps someone managing your intranet does.

 At this point I walked away pretty wound up if I'm honest.

I can understand that.  I am sorry that I'm part of what upset you but I will
again point out that we do this for our own delight and enjoyment and sometimes
real-life does intrude for us.  If you're running CI versions of NetSurf you
can expect issues from time to time which may take a while to fix.

D.

-- 
Daniel Silverstone   http://www.netsurf-browser.org/
PGP mail accepted and encouraged.Key Id: 3CCE BABE 206C 3B69



Re: BoxConvert?

2014-06-09 Thread Bob Latham
In article 20140609101514.GE2612@somnambulist.local,
   Daniel Silverstone dsilv...@netsurf-browser.org wrote:
 On Sun, Jun 08, 2014 at 12:18:49 +0100, Bob Latham wrote:

  And the config file from Cherokee for which I've asked what's the file
  name and where it may be in the structure but had no reply.

 If you don't know then perhaps someone managing your intranet does.

Hmmm, its me. The intranet is in my house but I've never seen the config
file, I just used the management console. Isn't that what I'm supposed to
do? :-)

  At this point I walked away pretty wound up if I'm honest.

This was my fight with the bug tracker system.

 I can understand that.  I am sorry that I'm part of what upset you but I
 will again point out that we do this for our own delight and enjoyment
 and sometimes real-life does intrude for us. 

Absolutely, I was only reporting the facts, not complaining except I did
moan about the bug tracker. 

 If you're running CI versions of NetSurf you can expect issues from time
 to time which may take a while to fix.

Indeed. I'm grateful it may get fixed at some point. Presumably, other
platforms will have the same problem?


Bob.




Re: BoxConvert?

2014-06-09 Thread Steve Fryatt
On 9 Jun, Bob Latham wrote in message
541506117a...@mightyoak.org.uk:

 In article 20140609101514.GE2612@somnambulist.local,
Daniel Silverstone dsilv...@netsurf-browser.org wrote:
  On Sun, Jun 08, 2014 at 12:18:49 +0100, Bob Latham wrote:
 
   At this point I walked away pretty wound up if I'm honest.
 
 This was my fight with the bug tracker system.
 
  I can understand that.  I am sorry that I'm part of what upset you but I
  will again point out that we do this for our own delight and enjoyment
  and sometimes real-life does intrude for us.
 
 Absolutely, I was only reporting the facts, not complaining except I did
 moan about the bug tracker.

From a post on the dev list, there would seem to have been hardware issues
affecting the bug tracker over the weekend (which are now fixed). Maybe try
again?

-- 
Steve Fryatt - Leeds, England

http://www.stevefryatt.org.uk/



Re: BoxConvert?

2014-06-09 Thread Vincent Sanders
On Sat, Jun 07, 2014 at 04:50:01PM +0100, Richard Torrens (lists) wrote:
 What does the message BoxConvert mean? It's obscure to say the least!

It is, and it is a implementation detail from some code that requires
improvment in its error reporting. It efectively means it went badly
wrong and was caused as a side effect from ChrisY nice work
supporting IDNA hostname format. 

Any URL where the hostname was invalid for the IDNA parser caused the
new code to report that error, unfortunately as I mentioned the higher
level code delt with this poorly.

I have commited a possible fix which is available from the CI system
as build #1962 Hopefully this fix will fare better than Ranger 3 did
in 1962.

 
 I now (3.2 (Dev CI #1959)) get it on every local www page I run. Which is
 a pain - as I cannot then check a www page before uploading.
 
 I suspect it may be because I use SSI on my www pages: they contain, for
 example
  !--#include virtual=+NavTable.inc --
 and
  h2Page Information/h2
  BRDocument URL: !--#echo var=SERVER_NAME --!--#echo
 var=DOCUMENT_URI --
  BRPage first published 30th July 2005
  BRLast modified: !--#echo var=LAST_MODIFIED --
  !--#config timefmt=%Y --
  BR#169; 2005-!--#echo var=DATE_LOCAL -- 4QD
 
 -- 
 Richard Torrens.
 http://www.Torrens.org.uk for genealogy, natural history, wild food, walks, 
 cats
 and more!
 
 

-- 
Regards Vincent
http://www.kyllikki.org/



Re: BoxConvert?

2014-06-08 Thread Bob Latham
In article
out-539399f2.md-1.4.17.chris.yo...@unsatisfactorysoftware.co.uk,
   Chris Young chris.yo...@unsatisfactorysoftware.co.uk wrote:
 On Sat, 07 Jun 2014 19:58:41 +0100, Richard Torrens (lists) wrote:

  After a bit more experimenting, it is caused by the line:
  
  Pa href=http://!--#echo var=HTTP_HOST --!--#echo
  var=DOCUMENT_URI --Top of page/a

 Ah, right.  I know exactly what the problem is and what causes it.

 NetSurf now rejects invalid URLs.  By invalid I mean, anything
 containing characters that are not permitted either in old-style ASCII
 names, or in IDNA, plus some other validity checking mostly related to
 IDNs.

 Previously NetSurf would percent-encode the host and return that, so
 you'd end up with a garbage URL.  Now it rejects the URL outright. 
 However, it appears the layouting can't cope with that.  I did some
 extensive searching when I made this change initially and was unable
 to track down why this was causing the layouting to fail - ideally, a
 broken URL shouldn't cause termination of the layouting process, it
 should only make the problem link go nowhere.

 I considered this low risk at the time as it is incredibly rare to
 encounter a link to a URL which doesn't conform to the rules.

 However, obviously it does need to be fixed, so if you can raise it on
 the bugtracker that'd be grand.

Good luck with that.

I'm plagued with this BocConvert as well as told in my thread Username
and Password problem.

Daniel showed some interest and asked for information and I've tried
everything to get it to him and after (in total) a couple of hours trying
I've given up.

The log from my Netsurf seems to say that it bombs out BoxConvert because
it encounters the character 5f presumably hex or 5F. I have searched
through the relevant html on my intranet and no 5F anywhere and certainly
not in a page url.

Mine is triggered not by the web page as such but by the security username
and password on items inside one folder on my Cherokee driven Intranet.

This started to happen for me with build 1950 and has persisted ever since
but builds up to and including 1949 did not have the problem. I would not
be surprised if the problem in this thread started with also 1950.

As regards reporting the problem, I found this an obstacle course and no
doubt.

Firstly, I was asked for a log file from netsurf which after some reading
and testing I managed to generate. I possibly wrongly emailed it to the
mailing list. I was told it was being help for the next moderator as it
was a little too big.

So I emailed Daniel to his email address with the file, no reply.

He also asked me for something in cgi. Err what?

And the config file from Cherokee for which I've asked what's the file
name and where it may be in the structure but had no reply.

The I thought maybe I should look into this bug tracker whatsit, that when
the problems started.

Registration kept bombing out or doing nothing and I had to use a PC to
get this done. I then logged in using the ARMiniX and Netsurf filled in a
report and then found in Netsurf I could not attach a log file.

I logged in on the pc, filled min the forms all again, attached the file,
hit send and it bombed out again.

At this point I walked away pretty wound up if I'm honest.



Cheers,

Bob.




Re: BoxConvert?

2014-06-08 Thread Chris Young


On 8 June 2014 12:18:49 BST, Bob Latham b...@mightyoak.org.uk wrote:
In article
out-539399f2.md-1.4.17.chris.yo...@unsatisfactorysoftware.co.uk,
   Chris Young chris.yo...@unsatisfactorysoftware.co.uk wrote:
 On Sat, 07 Jun 2014 19:58:41 +0100, Richard Torrens (lists) wrote:

  After a bit more experimenting, it is caused by the line:
  
  Pa href=http://!--#echo var=HTTP_HOST --!--#echo
  var=DOCUMENT_URI --Top of page/a

 Ah, right.  I know exactly what the problem is and what causes it.

 NetSurf now rejects invalid URLs.  By invalid I mean, anything
 containing characters that are not permitted either in old-style
ASCII
 names, or in IDNA, plus some other validity checking mostly related
to
 IDNs.

 Previously NetSurf would percent-encode the host and return that, so
 you'd end up with a garbage URL.  Now it rejects the URL outright. 
 However, it appears the layouting can't cope with that.  I did some
 extensive searching when I made this change initially and was unable
 to track down why this was causing the layouting to fail - ideally, a
 broken URL shouldn't cause termination of the layouting process, it
 should only make the problem link go nowhere.

 I considered this low risk at the time as it is incredibly rare to
 encounter a link to a URL which doesn't conform to the rules.

 However, obviously it does need to be fixed, so if you can raise it
on
 the bugtracker that'd be grand.

Good luck with that.

I'm plagued with this BocConvert as well as told in my thread Username
and Password problem.

Daniel showed some interest and asked for information and I've tried
everything to get it to him and after (in total) a couple of hours
trying
I've given up.

The log from my Netsurf seems to say that it bombs out BoxConvert
because
it encounters the character 5f presumably hex or 5F. I have searched
through the relevant html on my intranet and no 5F anywhere and
certainly
not in a page url.

Mine is triggered not by the web page as such but by the security
username
and password on items inside one folder on my Cherokee driven Intranet.
   

This started to happen for me with build 1950 and has persisted ever
since
but builds up to and including 1949 did not have the problem. I would
not
be surprised if the problem in this thread started with also 1950.

As regards reporting the problem, I found this an obstacle course and
no
doubt.

Firstly, I was asked for a log file from netsurf which after some
reading
and testing I managed to generate. I possibly wrongly emailed it to the
mailing list. I was told it was being help for the next moderator as it
was a little too big.

So I emailed Daniel to his email address with the file, no reply.

He also asked me for something in cgi. Err what?

And the config file from Cherokee for which I've asked what's the file
name and where it may be in the structure but had no reply.

The I thought maybe I should look into this bug tracker whatsit, that
when
the problems started.

Registration kept bombing out or doing nothing and I had to use a PC to
get this done. I then logged in using the ARMiniX and Netsurf filled in
a
report and then found in Netsurf I could not attach a log file.

I logged in on the pc, filled min the forms all again, attached the
file,
hit send and it bombed out again.

At this point I walked away pretty wound up if I'm honest.

Apologies for the excessive quoting. Can you send the log to me?

Chris




Re: BoxConvert?

2014-06-07 Thread Chris Young
On Sat, 07 Jun 2014 16:50:01 +0100, Richard Torrens (lists) wrote:

 What does the message BoxConvert mean? It's obscure to say the least!

It means NetSurf wasn't able to convert a box :)

I don't fully understand how it works, but it is to do with layouting.

 I now (3.2 (Dev CI #1959)) get it on every local www page I run. Which is
 a pain - as I cannot then check a www page before uploading.
 
 I suspect it may be because I use SSI on my www pages: they contain, for
 example

I wouldn't have thought so.  The SSI portion is an HTML comment if it
isn't getting parsed by the server, so it should be getting ignored.

a) When did this start?
b) Can you post one of the faulty pages here, or upload it in a way in
which it can be downloaded without the SSI being parsed?

Chris



Re: BoxConvert?

2014-06-07 Thread Chris Young
On 7 Jun 2014 17:32:35 +0100, Chris Young wrote:

 On Sat, 07 Jun 2014 16:50:01 +0100, Richard Torrens (lists) wrote:
  I now (3.2 (Dev CI #1959)) get it on every local www page I run. Which is
  a pain - as I cannot then check a www page before uploading.

 a) When did this start?
 b) Can you post one of the faulty pages here, or upload it in a way in
 which it can be downloaded without the SSI being parsed?
c) Log file?

Somehow missed (c).

Chris



Re: BoxConvert?

2014-06-07 Thread Richard Torrens (lists)
In article
out-53934cb3.md-1.4.17.chris.yo...@unsatisfactorysoftware.co.uk,
   Chris Young chris.yo...@unsatisfactorysoftware.co.uk wrote:
 a) When did this start?

I haven't updated NS for a while so don't know when it started!

 b) Can you post one of the faulty pages here, or upload it in a way in
 which it can be downloaded without the SSI being parsed?

After a bit more experimenting, it is caused by the line:

Pa href=http://!--#echo var=HTTP_HOST --!--#echo
var=DOCUMENT_URI --Top of page/a

Two pages in the attached archive: one contains the line, one does not.

NS clearly isn't going to do anything sensible with this - but at present
it causes the page not to load at all.

-- 
Richard Torrens.
http://www.Torrens.org.uk for genealogy, natural history, wild food, walks, cats
and more!


new.zip,A91
Description: application/riscos


Re: BoxConvert?

2014-06-07 Thread Chris Young
On Sat, 07 Jun 2014 19:58:41 +0100, Richard Torrens (lists) wrote:

 After a bit more experimenting, it is caused by the line:
 
 Pa href=http://!--#echo var=HTTP_HOST --!--#echo
 var=DOCUMENT_URI --Top of page/a

Ah, right.  I know exactly what the problem is and what causes it.

NetSurf now rejects invalid URLs.  By invalid I mean, anything
containing characters that are not permitted either in old-style ASCII
names, or in IDNA, plus some other validity checking mostly related to
IDNs.

Previously NetSurf would percent-encode the host and return that, so
you'd end up with a garbage URL.  Now it rejects the URL outright. 
However, it appears the layouting can't cope with that.  I did some
extensive searching when I made this change initially and was unable
to track down why this was causing the layouting to fail - ideally, a
broken URL shouldn't cause termination of the layouting process, it
should only make the problem link go nowhere.

I considered this low risk at the time as it is incredibly rare to
encounter a link to a URL which doesn't conform to the rules.

However, obviously it does need to be fixed, so if you can raise it on
the bugtracker that'd be grand.

Chris