I checked the page. At first glance examination it does not seem to record anything. Even though the key part of the code is very short:
s = s.replace( /\u2018|\u2019|\u201A|\uFFFD/g, “’” );
s = s.replace( /\u201c|\u201d|\u201e/g, ‘”’ );
s = s.replace( /\u02C6/g, ‘^’ );
s = s.replace( /\u2039/g, ‘<’ );
s = s.replace( /\u203A/g, ‘>’ );
s = s.replace( /\u2013/g, ‘-’ );
s = s.replace( /\u2014/g, ‘—’ );
s = s.replace( /\u2026/g, ‘...’ );
s = s.replace( /\u00A9/g, ‘(c)’ );
s = s.replace( /\u00AE/g, ‘(r)’ );
s = s.replace( /\u2122/g, ‘TM’ );
s = s.replace( /\u00BC/g, ‘1/4’ );
s = s.replace( /\u00BD/g, ‘1/2’ );
s = s.replace( /\u00BE/g, ‘3/4’ );
s = s.replace(/[\u02DC|\u00A0]/g, “ “);
FR should be able to easily incorporate it into their code.
W3C Internationalization CheckerHere is a pic of the line break issue I currently have.
The html tag has no language attributeWhy should I use the language attribute in web pages?
For example, fonts or line spacing may need to change to accommodate different alphabets, style-generated quotation marks may need to be different by language, emphasis may need to be expressed in language dependent ways, etc.Other typographic and layout features that are affected by language include line-breaking, justification, and case conversion, and more are coming as the specifications develop.