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

James Cloos <cloos@jhcloos.com> writes:

> Eli,
>
> Any idea how much work it'd take to merge the changes between
> the (your, right?) emacs-bidi-base and emacs-bidi branches into
> the emacs-unicode-2 branch?
>
> There are only 3 merge failures in src files, plus a couple in
> texinfo files and several in ChangeLog files.

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.  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.

There are also other issues which should probably be addressed when
reworking the display engine for bidi, like composite character
support and antialiasing, so merging the fragile bidi branch might not
actually be the best tactic for going forward.

At the current point of time, I think it prudent to leave Emacs-bidi
on the back burner, and to start thinking about what long-term
strategy to follow in a bidi-capable branch (it might well mean
abandoning the current emacs-bidi approach) when emacs-unicode-2 has
made it into the trunk and does not require major reworks before Emacs
23.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2007-02-03 16:21 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 [this message]
2007-02-03 18:42               ` Eli Zaretskii
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=858xffgqkb.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=cloos@jhcloos.com \
    --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).