FMSLogo Code

Remove five and six octect sequences from read_char_utf8
Although these follow the pattern, they are not included in UTF-8,
which is only for encoding 16-bit characters.

Fix GetConfigurationString() to work on the Unicode GNU/Linux build.

Print out procedure bodies at UTF-8.
This a stop-gap solution to fixing SAVE and the editor until g_Writer
can hold the character encoding to use (and possibly implement the
character encoding functionality).

Add a UTF-8 BOM to the temp files used to store the workspace for editing.
This will be used to instruct the reader to interpret it as UTF-8.

Add a UTF-8 BOM to whatever files an editor writes.

Explicitly write characters in UTF-8, instead of leaving it to the whim of the CRT.

Carry the character encoding of loadstream along with loadstream.
This makes it possible for TO, which continue reading from loadstream, to read the procedure definitions correctly.

Add more explanation to a comment

Apply the BOM sniffing logic to fileopen(), which is used by File -> Open.

Try to fix the problems with committing a UTF-16LE test case.