unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: David Kastrup <dak@gnu.org>
Cc: cloos@jhcloos.com, emacs-devel@gnu.org
Subject: Re: Hebrew xlation of Emacs tutorial
Date: Sat, 03 Feb 2007 20:42:27 +0200	[thread overview]
Message-ID: <u3b5n13sc.fsf@gnu.org> (raw)
In-Reply-To: <858xffgqkb.fsf@lola.goethe.zz> (message from David Kastrup on Sat, 03 Feb 2007 17:21:24 +0100)

> Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
> From: David Kastrup <dak@gnu.org>
> Date: Sat, 03 Feb 2007 17:21:24 +0100
> 
> I don't think that this is the only issue.  Eli might correct me on
> that, but the last time this issue came up, he clearly stated that the
> bidi branch was not production quality and had serious stability and
> performance issues.

David is right: the bidi branch is just a first attempt to make the
display engine support bidirectional languages.  It needs a lot of
debugging to become usable.  In particular, as soon as you turn on the
bidi support flag, Emacs instantly crashes.

> We certainly don't want it to be "merged into the
> emacs-unicode-2 branch" before Emacs 23 is released: emacs-unicode-2
> is a major step forward and apparently close to release quality.

I rather hope that Emacs 23 will come out with bidi support (since
Unicode requires that), but that hope has no basis whatsoever.

> There are also other issues which should probably be addressed when
> reworking the display engine for bidi, like composite character
> support and antialiasing

I'm not aware of any such issues, but then the implications of bidi
redisplay were never discussed in detail.

  reply	other threads:[~2007-02-03 18:42 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 [this message]
2007-02-03 19:12                 ` David Kastrup
2007-02-03 21:01                   ` James Cloos
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=u3b5n13sc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=cloos@jhcloos.com \
    --cc=dak@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).