In following up on bug 264016, I found that this bug no longer occurs (in unstable). A font with an iso8859-1 displays just fine in my UTF-8 locale. Andrew