Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [platform-ua-dev] New parser in 3.3?

Refer to Eclipse Bug 189192, which addresses the Sax Parse errors for named
entities in Eclipse 3.3. The bug has been fixed for the 3.4 release.

Named entities such as   and ® were parsed correctly in 3.2 and
will be in 3.4. The named entities are, in fact, referenced in the following
dtd:

http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd



Wendy Beren
Active Endpoints
www.active-endpoints.com
"Smart SOA Orchestration Powered by ActiveBPEL"



-----Original Message-----
From: platform-ua-dev-bounces@xxxxxxxxxxx
[mailto:platform-ua-dev-bounces@xxxxxxxxxxx] On Behalf Of Eric Sirois
Sent: Wednesday, October 31, 2007 9:26 PM
To: Eclipse Platform User Assistance component developers list.
Subject: Re: [platform-ua-dev] New parser in 3.3?

Hi Seth,

I think I opened a defect a while back regarding the Eclipse adding 
empty javascript tags.  If the sample in the defect

<script 
language="javascript" src="scroller.js" />

is one that you added, that is not valid the </script> endtag is required as
well as the type attribute.  
Yes, the new Equinox HTTP/Jetty architecture actually validates all content
it serves up.

The other error in the defect is valid as well.  &nbsp is a user defined
entity and not defined in the XHTML DTD.
It should be replaced with #xA0; or #160;


Here is a webpage that helps to answer questions regarding
nbsp;

http://www.stylusstudio.com/xsllist/200112/post20640.html

Even the HTML 4 spec defines the entity nbsp as #160; (#160 and #A0 are
equivalent)

http://www.w3.org/TR/html401/sgml/entities.html

Eric




Seth Packham wrote:
>
> Hi,
>
> Can someone explain the difference in the XML parser being used in 
> Eclipse 3.3 help? I've opened bug 205473 about a problem with the 
> parsing -- https://bugs.eclipse.org/bugs/show_bug.cgi?id=205473
>
> And my co-worker just reported some other org.xml.SAXParser exceptions 
> on XHTML pages. It seems to be doing some strict XML checking and even 
> changing tags at runtime (as mentioned in my bug).
>
> Thanks,
> Seth Packham
>
> Jazz Information Architect
> Rational User Assistance
> packham@xxxxxxxxxx
> 1-919-543-7415 (T/L 441-7415) 	> Tracker 
> <http://idbuild.rtp.raleigh.ibm.com/tracker/>
> > UA Design Documents wiki 
> <https://w3.webahead.ibm.com/w3ki/display/ratluaplans/UADD>
> > UA Guidelines infocenter 
> <http://idbuild.rtp.raleigh.ibm.com:8084/help/index.jsp>
> > Rational UA content plans 
> <https://w3.webahead.ibm.com/w3ki/display/ratluaplans/Home>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> platform-ua-dev mailing list
> platform-ua-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/platform-ua-dev
>   


_______________________________________________
platform-ua-dev mailing list
platform-ua-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-ua-dev



Back to the top