From: Kenichi Handa <handa@m17n.org>
Cc: emacs-bidi@gnu.org, shaikli@yahoo.com, developer@arabeyes.org,
emacs-devel@gnu.org
Subject: Re: merge emacs-bidi into the main tree
Date: Mon, 18 Aug 2003 09:24:47 +0900 (JST) [thread overview]
Message-ID: <200308180024.JAA01747@etlken.m17n.org> (raw)
In-Reply-To: <E19oBXI-0000Ro-TE@fencepost.gnu.org> (message from Richard Stallman on Sat, 16 Aug 2003 20:36:44 -0400)
In article <E19oBXI-0000Ro-TE@fencepost.gnu.org>, Richard Stallman <rms@gnu.org> writes:
> Synchronizing emacs-unicode to HEAD will take a few weeks
> more. After that, I'll take a look at Eli's code and decide
> what to do. In any cases, I will install the changes for
> BIDI in the branch emacs-unicode-2 because the current codes
> of emacs-bidi depends on automatic-composition facitliy to
> display Arabic and Hebrew, and that exists only in
> emacs-unicode (and in emacs-bidi) version.
> I am not sure what this means. What is the difference between the
> branch emacs-unicode-2 and the branch emacs-unicode?
To reflect the changes in HEAD to the Unicode version of
emacs, I made a branch emacs-unicode-2. When I finish the
work, emacs-unicode branch will be an obsolete branch.
---
Ken'ichi HANDA
handa@m17n.org
next prev parent reply other threads:[~2003-08-18 0:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87lluax3ch.fsf@emacswiki.org>
[not found] ` <7458-Sun03Aug2003224354+0300-eliz@elta.co.il>
[not found] ` <87smoi9p64.fsf@emacswiki.org>
[not found] ` <u1xw26isb.fsf@elta.co.il>
2003-08-04 14:54 ` merge emacs-bidi into the main tree Alex Schroeder
2003-08-07 6:05 ` Richard Stallman
2003-08-07 14:29 ` Eli Zaretskii
2003-08-08 9:05 ` Oliver Scholz
2003-08-08 11:47 ` Kenichi Handa
2003-08-08 15:57 ` Eli Zaretskii
2003-08-08 11:23 ` Gerd Moellmann
2003-08-08 16:02 ` Eli Zaretskii
2003-08-08 16:13 ` Gerd Moellmann
2003-08-09 14:21 ` Richard Stallman
2003-08-09 14:58 ` Gerd Moellmann
2003-08-10 6:34 ` Eli Zaretskii
2003-08-10 10:42 ` Gerd Moellmann
2003-08-10 16:56 ` Eli Zaretskii
2003-08-10 16:33 ` Gerd Moellmann
2003-08-10 16:45 ` Stefan Monnier
2003-08-11 12:53 ` Richard Stallman
2003-08-12 1:49 ` Kenichi Handa
2003-08-12 6:59 ` Eli Zaretskii
2003-08-12 7:18 ` Kenichi Handa
2003-08-12 8:48 ` Eli Zaretskii
2003-08-13 17:13 ` Richard Stallman
2003-08-09 14:21 ` Richard Stallman
2003-08-09 15:04 ` Gerd Moellmann
2003-08-10 6:36 ` Eli Zaretskii
2003-08-08 11:44 ` Kenichi Handa
2003-08-08 16:04 ` Eli Zaretskii
2003-08-08 17:48 ` Alex Schroeder
2003-08-08 18:58 ` Chahine M. HAMILA
2003-08-09 18:43 ` Nadim Shaikli
2003-08-11 12:54 ` Richard Stallman
2003-08-11 16:32 ` Nadim Shaikli
2003-08-12 23:22 ` Richard Stallman
2003-08-13 0:33 ` Kenichi Handa
2003-08-14 3:08 ` Richard Stallman
2003-08-15 5:51 ` Kenichi Handa
2003-08-15 11:51 ` Alex Schroeder
2003-08-15 15:38 ` Nadim Shaikli
2003-08-17 0:36 ` Richard Stallman
2003-08-18 0:24 ` Kenichi Handa [this message]
2003-08-13 3:44 ` Nadim Shaikli
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=200308180024.JAA01747@etlken.m17n.org \
--to=handa@m17n.org \
--cc=developer@arabeyes.org \
--cc=emacs-bidi@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=shaikli@yahoo.com \
/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).