unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: State of Unicode display support on Windows
Date: Tue, 12 Oct 2010 02:22:16 +0800	[thread overview]
Message-ID: <4CB355D8.5020705@gnu.org> (raw)
In-Reply-To: <87pqvg4ot0.fsf@telefonica.net>

On 12/10/2010 01:33, Óscar Fuentes wrote:
> Some characters display fine on GNU/Linux but not on Windows. An example
> is FISHEYE (?\u25c9) with the Consolas font. Apparently, that font does
> not include that character. In GNU/Linux Emacs simply uses DejaVu for
> displaying the character, but not on Windows, where a white space is
> displayed (the Windows machine also has DejaVu installed.)
>
> Is this a known limitation or a bug?
>
>      uniscribe:-outline-Consolas-normal-normal-normal-mono-20-*-*-*-c-*-iso10646-1 (#x03)
>    

The font is claiming to have that character in position 3 in the glyph 
table. I've also seen the same thing with fonts claiming position 1.  
There is nothing in the documentation for opentype or the font related 
Windows API functions that suggests that there is anything special about 
those glyph indexes, or that it is safe to assume that they mean a 
character is missing from the font.  Currently I think we only treat a 
return of 0 as indicating that the character is missing, as that is 
reserved by the truetype and opentype specs for the character ".notdef".





  reply	other threads:[~2010-10-11 18:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11 17:33 State of Unicode display support on Windows Óscar Fuentes
2010-10-11 18:22 ` Jason Rumney [this message]
2010-10-11 18:52   ` Juanma Barranquero
2010-10-11 19:00     ` Óscar Fuentes
2010-10-11 19:03       ` Juanma Barranquero
2010-10-11 19:13     ` 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=4CB355D8.5020705@gnu.org \
    --to=jasonr@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 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).