Remove unnecessary localBiblio entries

index.html

@@ -48,66 +48,6 @@
           github:       "w3c/charmod-norm",
 
 		  localBiblio: {
-		  "UTS18": {
-		    title: "Unicode Technical Standard #18: Unicode Regular Expressions",
-			href: "https://unicode.org/reports/tr18/",
-			authors: [ "Mark Davis", "Andy Heninger" ]
-		},
-
-		"ISO10646": {
-			title: "Information Technology - Universal Multiple- Octet Coded CharacterSet (UCS) - Part 1: Architecture and Basic Multilingual Plane",
-			authors: [ "ISO/IEC10646-1:1993" ],
-			note: "The current specification also takes into consideration the first five amendments to ISO/IEC 10646-1:1993. Useful roadmaps (http://www.egt.ie/standards/iso10646/ucs-roadmap.html) show which scripts sit at which numeric ranges."
-		},
-
-		"UTS10": {
-			title: "Unicode Technical Standard #10: Unicode Collation Algorithm",
-			href: "https://www.unicode.org/reports/tr10/",
-			authors: [ "Mark Davis", "Ken Whistler", "Markus Scherer" ]
-		},
-
-        "UAX9": {
-            title: "Unicode Standard Annex #9: Unicode Bidirectional Algorithm",
-            href: "https://unicode.org/reports/tr9/",
-            authors: [ "Mark Davis", "Aharon Lahnin", "Andrew Glass" ]
-        },
-
-		"UAX11": {
-		    title: "Unicode Standard Annex #11: East Asian Width",
-		    href: "https://www.unicode.org/reports/tr11/",
-		    authors: [ "Ken Lunde 小林劍" ]
-		},
-
-		"UAX29": {
-			title: "Unicode Standard Annex #29: Unicode Text Segmentation",
-			href: "https://www.unicode.org/reports/tr29/",
-			authors: [ "Mark Davis" ]
-		},
-
-		"UTS39": {
-		    title: "Unicode Technical Standard #39: Unicode Security Mechanisms",
-		    href: "https://www.unicode.org/reports/tr39/",
-		    authors: [ "Mark Davis", "Michel Suignard" ]
-		},
-
-		"UTR36": {
-			title: "Unicode Technical Report #36: Unicode Security Considerations",
-			href: "https://www.unicode.org/reports/tr36/",
-			authors: [ "Mark Davis", "Michel Suignard" ]
-		},
-
-		"UTR50": {
-		    title: "Unicode Technical Report #50: Unicode Vertical Text Layout",
-		    href: "https://www.unicode.org/reports/tr50/",
-		    authors: [ "Koji Ishii 石井宏治" ]
-		},
-
-		"UTR51": {
-		    title: "Unicode Technical Report #51: Unicode Emoji",
-		    href: "https://www.unicode.org/reports/tr51/",
-		    authors: [ "Mark Davis", "Peter Edberg" ]
-	    },
-
 	    "STRING-SEARCH": {
 			title: "Character Model for the World Wide Web: String Searching",
 			href: "https://w3c.github.io/string-search/",
@@ -116,9 +56,9 @@
 
 		"ASCII": {
 		    title: "ISO/IEC 646:1991, Information technology -- ISO 7-bit coded character set for information interchange",
-		    href:  "http://www.ecma-international.org/publications/standards/Ecma-006.htm",
+		    href:  "https://www.ecma-international.org/publications-and-standards/standards/ecma-6/",
 		    isoNumber: "ISO/IEC 646:1991",
-		    note:  "This standard defines an International Reference Version (IRV) which corresponds exactly to what is widely known as ASCII or US-ASCII. ISO/IEC 646 was based on the earlier standard ECMA-6. ECMA has maintained its standard up to date with respect to ISO/IEC 646 and makes an electronic copy available at http://www.ecma-international.org/publications/standards/Ecma-006.htm "
+		    note:  "This standard defines an International Reference Version (IRV) which corresponds exactly to what is widely known as ASCII or US-ASCII. ISO/IEC 646 was based on the earlier standard ECMA-6. ECMA has maintained its standard up to date with respect to ISO/IEC 646 and makes an electronic copy available at https://www.ecma-international.org/publications-and-standards/standards/ecma-6/ "
 	    },
 
 	}
@@ -888,7 +828,7 @@ <h4>Canonical vs. Compatibility Equivalence</h4>
             points, mainly for compatibility with legacy character encodings. In 
 		  many cases these variations are associated with the Unicode properties 
 		  described in <cite>East Asian Width</cite> [[UAX11]]. See also <cite>Unicode 
-		  Vertical Text Layout</cite> [[UTR50]] for a discussion of vertical text 
+		  Vertical Text Layout</cite> [[UAX50]] for a discussion of vertical text 
 		  presentation forms.</p>
           <p>In the case of characters with compatibility decompositions, such
             as those shown above, the <span class="qchar">K</span> Unicode
@@ -1578,7 +1518,7 @@ <h3>Invisible Unicode Characters</h3>
       </section>
       <section id="emojiSequences">
       <h3>Emoji Sequences</h3>   
-      <p>A newer feature of Unicode are the emoji characters. In [[UTR51]], Unicode describes these as:</p>   
+      <p>A newer feature of Unicode are the emoji characters. In [[UTS51]], Unicode describes these as:</p>   
 
       <p class="quote">Emoji are pictographs (pictorial symbols) that are typically presented in a colorful cartoon 
          form and used inline in text. They represent things such as faces, weather, vehicles and buildings, 
@@ -1592,7 +1532,7 @@ <h3>Emoji Sequences</h3>
 		  U+1F468 U+200D U+1F469 U+200D U+1F467 U+200D U+1F467</span> results in a composed
 		  emoji character for a "family: man, woman, girl, girl" on systems that support this kind of 
 		  composition. Many common emoji can <em>only</em> be formed using ZWJ sequences. For more 
-		  information, see [[UTR51]].</p>
+		  information, see [[UTS51]].</p>
 
 	  <p>Emoji characters can be followed by emoji modifier characters. These modifiers allow for the selection of skin tones for emoji that represent people. These characters are normally invisible modifiers that follow the base emoji that they modify. For example: &#x1f468;&nbsp;&#x1f468;&#x1f3fb;&nbsp;&#x1f468;&#x1f3fc;&nbsp;&#x1f468;&#x1f3fd;&nbsp;&#x1f468;&#x1f3fe;&nbsp;&#x1f468;&#x1f3ff;</p>