From: Kenichi Handa <handa@m17n.org>
To: Drew Adams <drew.adams@oracle.com>, 2949@emacsbugs.donarmstrong.com
Cc: miles@gnu.org
Subject: bug#2949: 23.0.92; font-info incompatible across Emacs versions
Date: Tue, 14 Apr 2009 21:41:22 +0900 [thread overview]
Message-ID: <E1Lthx4-0006EB-Jm@etlken> (raw)
In-Reply-To: <000601c9bacd$14ef5120$0200a8c0@us.oracle.com> (drew.adams@oracle.com)
In article <000601c9bacd$14ef5120$0200a8c0@us.oracle.com>, "Drew Adams" <drew.adams@oracle.com> writes:
> > > In Emacs 20, `font-info' returns an array like this: ...
> > > In Emacs 22 and later, it returns an array like this: ...
> > > This breaks any code that tries to use the result with
> > > different Emacs versions.
> >
> > So.... what exactly do you want to happen?
> >
> > The two formats look easy enough to distinguish. Since the change
> > occurred in 22, it's been widely released, so obviously 3rd-party code
> > simply has to be prepared to deal with it (if they care about 21 and
> > older versions), and there's little point in changing it back now.
Actually the change occurred in Emacs 21.
> I guess nothing can be done.
> But I do wonder why CHARSET was dropped from both `font-info' and
> `describe-font'. There seems to be nothing about this in NEWS (e.g. for Emacs
> 22). Is the character set no longer meaningful? useful? appropriate?
> discoverable?
I vaguely remember that the change was within a big change
of fontset implementation to match with Gerd's new display
engine for the release of 21. Before that, fonts are
specified for each charset, but after that, fonts are
specified for each character using a char table. As a
result, the concept for charset for a font lost the meaning.
Because the changes are quite lot at that time, perhaps I
forgot to record this specific change in NEWS and ChangeLog.
2000-03-21 Kenichi HANDA <handa@etl.go.jp>
The following changes are to make font selection based on
characters, not charset. In addition, they recover fontset
facilities while utilizing the new font selection mechanism.
[...]
In article <49E153DA.7070502@gnu.org>, Jason Rumney <jasonr@gnu.org> writes:
> Miles Bader wrote:
> > So.... what exactly do you want to happen?
> >
> At least the doc string for font-info should be updated. It still claims
> that the third entry in the returned vector is CHARSET.
I fixed the docstring.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2009-04-14 12:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5062.1239379440.31690.bug-gnu-emacs@gnu.org>
2009-04-11 17:26 ` bug#2949: 23.0.92; font-info incompatible across Emacs versions Miles Bader
2009-04-11 17:43 ` Drew Adams
2009-04-14 12:41 ` Kenichi Handa [this message]
2009-04-14 14:32 ` Drew Adams
2009-04-12 2:37 ` Jason Rumney
2009-04-10 15:44 Drew Adams
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=E1Lthx4-0006EB-Jm@etlken \
--to=handa@m17n.org \
--cc=2949@emacsbugs.donarmstrong.com \
--cc=drew.adams@oracle.com \
--cc=miles@gnu.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.