XHTML compatibility problem with Safari

[nickshanks]

Safari currently does not parse DTDs for XML content types. Upon changing my html_type to application/xhtml+xml, all named entities encountered caused fatal errors because the <!ENTITY ...> tags were never parsed. The solution is simply to search/replace all &nbsp; &hellip; &raquo; and &rsaquo; tags with their equivalent NCRs. I've not checked every admin page, there may be others lurking but those were the obvious ones.

There is also a <td> Default </tr> in link-categories.php. A </td> is missing.

[foolswisdom]

Closing as invalid.

Thank you for particating in WordPress!

The problem seems to be much more fundamental and complicated then this and your proposed solution would decrease maintainability.
​http://trac.wordpress.org/ticket/3406
​http://comox.textdrive.com/pipermail/wp-hackers/2006-December/009848.html

Regarding the misplaced </td>, thank you. I will file this as a separate ticket.

[matt]

This is different than the other tickets and something we should think about for 2.2. I don't think there would be any decrease in maintainability by using numeric entities, we do it already most everywhere.

[nickshanks]

I have since been through every admin page in it's default state (initalised database) and those are the only four named entities that trip up Safari.

[nickshanks]

Proposesd fix

[nickshanks]

Note that if you view the diff with trac, the file wp-content/themes/default/functions.php will only show a remove line. That file has DOS line endings, unlike all the others, and SVN produces a diff file with alternating empty lines, which trac seems unable to handle.

I would like to see this fix get into 2.1 si possis.

[nickshanks]

Proposesd fix

[nickshanks]

Added a new patch. This also changes uarr/darr/larr/rarr to NCRs, and converts the two files wp-content/themes/default/functions.php and wp-includes/js/tinymce/plugins/paste/editor_plugin.js to UNIX line endings so that patch(1) can apply diffs. These files will look odd in trac's diff viewer.

[nickshanks]

New fix, after rboren's svn:eol-style corrections

[markjaquith]

Andy, can you take a look and make sure the TinyMCE-related replacements won't cause problems?

[nickshanks]

To re-create the patch, find/replace the following with NCRs:
nbsp, hellip, raquo, laquo, rsaquo, uarr, darr, larr, rarr

Then revert the file wp-includes/formatting.php (which should not be changed)
Then revert the file wp-includes/js/tinymce/themes/advanced/jscripts/charmap.js
Then edit that same charmaps.js file to restore one &nbsp; to &#160; change towards the bottom.

[foolswisdom]

WORKAROUND
NCR Everywhere ​mentioned on support forum

[azaozz]

This seems to be a problem with Safari 1.2. It seems it has been fixed in newer versions.