all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Werner LEMBERG <wl@gnu.org>
Cc: oub@mat.ucm.es,  rogers@rgrjr.com,  eliz@gnu.org,  emacs-devel@gnu.org
Subject: Re: has the emoji support been enhanced on master?
Date: Sun, 12 Feb 2023 18:36:27 +0800	[thread overview]
Message-ID: <87sffbyxuc.fsf@yahoo.com> (raw)
In-Reply-To: <20230212.093223.2188702668728218260.wl@gnu.org> (Werner LEMBERG's message of "Sun, 12 Feb 2023 08:32:23 +0000 (UTC)")

Werner LEMBERG <wl@gnu.org> writes:

> I'm using openSUSE 15.4, too, and in my Emacs (self-compiled from git two
> weeks ago) I see both Emojis (image attached).

Hi, Werner.

I'm not sure if this is the right place to reach you about this problem,
but I'm seeing some mysterious behavior in FreeType.

As part of the Android port, I'm writing a module to display TrueType
fonts.  This includes a TrueType interpreter for instructing fonts.

AFAIU, as long as a font does not perform an INSTCTRL which sets bit 2
in the instruction control, changes made to the graphics state from the
control value program will become the ``default'' state from which
glyphs are instructed.

However, some CJK fonts perform no INSTCTRL instructions at all, change
the projection vector and rp1 from prep, yet FreeType resets both to the
X axis and 0 respectively before any glyph programs are run.

Am I missing anything?  If not, could you tell me where this behavior is
documented?

Thanks.



  parent reply	other threads:[~2023-02-12 10:36 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11 14:39 has the emoji support been enhanced on master? Uwe Brauer
2023-02-11 15:31 ` Eli Zaretskii
2023-02-11 16:13   ` Uwe Brauer
2023-02-11 16:32     ` Eli Zaretskii
2023-02-11 17:06       ` Uwe Brauer
2023-02-11 17:13         ` Eli Zaretskii
2023-02-11 17:26           ` Uwe Brauer
2023-02-11 17:40             ` Eli Zaretskii
2023-02-11 19:17               ` Uwe Brauer
2023-02-11 19:21                 ` Eli Zaretskii
2023-02-11 19:38                   ` Uwe Brauer
2023-02-11 19:41                     ` Eli Zaretskii
2023-02-11 20:46                       ` Bob Rogers
2023-02-12  7:45                         ` Uwe Brauer
2023-02-12  8:05                           ` Eli Zaretskii
2023-02-12  9:26                             ` Uwe Brauer
2023-02-12 11:53                               ` Eli Zaretskii
2023-02-12 13:10                                 ` Uwe Brauer
2023-02-12 13:22                                   ` Eli Zaretskii
2023-02-12 20:19                                     ` Bob Rogers
2023-02-12 20:22                                       ` Eli Zaretskii
2023-02-12 20:44                                         ` Bob Rogers
2023-02-12  8:32                           ` Werner LEMBERG
2023-02-12  9:33                             ` Uwe Brauer
2023-02-12  9:59                               ` Werner LEMBERG
2023-02-12 10:34                                 ` Uwe Brauer
2023-02-12 12:14                                   ` Werner LEMBERG
2023-02-12 13:10                                     ` Uwe Brauer
2023-02-12 10:36                             ` Po Lu [this message]
2023-02-12 14:43                               ` Werner LEMBERG
2023-02-12 15:37                                 ` Po Lu
2023-02-12 16:56                               ` Benjamin Riefenstahl
2023-02-13  2:32                                 ` Po Lu
2023-02-13 14:25                                   ` Benjamin Riefenstahl
2023-02-13 15:08                                     ` Po Lu
2023-02-13 18:21                                       ` Benjamin Riefenstahl
2023-02-11 20:30                 ` Tim Cross

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=87sffbyxuc.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=oub@mat.ucm.es \
    --cc=rogers@rgrjr.com \
    --cc=wl@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.