Merge pull request #24 from hannob-forks/links3

Change links from http to https

Author: hartwork

content/pages/custom-encodings.md

@@ -21,7 +21,7 @@ encoding.
 
 A _character encoding_ in Expat is a combination of tables and
 functions that translates a sequence of bytes into [Unicode
-codepoints](http://unicode.org/glossary/#code_point) and from there to
+codepoints](https://unicode.org/glossary/#code_point) and from there to
 UTF-8 or UTF-16 (as configured at compile time) for the library's
 internal use.  Expat natively understands several encodings: UTF-8,
 ASCII, Latin-1 (aka ISO/IEC 8859-1) and UTF-16 (big- and little-endian).

content/pages/doc.md

@@ -34,5 +34,5 @@ This page is meant to serve as an index of Documentation on Expat.
 # External Articles and References
 
 * [James Clark's original Expat page](http://www.jclark.com/xml/expat.html), for Expat 1.2 and earlier
-* [Introductory article "Using Expat"](http://www.xml.com/pub/1999/09/expat/index.html)
+* [Introductory article "Using Expat"](https://www.xml.com/pub/1999/09/expat/index.html)
   by [Clark Cooper](https://www.xml.com/pub/au/43)

content/pages/encodings.md

@@ -19,7 +19,7 @@ maintainers understand what it does.
 
 A _character encoding_ in Expat is a combination of tables and
 functions that translates a sequence of bytes into [Unicode
-codepoints](http://unicode.org/glossary/#code_point) and from there
+codepoints](https://unicode.org/glossary/#code_point) and from there
 to UTF-8 or UTF-16 (as configured at compile time).  This includes
 functions to determine various syntactic elements of XML, such as
 whether a byte sequence translates to a codepoint that would be valid
@@ -329,7 +329,7 @@ use them.  The macro definitions for the 16-bit encodings still use
 the `type` table as an optimisation, but use the function
 `unicode_byte_type()` to convert the input into a byte type.  Slightly
 different logic is used to deal with [surrogate
-pairs](http://unicode.org/glossary/#surrogate_pair), and as a result
+pairs](https://unicode.org/glossary/#surrogate_pair), and as a result
 none of the functions are needed.
 
 

content/pages/string-pools.md

@@ -185,7 +185,7 @@ block can be hanging off `blocks`.  That makes linking and unlinking
 simple.
 
 The pointer-fiddling for `pool->blocks` and `pool->freeBlocks` is
-[fairly standard linked-list](http://www.learn-c.org/en/Linked_lists)
+[fairly standard linked-list](https://www.learn-c.org/en/Linked_lists)
 stuff.  More interesting is the initialisation of `start` (to the
 start of the available memory in the block), `end` (calculated from
 the number of characters available) and `ptr` (same as `start`,
@@ -762,7 +762,7 @@ usage patterns unnecessarily hard, as in this case.
 <a name="cunning">3</a>: something is described as cunning if it is
 very clever, often deceitful.  In recent years it has come to have
 sarcastic overtones, thanks to
-[Blackadder](http://www.bbc.co.uk/programmes/b006xxw3); Baldrick's cry
+[Blackadder](https://www.bbc.co.uk/programmes/b006xxw3); Baldrick's cry
 of "I have a cunning plan, milord" generally introduced a bizarre,
 complicated and very stupid suggestion.
 

content/pages/walkthrough1.md

@@ -559,7 +559,7 @@ sequence of three bytes.  Its case checks that there are at least
 three bytes available, then calls through the `isNmstrt3` function
 pointer in the encoding.  This time `utf8_isNmstrt3()` as it becomes
 is a real function, one that uses macros to turn the UTF-8 into
-a [Unicode codepoint](http://unicode.org/glossary/#code_point) and
+a [Unicode codepoint](https://unicode.org/glossary/#code_point) and
 look up that codepoint (an integer in the range 0–1114111
 (0x10ffff in hexadecimal), or rather 2048–65535
 (0x0800–0xffff in hex) given that it comes from a three-byte

content/pages/walkthrough2.md

@@ -321,7 +321,7 @@ character permitted in XML.  That includes the ASCII [control
 characters](https://en.wikipedia.org/wiki/Control_character) other
 than whitespace characters, and bytes that would start a four byte
 sequence that would encode a [Unicode
-codepoint](http://unicode.org/glossary/#code_point) outside the
+codepoint](https://unicode.org/glossary/#code_point) outside the
 permitted range.
 
 `BT_MALFORM` is slightly different; it is reserved for 0xFE and 0xFF,