0-issue

@rkd77 Tested on 0.13.0, its the same there! I wonder if there is any other unicode shaping library that you could use, or how links is able to display these...

@rkd77 For 1) I get an error "Bad url syntax" with elinks, but not with links. For 2) (the -dump option): same problem. The output from links has correct S...

@rkd77 Didn't resolve it. One comment I have is: a lot of unicode seems to just render fine. It's only a subset that doesn't. If you could think of a...

@rkd77 Am not a unicode/utf-8 expert and we might end up doing a lot of back and forth that way. Don't you want to add a fprintf or two to...

@rkd77 Ok I have something for you! I used the test [document](https://github.com/fabrizioschiavi/pragmatapro/blob/master/useful_files/All_chars.txt) from [pragmatapro](https://github.com/fabrizioschiavi/pragmatapro)'s repository. As that is one of the most comprehensive terminal fonts, and the test file has...

@rkd77 Here we go, this is what the log file has: ``` goto charsets.c:758:utf8_to_unicode charsets.c:751:utf8_to_unicode ```

@rkd77 Here's the output: ``` goto charsets.c:759:utf8_to_unicode str[0]=195 str[1]=32 str[1] & 0xc0 = 0 charsets.c:751:utf8_to_unicode str[0]=195 ``` Clang, as gcc/g++ is actually clang/clang++ on Apple macOS. This is also the...

@rkd77 It's the same stderr output as before: ``` goto charsets.c:759:utf8_to_unicode str[0]=195 str[1]=32 str[1] & 0xc0 = 0 charsets.c:751:utf8_to_unicode str[0]=195 ``` stdout has this: ``` U+00C0 1À2Á3Â4Ã5Ä6�7Æ8Ç9È ```

@rkd77 One observation: If I open the document without -dump, the character renders correctly (no error is seen). Are you sure the path taken by application for -dump is the...

@rkd77 Here's the log: [chars.log](https://github.com/rkd77/elinks/files/12217281/chars.log). Not sure if it matters, here's the entire build log: [build.log](https://github.com/rkd77/elinks/files/12217338/build.log).