all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Miles Bader <miles@gnu.org>
Cc: stephen@xemacs.org, jasonr@f2s.com, brep@163.com, emacs-devel@gnu.org
Subject: Re: font name not decoded in the output of describe-font
Date: Fri, 19 Dec 2008 14:44:22 +0900	[thread overview]
Message-ID: <E1LDY9u-0007mR-Qj@etlken.m17n.org> (raw)
In-Reply-To: <buo8wqg8psl.fsf@dhapc248.dev.necel.com> (message from Miles Bader on Tue, 16 Dec 2008 17:52:58 +0900)

In article <buo8wqg8psl.fsf@dhapc248.dev.necel.com>, Miles Bader <miles@gnu.org> 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 ?

Ok, I've just installed a code to decode/encode font names
property for x, xft, ftx font-backends.

The decoder checks the validity of utf-8 sequence.

---
Kenichi Handa
handa@m17n.org




  parent reply	other threads:[~2008-12-19  5:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-13 14:18 font name not decoded in the output of describe-font brep
2008-12-13 17:55 ` Jason Rumney
2008-12-16  1:36   ` Miles Bader
2008-12-16  1:46     ` jasonr
2008-12-16  4:44       ` Kenichi Handa
2008-12-16  8:17         ` Stephen J. Turnbull
2008-12-16  8:52           ` Miles Bader
2008-12-17  4:37             ` Stephen J. Turnbull
2008-12-19  5:44             ` Kenichi Handa [this message]
2008-12-14 14:16 ` brep

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1LDY9u-0007mR-Qj@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=brep@163.com \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@f2s.com \
    --cc=miles@gnu.org \
    --cc=stephen@xemacs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.