all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Cairo branch.
Date: Thu, 12 Feb 2015 20:17:34 +0100	[thread overview]
Message-ID: <42DC973F-FE9F-4C77-9371-374C5A8F3A04@swipnet.se> (raw)
In-Reply-To: <83lhk35d69.fsf@gnu.org>

Hi.

> 12 feb 2015 kl. 17:04 skrev Eli Zaretskii <eliz@gnu.org>:
> 
>> Date: Thu, 12 Feb 2015 16:01:11 +0100
>> From: "Jan D." <jan.h.d@swipnet.se>
>> Cc: emacs-devel@gnu.org
>> 
>> YAMAMOTO Mitsuharu made the patch to demonstrate printing, so that is 
>> new (see x-print-frames-dialog or the Printing section in xfns.c).
>> 
>> Otherwise it is just a step to keep up with the times, i.e. server side 
>> (as in X11 server) rendering is going away as it seems.  So Emacs must 
>> at some point develop client side (cairo) rendering.
> 
> Is the intent to use Cairo alone, or also use Pango?

Cairo alone.  We use the normal font backend stuff, there is a new one for cairo (ftcrfont.c), based on the Freetype backend (ftfont.c).

> 
> If the latter, then one problem we'd need to figure out is what to do
> with bidirectional display, since AFAIR Pango does its own reordering.
> 
> Another interesting issue is whether we want to use Cairo on Windows
> as well, and eventually drop the w32-specific display back-end.

You have to separate the event and system interaction from the rendering in w32, but also in the X backend so to have a pure resuable cairo rendering code base.  Right now its all kind of mixed in.

	Jan D.





  reply	other threads:[~2015-02-12 19:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11 15:16 Cairo branch Jan Djärv
2015-02-11 21:49 ` Stefan Monnier
2015-02-12 15:01   ` Jan D.
2015-02-12 16:04     ` Eli Zaretskii
2015-02-12 19:17       ` Jan D. [this message]
2015-02-12 20:06         ` Eli Zaretskii
2015-02-12 20:51           ` Jan D.
2015-02-12 16:18     ` Stefan Monnier
2015-02-12 19:20       ` Jan D.

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=42DC973F-FE9F-4C77-9371-374C5A8F3A04@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.