Re: font name not decoded in the output of describe-font

["Stephen J. Turnbull" <stephen@xemacs.org>]

Miles Bader writes:
 > "Stephen J. Turnbull" <stephen@xemacs.org> writes:
 > > I haven't found a specification that says so myself, but Aidan Kehoe
 > > says it's clear from the source of fontconfig that it's UTF-8.  I
 > > can't imagine why that would change in the future so it's probably
 > > safe to assume it (at least for user presentation purposes).
 > 
 > Anyway, since in practice everything uses utf-8, surely it's better to
 > assume that until a better solution is found, than returning raw
 > undecoded font names ?

Indeed.  The question in my mind is how defensive to be about checking
for UTF-8 compatibility.  I think it's OK to just decode willy-nilly
and let the errors come if they will (because I'm quite sure they won't).