Re: "iconv: illegal input sequence" in VM
Ar an seachtú lá is fiche de mí Márta, scríobh Stephen J. Turnbull:
On Sat, Mar 24, 2012 at 1:59 AM, Charles G Waldman
<cgw(a)alum.mit.edu> wrote:
> 1) Should the bullet char (composed of bytes 226, 128, 162) display
> in XEmacs? Is this font-dependent?
It should, but AFAIK it won't. Aidan did some work to ensure
that Unicode characters get into the buffer, but they don't
display correctly on X11 or in a terminal AFAICT. Maybe
that's just me. :-)
Many of them (in particular, very common characters like this one) display
fine on X11 and in a terminal (make sure your language environment reflects
the encoding of the terminal, or set the terminal encoding explicitly).
They will have trouble under XFT, which Charles appears to be using, and the
long-term solution to this is to merge Jeff Sparke’s GTK2 support, and for
me to fix some poor architectural decisions about what level textual runs
should be split when it comes to character coverage. Here’s some code to
test:
(decode-coding-string (map 'string #'int-char '(226 128 162)) 'utf-8)
=> "•"
--
‘Iodine deficiency was endemic in parts of the UK until, through what has been
described as “an unplanned and accidental public health triumph”, iodine was
added to cattle feed to improve milk production in the 1930s.’
(EN Pearce, Lancet, June 2011)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta