From: Adrian Robert <adrian.b.robert@gmail.com>
To: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: NS font case sensitivity
Date: Fri, 19 Jun 2009 23:06:35 +0300 [thread overview]
Message-ID: <8FED0638-F71F-469F-B191-EB87ADCE7BEC@gmail.com> (raw)
In-Reply-To: <4A3B210A.8060001@gnu.org>
On Jun 19, 2009, at 8:24 AM, Jason Rumney wrote:
> Adrian Robert wrote:
>> Jason Rumney <jasonr <at> gnu.org> writes:
>>
>>
>>> Is there a good reason why the entries in face-alternative-font-
>>> family-alist need to be case sensitive
>>> on NS when they are not on other platforms?
>>>
>>
>> Font family matching is case sensitive in the API used
>> by the NS font driver.
>>
>
> I'm not sure that is relevant here. This variable (actually it is
> exposed to lisp as face-font-family-alternatives) is only used when
> it has already been determined that the named font does not exist
> in the system, so for example on other platforms if some lisp code
> requests the font "Sans Serif" or "sans serif" and a font by that
> name is not defined, "helv", "helvetica", "arial" and "fixed" are
> tried as alternatives. But on NS, that list will only be used if
> the lisp code requests that font with matching case.
Logically, this behavior is consistent with family names being case
sensitive -- the user customizing face-font-family-alternatives may
want to specify different alternative lists for different family
names, even if they differ only in their case. But practically, I
doubt the situation will come up in that way -- so we might as well
remove the ifdef to streamline the code if that is best.
prev parent reply other threads:[~2009-06-19 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 13:13 NS font case sensitivity Jason Rumney
2009-06-18 16:33 ` Glenn Morris
2009-06-19 5:04 ` Adrian Robert
2009-06-19 5:24 ` Jason Rumney
2009-06-19 20:06 ` Adrian Robert [this message]
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=8FED0638-F71F-469F-B191-EB87ADCE7BEC@gmail.com \
--to=adrian.b.robert@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jasonr@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 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).