On Thursday, August 29, 2013 12:50:07 AM UTC-5, Ken F wrote:
Composer inserts characters symbols display OK when preparing html
webpages. When viewed on the web, Firefox will display a black diamond
w/white ? for many (all?) of the inserted symbols characters.
Example links:
Ken F wrote:
On Thursday, August 29, 2013 12:50:07 AM UTC-5, Ken F wrote:
Composer inserts characters symbols display OK when preparing html webpages. When
viewed on the web, Firefox will display a black diamond w/white ? for many (all?) of
the inserted symbols characters.
Example links:
Philip Taylor p.tay...@rhul.ac.uk wrote:
Rob (nom...@example.com) wrote:
Content-Type: text/html; charset=UTF-8
meta http-equiv=Content-Type content=text/html;
charset=windows-1252
Nothing has changed. The HTTP Content-Type header has aways taken
precedence
over the HTML meta
Rob wrote:
Philip Taylor p.tay...@rhul.ac.uk wrote:
Rob (nom...@example.com) wrote:
Content-Type: text/html; charset=UTF-8
meta http-equiv=Content-Type content=text/html;
charset=windows-1252
Nothing has changed. The HTTP Content-Type header has aways taken
precedence
over the
Philip Taylor p.tay...@rhul.ac.uk wrote:
Rob wrote:
Philip Taylor p.tay...@rhul.ac.uk wrote:
Rob (nom...@example.com) wrote:
Content-Type: text/html; charset=UTF-8
meta http-equiv=Content-Type content=text/html;
charset=windows-1252
Nothing has changed. The HTTP Content-Type
On 8/30/13 11:34 AM +0900, Geoff Welsh wrote:
Geoff Welsh wrote:
Philip Taylor wrote:
Rob (nom...@example.com) wrote:
Content-Type: text/html; charset=UTF-8
meta http-equiv=Content-Type content=text/html;
charset=windows-1252
Nothing has changed. The HTTP Content-Type header has
On Thu, 29 Aug 2013 11:31:59 -0500, Rob wrote:
Philip Taylor p.tay...@rhul.ac.uk wrote:
Ralph Fox (-rf-nz-@xn--kba.invalid) wrote:
Nothing has changed. The HTTP Content-Type header has aways taken
precedence
over the HTML meta declaration, and not only in SM.
This is the
In news:slrnl1utrv.miv.nom...@xs8.xs4all.nl,
Rob nom...@example.com wrote:
Philip Taylor p.tay...@rhul.ac.uk wrote:
Ralph Fox (-rf-nz-@xn--kba.invalid) wrote:
Nothing has changed. The HTTP Content-Type header has aways taken
precedence over the HTML meta declaration, and not only in
Thank you all for the continuing discussion.
Have you shared enough that it is a good time for me to take this to the
webhost/webserver for additional support?
Ken F
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
Interviewed by CNN on 30/08/2013 02:34, Ken F told the world:
I will experiment with that. Doing the actual html codes could be a good
basic quick fix for me to do for restoring copyright symbols, and other
isolated symbols on webpages. It may be more difficult for the much older
story
On 8/31/13 12:58 PM +0900, MCBastos wrote:
Interviewed by CNN on 30/08/2013 02:34, Ken F told the world:
I will experiment with that. Doing the actual html codes could be a good basic quick
fix for me to do for restoring copyright symbols, and other isolated symbols on
webpages. It may be
kenandgiova...@yahoo.com wrote:
Composer inserts characters symbols display OK when preparing html webpages. When
viewed on the web, Firefox will display a black diamond w/white ? for many (all?) of
the inserted symbols characters.
Example links:
Test page -
kenandgiova...@yahoo.com wrote:
Composer inserts characters symbols display OK when preparing html
webpages. When viewed on the web, Firefox will display a black
diamond w/white ? for many (all?) of the inserted symbols
characters.
Example links:
Test page -
Paul B. Gallagher pau...@pbgdashtranslations.com wrote:
kenandgiova...@yahoo.com wrote:
Composer inserts characters symbols display OK when preparing html
webpages. When viewed on the web, Firefox will display a black
diamond w/white ? for many (all?) of the inserted symbols
characters.
On Thu, 29 Aug 2013 02:37:27 -0500, Rob wrote:
The HTTP headers say UTF-8:
HTTP/1.1 200 OK
Date: Thu, 29 Aug 2013 07:31:25 GMT
Server: Apache
Last-Modified: Thu, 29 Aug 2013 04:44:38 GMT
ETag: e74073-a7a-c36f5980
Accept-Ranges: bytes
Content-Length: 2682
Connection: close
Ralph Fox (-rf-nz-@xn--kba.invalid) wrote:
Nothing has changed. The HTTP Content-Type header has aways taken precedence
over the HTML meta declaration, and not only in SM.
This is the defined behaviour :
http://www.w3.org/International/questions/qa-html-encoding-declarations) :
The
Ralph Fox -rf-nz-@xn--kba.invalid wrote:
On Thu, 29 Aug 2013 02:37:27 -0500, Rob wrote:
The HTTP headers say UTF-8:
HTTP/1.1 200 OK
Date: Thu, 29 Aug 2013 07:31:25 GMT
Server: Apache
Last-Modified: Thu, 29 Aug 2013 04:44:38 GMT
ETag: e74073-a7a-c36f5980
Accept-Ranges: bytes
Philip Taylor p.tay...@rhul.ac.uk wrote:
Ralph Fox (-rf-nz-@xn--kba.invalid) wrote:
Nothing has changed. The HTTP Content-Type header has aways taken
precedence
over the HTML meta declaration, and not only in SM.
This is the defined behaviour :
Rob (nom...@example.com) wrote:
Content-Type: text/html; charset=UTF-8
meta http-equiv=Content-Type content=text/html; charset=windows-1252
Nothing has changed. The HTTP Content-Type header has aways taken
precedence
over the HTML meta declaration, and not only in SM.
Then why
Philip Taylor wrote:
Rob (nom...@example.com) wrote:
Content-Type: text/html; charset=UTF-8
meta http-equiv=Content-Type content=text/html; charset=windows-1252
Nothing has changed. The HTTP Content-Type header has aways taken precedence
over the HTML meta declaration, and not only
Geoff Welsh wrote:
Philip Taylor wrote:
Rob (nom...@example.com) wrote:
Content-Type: text/html; charset=UTF-8
meta http-equiv=Content-Type content=text/html;
charset=windows-1252
Nothing has changed. The HTTP Content-Type header has aways taken
precedence
over the HTML meta
Thank you all for your comments.
Even with my lack of html-fu I am getting some clues on what the issues likely
are.
Because of my work schedule, I may not be able to see comments or ask questions
until Friday evening after 9pm Central Daylight Time.
Ken F
On Thursday, August 29, 2013
On Thursday, August 29, 2013 2:37:27 AM UTC-5, Rob wrote:
((snipped))
The page appears to have a long history :-)
I suppose I could claim that the not-so-hidden layers of broken html code were
left underneath the surface on purpose, so future web archeologists could
accurately compute
On Thursday, August 29, 2013 9:34:26 PM UTC-5, Geoff Welsh wrote:
Geoff Welsh wrote:
Philip Taylor wrote:
Rob (.com) wrote:
Content-Type: text/html; charset=UTF-8
meta http-equiv=Content-Type content=text/html;
charset=windows-1252
Nothing has changed.
Composer inserts characters symbols display OK when preparing html webpages.
When viewed on the web, Firefox will display a black diamond w/white ? for
many (all?) of the inserted symbols characters.
Example links:
Test page -
http://spontoon.rootoon.com/SPwTest1.html
Looks OK in View/
25 matches
Mail list logo
