unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>,
	Kenichi Handa <handa@gnu.org>
Cc: 17457@debbugs.gnu.org
Subject: bug#17457: 24.4.50; REGRESSION: "Invalid font name: -outline-Lucida	Console-normal-normal-normal-mono"
Date: Sun, 11 May 2014 12:23:32 -0700 (PDT)	[thread overview]
Message-ID: <224c2504-400c-439e-ad89-bb81e82a7b7f@default> (raw)
In-Reply-To: <<834n0wus9k.fsf@gnu.org>>

> > I truncated it because I am not interested in anything except the
> > first 6 fields of the XLFD string.
> 
> The right way is to replace the other fields with "*", not chop them
> off.

I almost added, and will add now, that I think perhaps the reason
I did that before passing the font arg to `font-info', was mainly to
allow handling of the problematic fonts.  I did not realize, however,
that they were anyway not being handled correctly that way.  They were
tolerated, but the returned info was not relevant.

> Yes, I think the problem is in that "-ExtB", which I think is part of
> the font name, but Emacs's XLFD parser thinks it is a separate field.
> Perhaps Handa-san, or someone else who knows more about fonts, could
> tell how to handle these font names correctly.  It looks like a bug to
> me, FWIW.

I thought of that, but I don't know how the name should be parsed,
to determine that the name field has ended.  Perhaps the following
field has only a fixed number of possibilities.  But then there is
(IIRC) the possibility that fields can be missing.  IOW, is it
perhaps problematic to parse names that contain hyphens?

I closed the bug.  If appropriate, feel free to open it based on
the possibility of a parsing problem.





  parent reply	other threads:[~2014-05-11 19:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<a68b8275-2f8b-4e80-8e34-5905d809da11@default>
     [not found] ` <<83eh01udux.fsf@gnu.org>
2014-05-11  5:23   ` bug#17457: 24.4.50; REGRESSION: "Invalid font name: -outline-Lucida Console-normal-normal-normal-mono" Drew Adams
2014-05-11 16:03     ` Eli Zaretskii
     [not found]   ` <<cadd8cdd-0fd8-454a-9f82-901c41e19423@default>
     [not found]     ` <<83a9aouwtj.fsf@gnu.org>
2014-05-11 17:19       ` Drew Adams
2014-05-11 17:41         ` Eli Zaretskii
     [not found]       ` <<c873b85c-4ea9-462f-b2a4-4761a218b2e1@default>
     [not found]         ` <<834n0wus9k.fsf@gnu.org>
2014-05-11 19:23           ` Drew Adams [this message]
2014-05-11  1:57 Drew Adams
2014-05-11  2:07 ` Drew Adams
2014-05-11  4:40 ` Eli Zaretskii

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=224c2504-400c-439e-ad89-bb81e82a7b7f@default \
    --to=drew.adams@oracle.com \
    --cc=17457@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=handa@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).