rkd77

@amanvm you can prepare test cases and save dumps (elinks --dump) . And show hex view of these dumps.

@amanvm There are many places where it can break. First I want to know how it "looks" like. In elinks F9 -> File -> Save formatted document (save with .txt...

Another question. How is rendered plain text with this character? Also "tofu" or ok?

@amanvm on branch utf I added debug statements and test/chars.txt. Please compile, and check elinks -dump chars.txt 2> log and show log.

Added more debug statements. Could you rerun test? Which compiler is it?

Added another commit to the utf branch. I disabled maybe_preformat_hook in dump to exclude it from suspected. Second issue is str[1]=32 (space). In chars.txt I replaced spaces with digits, so...

dump interprets document as html, normal view as plain text. You can check latest commits and show log. I'm slowly running out of ideas.

@amanvm, thanks, could you continue? I make mistake in commit log, but we are closer. git pull, compile and the same log.

For now, files are written and read from ~/.config/elinks/ It is up to user to move/copy files there. Location of global configuration was not touched.

If ELINKS_CONFDIR is set, to use it makes sense. Do you know anybody who has set ELINKS_CONFDIR? But (2), no. Users can copy files to ~/.config/elinks . It takes a...