Warnings when I visit http://www.macports.org/ in Safari v.1.3.2
Hi, when I viist http://www.macports.org/ with Safari v.1.3.2, I always see the warnings saying <warnings> This page contains the following errors: error on line 41 at column 459: Entity 'nbsp' not defined error on line 92 at column 45: Entity 'ldquo' not defined error on line 113 at column 211: Entity 'ldquo' not defined error on line 125 at column 319: Entity 'ldquo' not defined Below is a rendering of the page up to the first error. </warnings> The page was itself apparently rendered well. Is this a problem no a bit old Safari? (seems safari process the document as xml?) In my opinion, if MacPorts is still supporting OS S 10.3, the main page should be ready for Safari v.1.3.2, the latest Safari for OS X 10.3. Any comments or suggestions?
Sounds like a bug. Though it may surprise some people to learn it, "nbsp" etc. are not valid entities in XML. Please file a ticket in our issue tracker so we can correct this. On Feb 22, 2008, at 23:07, js wrote:
Hi,
when I viist http://www.macports.org/ with Safari v.1.3.2, I always see the warnings saying
<warnings> This page contains the following errors: error on line 41 at column 459: Entity 'nbsp' not defined error on line 92 at column 45: Entity 'ldquo' not defined error on line 113 at column 211: Entity 'ldquo' not defined error on line 125 at column 319: Entity 'ldquo' not defined
Below is a rendering of the page up to the first error. </warnings>
The page was itself apparently rendered well.
Is this a problem no a bit old Safari? (seems safari process the document as xml?)
In my opinion, if MacPorts is still supporting OS S 10.3, the main page should be ready for Safari v.1.3.2, the latest Safari for OS X 10.3.
Any comments or suggestions?
Done http://trac.macosforge.org/projects/macports/ticket/14455 On Sat, Feb 23, 2008 at 8:47 PM, Ryan Schmidt <ryandesign@macports.org> wrote:
Sounds like a bug. Though it may surprise some people to learn it, "nbsp" etc. are not valid entities in XML. Please file a ticket in our issue tracker so we can correct this.
On Feb 22, 2008, at 23:07, js wrote:
Hi,
when I viist http://www.macports.org/ with Safari v.1.3.2, I always see the warnings saying
<warnings> This page contains the following errors: error on line 41 at column 459: Entity 'nbsp' not defined error on line 92 at column 45: Entity 'ldquo' not defined error on line 113 at column 211: Entity 'ldquo' not defined error on line 125 at column 319: Entity 'ldquo' not defined
Below is a rendering of the page up to the first error. </warnings>
The page was itself apparently rendered well.
Is this a problem no a bit old Safari? (seems safari process the document as xml?)
In my opinion, if MacPorts is still supporting OS S 10.3, the main page should be ready for Safari v.1.3.2, the latest Safari for OS X 10.3.
Any comments or suggestions?
On Feb 23, 2008, at 7:17 AM, Ryan Schmidt wrote:
Sounds like a bug. Though it may surprise some people to learn it, "nbsp" etc. are not valid entities in XML. Please file a ticket in our issue tracker so we can correct this.
If I'm not mistaken, they are in XHTML, as added by the DTD's: http://www.w3.org/TR/xhtml-modularization/dtd_module_defs.html#a_module_XHTM... (again, if I'm not mistaken, that document applies to XHTML 1.1, which is what I used for the website) But, of course, I could be reading that wrong, since you know much more about the subject than me ;-) In any case, would using the unicode code points fix the problems? Regards,... -jmpp
On Feb 22, 2008, at 23:07, js wrote:
Hi,
when I viist http://www.macports.org/ with Safari v.1.3.2, I always see the warnings saying
<warnings> This page contains the following errors: error on line 41 at column 459: Entity 'nbsp' not defined error on line 92 at column 45: Entity 'ldquo' not defined error on line 113 at column 211: Entity 'ldquo' not defined error on line 125 at column 319: Entity 'ldquo' not defined
Below is a rendering of the page up to the first error. </warnings>
The page was itself apparently rendered well.
Is this a problem no a bit old Safari? (seems safari process the document as xml?)
In my opinion, if MacPorts is still supporting OS S 10.3, the main page should be ready for Safari v.1.3.2, the latest Safari for OS X 10.3.
Any comments or suggestions?
macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
The problem is Safari 1.3 is processing the page as an XML document, even though, just as you pointed out, it's really a XHTML. The server seems returning the right HTTP header, "Content-Type: application/xhtml+xml; charset=utf-8", so I think it's actually a Safari's problem. Converting the entities with its applicable characters or numeric entities would fix this problem. On 2/25/08, Juan Manuel Palacios <jmpp@macports.org> wrote:
On Feb 23, 2008, at 7:17 AM, Ryan Schmidt wrote:
Sounds like a bug. Though it may surprise some people to learn it, "nbsp" etc. are not valid entities in XML. Please file a ticket in our issue tracker so we can correct this.
If I'm not mistaken, they are in XHTML, as added by the DTD's:
http://www.w3.org/TR/xhtml-modularization/dtd_module_defs.html#a_module_XHTM... (again, if I'm not mistaken, that document applies to XHTML 1.1, which is what I used for the website)
But, of course, I could be reading that wrong, since you know much more about the subject than me ;-) In any case, would using the unicode code points fix the problems?
Regards,...
-jmpp
On Feb 22, 2008, at 23:07, js wrote:
Hi,
when I viist http://www.macports.org/ with Safari v.1.3.2, I always see the warnings saying
<warnings> This page contains the following errors: error on line 41 at column 459: Entity 'nbsp' not defined error on line 92 at column 45: Entity 'ldquo' not defined error on line 113 at column 211: Entity 'ldquo' not defined error on line 125 at column 319: Entity 'ldquo' not defined
Below is a rendering of the page up to the first error. </warnings>
The page was itself apparently rendered well.
Is this a problem no a bit old Safari? (seems safari process the document as xml?)
In my opinion, if MacPorts is still supporting OS S 10.3, the main page should be ready for Safari v.1.3.2, the latest Safari for OS X 10.3.
Any comments or suggestions?
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
js wrote:
The problem is Safari 1.3 is processing the page as an XML document, even though, just as you pointed out, it's really a XHTML. The server seems returning the right HTTP header, "Content-Type: application/xhtml+xml; charset=utf-8", so I think it's actually a Safari's problem.
This may be related to http://trac.macosforge.org/projects/macports/ticket/14062 Rainer
http://www.456bereastreet.com/archive/200410/safari_and_xhtml/ On Wed, Feb 27, 2008 at 1:10 AM, Rainer Müller <raimue@macports.org> wrote:
js wrote:
The problem is Safari 1.3 is processing the page as an XML document, even though, just as you pointed out, it's really a XHTML. The server seems returning the right HTTP header, "Content-Type: application/xhtml+xml; charset=utf-8", so I think it's actually a Safari's problem.
This may be related to http://trac.macosforge.org/projects/macports/ticket/14062
Rainer
On Feb 26, 2008, at 11:03, js wrote:
On Wed, Feb 27, 2008 at 1:10 AM, Rainer Müller wrote:
js wrote:
On 2/25/08, Juan Manuel Palacios wrote:
On Feb 23, 2008, at 7:17 AM, Ryan Schmidt wrote:
Sounds like a bug. Though it may surprise some people to learn it, "nbsp" etc. are not valid entities in XML. Please file a ticket in our issue tracker so we can correct this.
If I'm not mistaken, they are in XHTML, as added by the DTD's:
http://www.w3.org/TR/xhtml-modularization/ dtd_module_defs.html#a_module_XHTML_Latin_1_Character_Entities (again, if I'm not mistaken, that document applies to XHTML 1.1, which is what I used for the website)
But, of course, I could be reading that wrong, since you know much more about the subject than me ;-) In any case, would using the unicode code points fix the problems?
The problem is Safari 1.3 is processing the page as an XML document, even though, just as you pointed out, it's really a XHTML. The server seems returning the right HTTP header, "Content-Type: application/xhtml+xml; charset=utf-8", so I think it's actually a Safari's problem.
This may be related to http://trac.macosforge.org/projects/macports/ticket/14062
http://www.456bereastreet.com/archive/200410/safari_and_xhtml/
Sorry, Juan Manuel; you're right, I was thinking of XML, where those entities aren't defined. Looks like they are defined in XHTML, but Safari 1.x has a bug. I am moving this week, but next week I will have access to a Power Mac G3 on which I can install Panther and try to tackle this, if nobody else has by then.
participants (4)
-
js
-
Juan Manuel Palacios
-
Rainer Müller
-
Ryan Schmidt