Closed Bug 145810 Opened 22 years ago Closed 22 years ago

Add XHTML+MathML+SVG in the recognized catalog list

Categories

(Core :: XML, defect)

Product:
Core
Component:
XML
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: rbs, Assigned: rbs)

References

(
URL
)

Details

Attachments

(1 file)

one-liner patch
844 bytes, patch
hjtoi-bugzilla
: review+
jst
: superreview+
Details | Diff | Splinter Review 
From the W3C site:

"First Working Draft of "An XHTML + MathML + SVG Profile" published
30 April 2002: The HTML Working Group and the SVG Working Group have worked 
together to publish the first Working Draft of "An XHTML + MathML + SVG 
Profile." An XHTML+MathML+SVG profile is a profile that combines XHTML 1.1,
MathML 2.0, and SVG 1.1 together. This profile enables mixing XHTML, MathML and 
SVG in the same document using XML namespaces mechanism, while allowing 
validation of such a mixed-namespace document. Read about the HTML Activity
and the Graphics Activity."

Some people might already want to try the DOCTYPE and it isn't a big deal to add 
it in the catalog list:

<!DOCTYPE html PUBLIC
   "-//W3C//DTD XHTML 1.1 plus MathML 2.0 plus SVG 1.1//EN"
   "http://www.w3.org/2002/04/xhtml-math-svg/xhtml-math-svg.dtd">

Without it in the catalog list, documents that try to use it are getting a fatal 
error on entity names.

Although the prose of the spec may change, it is unlikely that the FPI will 
change, so adding it now isn't that risky re:forward compatibility.
Attached patch one-liner patch — — Splinter Review 

    
    

    
  
Does the mathml.dtd include all the entities svg.dtd does?

    
    

    
  
No worries, svg.dtd only has one line:
http://lxr.mozilla.org/seamonkey/source/layout/svg/base/src/svg.dtd#37

This line is aimed at making the SVG namespace implicit, but this way of doing so
was discouraged (that's why the SVG entry in the catalog list is actually
associated to the weird "-//W3C//DTD SVG 20001102//EN"). bbaetz said in bug
113400 that it was for backward compatibility with an earlier SVG draft, maybe
that entry is not even necessary anymore these days.
Status: NEW → ASSIGNED

    
    

    
  
Comment on attachment 84332 [details] [diff] [review]
one-liner patch

Ok, in that case r=heikki

        Attachment #84332 -
        Flags: review+

    
    

    
  
Yeah, the svg line could possibly be removed. Given the lack of work being done
on svg ATM, though, we may as well support the older stuff.

    
    

    
  
As the editor of "An XHTML+MathML+SVG Profile", I can assure you that the FPI
for XHTML+MathML+SVG is extremely unlikely to change.  Actually one of the
motivation behind this specification is to allow browsers that support XHTML,
MathML and SVG, such as SVG-enabled build of Mozilla and Amaya, to refer to a
DTD so that they can use XHTML/MathML entities.  I wrote a similar patch and
recompiled Mozilla, and so far it's working fine.

    
    

    
  
Comment on attachment 84332 [details] [diff] [review]
one-liner patch

jst, sr=?

    
    

    
  
Comment on attachment 84332 [details] [diff] [review]
one-liner patch

sr=jst

        Attachment #84332 -
        Flags: superreview+

    
    

    
  
Checked in.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED

    
  
Summary: Add XHML+MathML+SVG in the recognized catalog list → Add XHTML+MathML+SVG in the recognized catalog list

    
  
QA Contact: petersen → rakeshmishra

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: