On Jan 17, 2005, at 3:25 PM, Christophe Rhodes wrote:
> Oh, my word. PAIN AND SUFFERING.
> OS X's terminal defaults to utf-8 input/output, so that's what SBCL
> does. How are you setting up your X11 to deal with latin-1
> input/output? (OS X doesn't provide the posix-defined nl_langinfo()
> method for querying the system ourselves for natural language
> environmental questions).
It might be slightly more painful than you think, Christophe. OS X 10.3
provides nl_langinfo, but OS X 10.2 does not. However, 10.3's version
lies: even when the terminal is set to UTF-8, it returns the equivalent
of iso latin 1. Since I couldn't figure out a good solution to this
problem, I decided that always returning UTF-8 was a good enough
solution, as most other programs on OS X expect and know how to deal
The solution to this problem might just be to use a unicode xterm.