From: Kenichi Handa <handa@m17n.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: jasonr@gnu.org, emacs-devel@gnu.org
Subject: Re: font-backend branch
Date: Sun, 04 May 2008 20:52:15 +0900 [thread overview]
Message-ID: <E1JsclL-0005eq-0O@etlken.m17n.org> (raw)
In-Reply-To: <jwvbq3mubub.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sat, 03 May 2008 20:57:38 -0400)
In article <jwvbq3mubub.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> Is depending on the format of the font name returned by frame-parameter
>>> widespread?
> > I don't know, but I got at least one bug-report as attached.
> The bug report doesn't necessarily point to the need to support XFLD,
> but rather that (frame-parameter <foo> 'font) should return something
> that is considered as a font so it can be passed to x-list-fonts and
> things like that.
>
> I.e. we can address the issue by adapting x-list-fonts to accept
> whichever format is output by (frame-parameter <foo> 'font).
Yes. But, modifying all of "x-list-fonts and things like
that" can't be done quickly, and as it is not that urgent
task, we can leave it until later. On the other hand,
setting FONT_NAME_INDEX of font-vector to a font name of
XLFD format can be done easily and quickly.
---
Kenichi Handa
handa@ni.aist.go.jp
next prev parent reply other threads:[~2008-05-04 11:52 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 4:24 font-backend branch Kenichi Handa
2008-04-30 6:04 ` Stefan Monnier
2008-04-30 7:39 ` Kenichi Handa
2008-04-30 11:38 ` Juanma Barranquero
2008-04-30 13:12 ` Kenichi Handa
2008-04-30 13:47 ` Juanma Barranquero
2008-04-30 16:38 ` Eli Zaretskii
2008-04-30 20:23 ` Glenn Morris
2008-04-30 21:11 ` Glenn Morris
2008-04-30 21:28 ` Glenn Morris
2008-05-01 1:01 ` Kenichi Handa
2008-04-30 23:48 ` Jason Rumney
2008-05-01 0:24 ` Jason Rumney
2008-05-02 10:55 ` Kenichi Handa
2008-05-02 11:30 ` Jason Rumney
2008-05-02 11:42 ` Jason Rumney
2008-05-02 12:16 ` Kenichi Handa
2008-05-02 13:27 ` Jason Rumney
2008-05-04 0:05 ` Kenichi Handa
2008-05-04 0:57 ` Stefan Monnier
2008-05-04 11:52 ` Kenichi Handa [this message]
2008-05-04 14:46 ` Jason Rumney
2008-05-05 0:58 ` Stefan Monnier
2008-05-06 11:25 ` Kenichi Handa
2008-05-07 1:53 ` Stefan Monnier
2008-05-14 13:31 ` Font not found Robert J. Chassell
2008-05-15 3:39 ` Kenichi Handa
2008-05-15 12:27 ` Robert J. Chassell
2008-05-06 11:16 ` font-backend branch Kenichi Handa
2008-05-04 14:14 ` Jason Rumney
2008-05-04 14:08 ` Jason Rumney
2008-05-01 3:54 ` Glenn Morris
2008-05-01 6:27 ` Kenichi Handa
2008-05-01 7:07 ` Glenn Morris
2008-05-01 7:21 ` Kenichi Handa
2008-05-01 7:28 ` Glenn Morris
2008-05-01 15:20 ` Kenichi Handa
2008-05-01 17:52 ` Glenn Morris
2008-05-02 0:22 ` Kenichi Handa
2008-05-01 8:00 ` Kenichi Handa
2008-05-02 1:14 ` James Cloos
2008-05-02 2:15 ` Kenichi Handa
2008-05-02 8:16 ` Jason Rumney
2008-05-04 22:00 ` Jason Rumney
2008-05-05 10:14 ` Florian Beck
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1JsclL-0005eq-0O@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).