[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: font name not decoded in the output of describe-font
From: |
Stephen J. Turnbull |
Subject: |
Re: font name not decoded in the output of describe-font |
Date: |
Wed, 17 Dec 2008 13:37:58 +0900 |
Miles Bader writes:
> "Stephen J. Turnbull" <address@hidden> 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).
- font name not decoded in the output of describe-font, brep, 2008/12/13
- Re: font name not decoded in the output of describe-font, Jason Rumney, 2008/12/13
- Re: font name not decoded in the output of describe-font, Miles Bader, 2008/12/15
- Re: font name not decoded in the output of describe-font, jasonr, 2008/12/15
- Re: font name not decoded in the output of describe-font, Kenichi Handa, 2008/12/15
- Re: font name not decoded in the output of describe-font, Stephen J. Turnbull, 2008/12/16
- Re: font name not decoded in the output of describe-font, Miles Bader, 2008/12/16
- Re: font name not decoded in the output of describe-font,
Stephen J. Turnbull <=
- Re: font name not decoded in the output of describe-font, Kenichi Handa, 2008/12/19
Re:Re: font name not decoded in the output of describe-font, brep, 2008/12/14