My aim was not to rush.
I'm currently looking at what needs to be implemented in WebKit to support 
MathML 3.
I noticed that a lot of entities are not implemented and I first thought it was 
easy to implement.

After this discussion on the mailing list, it appears not to be so simple.

I filled a bug to continue the discussion and track the progresses in a 
refactoring of the entity parser:

François Sausset

Le 11 juil. 2010 à 04:21, Maciej Stachowiak a écrit :

> On Jul 10, 2010, at 9:36 AM, Alexey Proskuryakov wrote:
>> 10.07.2010, в 04:49, Maciej Stachowiak написал(а):
>>> Go with the HTML5 / MathML 3 definitions for everything. Our XHTML 
>>> implementation targets XHTML5, not XHTML 1.0.
>> I think that xml-entity-names and HTML5 made a poor choice changing the 
>> semantics of ⟩ and ⟨ (they used to be CJK punctuation, and now 
>> they are suddenly math). These are rendered differently. We should probably 
>> take a pragmatic approach, and avoid rushing to be the first to implement 
>> this aspect of the specs.
> I agree we shouldn't rush on potential compatibility-breaking changes, if we 
> can get someone else to do some testing for us first. However I believe 
> Firefox dev builds have the new meanings of ⟩ and ⟨. They haven't 
> discovered a problem yet, as far as I know.
> Regards,
> Maciej

webkit-dev mailing list

Reply via email to