Re: Unicode on local pages

2012-12-18 Thread Gavin Wraith
In message <3e10b8ff52.mar...@blueyonder.co.uk> you wrote:

> The following bytes were arranged on 16 Dec 2012 by Gavin Wraith :
> 
> > With NetSurf #739. If I browse
> > http://www.perseus.tufts.edu/hopper/text?doc=Perseus%3Atext%3A1999.01.0173%3Atext%3DSym.
> > it displays OK. If I save or do a full save of the page, and then browse
> > the resulting local page the Greek text displays as garbage. Why is there
> > a difference?
> 
> This question's come up before.  It's probably because, when you fetch
> the file over HTTP, the server knows it's in UTF-8 and tells NetSurf so,
> but when you load a local file, RISC OS doesn't tell NetSurf what
> encoding it's in and so NetSurf is reduced to guesswork.  Presumably
> whatever encoding it defaults to is not the correct one in your case.

Thanks. I will have a look at the header and if necessary stick in the
right cantrap.
 
-- 
Gavin Wraith (ga...@wra1th.plus.com)
Home page: http://www.wra1th.plus.com/



Re: Unicode on local pages

2012-12-17 Thread Martin Bazley
The following bytes were arranged on 16 Dec 2012 by Gavin Wraith :

> With NetSurf #739. If I browse
> http://www.perseus.tufts.edu/hopper/text?doc=Perseus%3Atext%3A1999.01.0173%3Atext%3DSym.
> it displays OK. If I save or do a full save of the page, and then browse
> the resulting local page the Greek text displays as garbage. Why is there
> a difference?

This question's come up before.  It's probably because, when you fetch
the file over HTTP, the server knows it's in UTF-8 and tells NetSurf so,
but when you load a local file, RISC OS doesn't tell NetSurf what
encoding it's in and so NetSurf is reduced to guesswork.  Presumably
whatever encoding it defaults to is not the correct one in your case.

-- 
  __<^>__   === RISC OS is a work of art.  Some people adore it,  ===
 / _   _ \  === others can't see the point of it, and it's really ===
( ( |_| ) ) === expensive.===
 \_>   <_/  === Martin Bazley ===



Re: Unicode on local pages

2012-12-16 Thread Peter Young
On 16 Dec 2012  John Rickman Iyonix  wrote:

> Brian Howlett  wrote

>> On 16 Dec, Gavin Wraith wrote:

>>> With NetSurf #739. If I browse
>>> http://www.perseus.tufts.edu/hopper/text?doc=Perseus%3Atext%3A1999.01.
>>> 0173%3Atext%3DSym. it displays OK. If I save or do a full save of the
>>> page, and then browse the resulting local page the Greek text displays
>>> as garbage. Why is there a difference?

>> All I get from that page after the header is "We're sorry, but we were
>> unable to find a document matching your query."
>> Iyonix, RISC OS 5.18 and NS #743.

> Brian - the link is split over two lines in the Messenger mail editor.
> I copied it out to StrongED and clicked on it as one line ok.

Only if you include the full stop at the end of that URL. I originally 
got the "We're sorry..." message, as I assumed that a URL didn't 
usually have a full stop at the end of it!

With best wishes,

Peter.

-- 
Peter Young (zfc Ta) and family
Prestbury, Cheltenham, Glos. GL52, England
http://pnyoung.orpheusweb.co.uk
pnyo...@ormail.co.uk



Re: Unicode on local pages

2012-12-16 Thread John Rickman Iyonix
Brian Howlett  wrote

> On 16 Dec, Gavin Wraith wrote:

>> With NetSurf #739. If I browse
>> http://www.perseus.tufts.edu/hopper/text?doc=Perseus%3Atext%3A1999.01.
>> 0173%3Atext%3DSym. it displays OK. If I save or do a full save of the
>> page, and then browse the resulting local page the Greek text displays
>> as garbage. Why is there a difference?

> All I get from that page after the header is "We're sorry, but we were
> unable to find a document matching your query."
> Iyonix, RISC OS 5.18 and NS #743.

Brian - the link is split over two lines in the Messenger mail editor.
I copied it out to StrongED and clicked on it as one line ok.



-- 
John Rickman- http://mug.riscos.org/




Re: Unicode on local pages

2012-12-16 Thread Brian Howlett
On 16 Dec, Gavin Wraith wrote:

> With NetSurf #739. If I browse
> http://www.perseus.tufts.edu/hopper/text?doc=Perseus%3Atext%3A1999.01.
> 0173%3Atext%3DSym. it displays OK. If I save or do a full save of the
> page, and then browse the resulting local page the Greek text displays
> as garbage. Why is there a difference?

All I get from that page after the header is "We're sorry, but we were 
unable to find a document matching your query."

Iyonix, RISC OS 5.18 and NS #743.
-- 
Brian Howlett
--
"Are you the Prime Minister?" "No, but I've often been mistaken."
"What, for the Prime Minister?" "No. I've just often been mistaken..."



Re: Unicode on local pages

2012-12-16 Thread Gavin Wraith
NetSurf 3 #739

Altering fonts using the Fonts dialog in Choices.. from the iconbar
seems to have no effect on unicode text.

-- 
Gavin Wraith (ga...@wra1th.plus.com)
Home page: http://www.wra1th.plus.com/



Unicode on local pages

2012-12-16 Thread Gavin Wraith
With NetSurf #739. If I browse
http://www.perseus.tufts.edu/hopper/text?doc=Perseus%3Atext%3A1999.01.0173%3Atext%3DSym.
it displays OK. If I save or do a full save of the page, and then browse
the resulting local page the Greek text displays as garbage. Why is there
a difference?

-- 
Gavin Wraith (ga...@wra1th.plus.com)
Home page: http://www.wra1th.plus.com/