Ticket #61 (closed defect: fixed)

Opened 9 years ago

Last modified 8 years ago

Ignored unencodeable characters mess up the terminal.

Reported by: judah Owned by:
Priority: minor Milestone: 0.6.*
Version: Keywords:


In Terminal.app, with a UTF-8 encoding, use runghc examples/Test.hs to enter a line of text with several Greek letters in it.

Then, open a new terminal with the Western (ISO Latin 1) encoding and export LANG=fr_FR.ISO8859-1. Run Test.hs again and page through the old command history. The Greek letters are not encoded, so the redrawing commands mess up and delete the prefix "0:".

Change History

Changed 9 years ago by judah

Workaround is probably to encode the bad characters as '?'.

Need to investigate:

  • Can we always assume that the byte '?' is a valid encoding of a character?
  • Will this work with both encoding and decoding?

Changed 9 years ago by judah

  • milestone set to 0.6.*

Changed 9 years ago by judah

The various encodings I've checked (UTF-8, EUC, KOI8, etc.) all encode '?' as the single byte 0x3f. So the above solution is fine (and is a desireable feature on its own).

Remember to update the Unicode wiki page to say that we only support encodings which use a single byte for both '\n' and '?'.

Changed 8 years ago by judah

  • status changed from new to closed
  • resolution set to fixed

This was fixed in

Note: See TracTickets for help on using tickets.