From: Alexis <flexibeast@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Ping! Re: `font-spec` unable to retrieve :name of font
Date: Fri, 23 Oct 2015 20:55:06 +1100 [thread overview]
Message-ID: <87h9lhucxx.fsf@gmail.com> (raw)
In-Reply-To: <83k2qft0ej.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> Sorry for not responding earlier.
That's okay!
> Emacs's font handling is deeply entrenched in the XLFD spec.
> That is true even on platforms that don't support XLFD, such as
> MS-Windows. So this is not a bug, it's the intended behavior,
> the code is working as designed.
*nod* Fair enough.
> That said, I had a similar problem with fonts named like
> Foobar-12, see commit 7d5a7a4 which solved that. (The original
> problem is described in the discussion that started in
> http://lists.gnu.org/archive/html/help-emacs-windows/2015-06/msg00001.html.)
> That problem could be solved because the part after the dash was
> a number, and a font's family cannot be a number. I don't know
> if we can do the same with this case. Which "family" names are
> we allowed to reject, exactly? Don't forget that the weight
> field of the XLFD spec, which follows the family, uses
> single-letter codes (although AFAIK "g" is not one of them); we
> ought not to trick ourselves into accidentally treating weight
> as part of the font name.
Yes, i gave some thought to possible heuristics that could be used
in instances such as this, but didn't come up with anything
practical .... i might see if i can use FontForge to change the
name to something XLFD-friendly (e.g. 'InconsolataG').
Thanks!
Alexis.
next prev parent reply other threads:[~2015-10-23 9:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 2:13 `font-spec` unable to retrieve :name of font Alexis
2015-10-22 8:48 ` Ping! " Alexis
2015-10-22 14:59 ` Eli Zaretskii
2015-10-23 9:55 ` Alexis [this message]
2015-10-24 17:45 ` Nix
2015-10-24 17:57 ` Eli Zaretskii
2015-10-24 18:04 ` Drew Adams
2015-10-26 14:10 ` Nix
2015-10-27 2:32 ` Stephen J. Turnbull
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=87h9lhucxx.fsf@gmail.com \
--to=flexibeast@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.