Thus said The Tick on Wed, 29 Mar 2017 15:47:32 -0500: > If I edit the file, of course the utf-8 copyright symbol is garbled. > Furthermore, there is no way I can insert a utf-8 character.
My editor (nvi) allows me to insert UTF-8 characters by typing the ASCII character, then by pressing ctrl-x followed the 2-digit value 00 (for a null byte). > You can copy and paste the "Peggle®" and paste it into notepad. When you > save the file, you will see that the "registered" character is a single > character with the hex value \xAE. The problem here is not one of ``which character is this?'' but rather one of ``which encoding should be used to render the character visible?'' \xAE is not ASCII. ASCII ranges from \x00 to \x7f, but only \x20 to \x7e are ``printable'' characters. That being said, if you want to make your browser show you the character correctly, you need to tell your browser that the data it is viewing is not UTF-8 (the likely default). I added a file to a test repostory that had a single \xAE character in it. Then I ran fossil server and looked at the file in my browser. It showed up as a circle with ? inside because it didn't know what to do with it. So I then clicked on View->Text Encoding->Western and magically, and instantaneously, that broken character now shows up as it should. Andy -- TAI64 timestamp: 4000000058dc768b _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
