You are not logged in

See also bug 38882 for including UTF-8 content, and bug 38883 for tracking character set and graphics modifications in the text blocks.

In addition to these concerns, though, it might be desirable to add an option allowing non-control high bytes from the single-byte ISO-8859-*/Ecma-48 character encodings to be passed through as-is, without respect to whether character sets have been designated to GR, etc. IOW, trust that the viewer is already set up with the right latinX encoding, and emit the characters as they're found.

This is obviously much easier to implement than character encoding state tracking (as in bug 38883), and slightly easier to implement than UTF-8 support (bug 38882).