unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: David Kastrup <dak@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Hebrew xlation of Emacs tutorial
Date: Sat, 03 Feb 2007 16:01:18 -0500	[thread overview]
Message-ID: <m3irejgdl6.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <85r6t7f42d.fsf@lola.goethe.zz> (David Kastrup's message of "Sat\, 03 Feb 2007 20\:12\:42 +0100")

>>>>> "David" == David Kastrup <dak@gnu.org> writes:

David> Oh, that is not as much an implication of bidi redisplay but rather of
David> missing display features of Emacs in general.  "composite character"
David> may be the wrong word, it is "compositing"?  Things like accents that
David> are supposed to overprint the following character.

David> Emacs does not cater for them yet, neither does it for antialiased
David> font display

Actually, the font-backend code in the unicode-2 branch handles aa and
simple-compositing just fine, in my experience.  At least when using
the xft backend (alone; I don't run with fallback to the x backend).
Handa-san's got that much working very well, though I did need to put
in some effort creating a reasonably complete xft fontset.

My understanding is that it also works well on the mac backend.

OTOH, I've had no luck with complex composition, such as for Brahmic
scripts.  

So the basic support for compositing seems to be there, it just needs
a full set of rules for the complex scripts.  Eg, everything that
pango can do.  (Pango is (or 'LGPL-2 'FreetypeLicence), so there
shouldn't be any problem using it as a primary reference for writing
the necessary lisp.)

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6

  reply	other threads:[~2007-02-03 21:01 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-01 23:48 Hebrew xlation of Emacs tutorial Yotam Medini יותם מדיני
2007-02-02 12:57 ` David Kastrup
2007-02-02 13:13 ` Eli Zaretskii
2007-02-02 15:25   ` Yotam Medini יותם מדיני
2007-02-02 15:33     ` David Kastrup
2007-02-02 16:16       ` Yotam Medini יותם מדיני
2007-02-02 18:21         ` Eli Zaretskii
2007-02-02 18:19       ` Eli Zaretskii
2007-02-02 22:39         ` David Kastrup
2007-02-03 11:04           ` Eli Zaretskii
2007-02-03 11:11             ` David Kastrup
2007-02-03 11:43               ` Eli Zaretskii
2007-02-03 11:47                 ` David Kastrup
2007-02-03 14:06                   ` Eli Zaretskii
2007-02-02 18:16     ` Eli Zaretskii
2007-02-02 19:07       ` Stefan Monnier
2007-02-02 19:12         ` Drew Adams
2007-02-02 20:10           ` Eli Zaretskii
2007-02-02 20:28             ` Drew Adams
2007-02-02 20:04         ` Eli Zaretskii
2007-02-03  1:52           ` Stefan Monnier
2007-02-03 11:18             ` Eli Zaretskii
2007-02-03 16:01           ` James Cloos
2007-02-03 16:21             ` David Kastrup
2007-02-03 18:42               ` Eli Zaretskii
2007-02-03 19:12                 ` David Kastrup
2007-02-03 21:01                   ` James Cloos [this message]
2007-02-04 19:00                     ` James Cloos
2007-02-05  0:52                       ` Kenichi Handa
2007-02-05 18:37                         ` James Cloos
2007-02-10 11:43                         ` Eli Zaretskii
2007-02-11 14:51                           ` Kenichi Handa
2007-02-03 21:40                   ` Eli Zaretskii
2007-02-05  1:35                   ` Kenichi Handa
2007-02-05 17:51                     ` David Kastrup
2007-02-02 22:12         ` Jason Rumney
2007-02-03 11:19 ` Richard Stallman

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=m3irejgdl6.fsf@lugabout.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=dak@gnu.org \
    --cc=eliz@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).