all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Adrian Robert <adrian.b.robert@gmail.com>
To: Kenichi Handa <handa@m17n.org>
Cc: mituharu@math.s.chiba-u.ac.jp, emacs-devel@gnu.org
Subject: Re: fail on osx between 2/4/2009 and 2/5/2009
Date: Sun, 15 Feb 2009 18:04:13 +0200	[thread overview]
Message-ID: <86BB7F5A-18D1-4D15-A141-FC721BCC7CB4@gmail.com> (raw)
In-Reply-To: <E1LYKAt-00008y-IS@etlken>


On Feb 14, 2009, at 3:03 PM, Kenichi Handa wrote:
>
> :script -- script name symbol.  script-representative-chars
> can be used as an additional hint to find a font.
>
> :lang -- symbol of iso639 two-letter language code.
>
> :otf -- see the docstring of query-font
>
> and I'm going to add:
>
> :chars -- the same format as the cdr part of each element of
> script-representative-chars.

OK, thanks, I'll work on responding to them in the NS backend (though  
I'm unsure about the OTF stuff).  Does this new mechanism of   
displaying chars in any script (through passing :script to the  
backend when asking for fonts) operate with any fontset (e.g., if the  
user does set-frame-font or similar), or is it only when the user is  
using the so-called "default" fontset?

As far as prioritization, it was said earlier that :chars should  
override anything in script-representative-chars.  What about  
priority between :lang and :script?  From the backend impl's  
perspective, does :lang really need to be worried about if :script is  
present?  Will there be times when match() or list() receives a spec  
with :lang only (and no :script)?

Also, is there a plan to update the documentation for match() and list 
() in font.h?  I'm willing to do this (after I've finished and tested  
my new implementation) if no one else has time.

thanks,
Adrian





  reply	other threads:[~2009-02-15 16:04 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-07  1:15 fail on osx between 2/4/2009 and 2/5/2009 Randal L. Schwartz
2009-02-07  5:02 ` Will Farrington
2009-02-07 10:46   ` Adrian Robert
2009-02-09  2:52     ` Will Farrington
2009-02-10  6:42     ` Kenichi Handa
2009-02-10  6:47       ` Will Farrington
2009-02-10  8:08       ` Jules Colding
2009-02-10  8:44         ` YAMAMOTO Mitsuharu
2009-02-10  9:05           ` Jules Colding
2009-02-10 10:51           ` YAMAMOTO Mitsuharu
2009-02-10 12:06           ` Kenichi Handa
2009-02-10 13:06             ` Jason Rumney
2009-02-12  7:37               ` Kenichi Handa
2009-02-12  8:03                 ` YAMAMOTO Mitsuharu
2009-02-12 10:22                   ` Kenichi Handa
2009-02-12 18:42                     ` Adrian Robert
2009-02-14 13:03                       ` Kenichi Handa
2009-02-15 16:04                         ` Adrian Robert [this message]
2009-02-16  0:53                           ` Kenichi Handa
2009-02-16  4:09                             ` Kenichi Handa
2009-02-17 10:15                             ` Adrian Robert
2009-02-17 11:15                               ` Kenichi Handa
2009-02-18  2:48                                 ` Kenichi Handa
2009-02-18  3:12                                   ` YAMAMOTO Mitsuharu
2009-02-18  4:01                                     ` Kenichi Handa
2009-02-18  5:43                                       ` YAMAMOTO Mitsuharu
2009-02-19 10:30                                   ` Adrian Robert
2009-02-24  2:55                                     ` Kenichi Handa
2009-02-16  0:33                       ` YAMAMOTO Mitsuharu
2009-02-17 10:26                         ` Adrian Robert
2009-02-17 11:09                           ` YAMAMOTO Mitsuharu
2009-02-19 10:30                             ` Adrian Robert
2009-02-20  1:19                               ` YAMAMOTO Mitsuharu
2009-02-11  1:08             ` YAMAMOTO Mitsuharu
2009-02-10 12:59       ` William Xu
2009-02-09 14:39   ` William Xu

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=86BB7F5A-18D1-4D15-A141-FC721BCC7CB4@gmail.com \
    --to=adrian.b.robert@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.org \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    /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.