Warnings when I visit http://www.macports.org/ in Safari v.1.3.2

[Ryan Schmidt]

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.