From: Jason Rumney <jasonr@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Alan Mackenzie <acm@muc.de>, emacs-devel@gnu.org
Subject: Re: Being constructive [Was: Nit-picking]
Date: Sat, 12 Apr 2008 15:14:03 +0100 [thread overview]
Message-ID: <4800C3AB.8020409@gnu.org> (raw)
In-Reply-To: <uskxr8b72.fsf@gnu.org>
Eli Zaretskii wrote:
> Continuing and perhaps even finishing my bidi display code has been a
> pipe dream for several years now, so it's probably not even worth
> mentioning.
>
A smaller task might be to make use of the functionality of libotf/m17n
and uniscribe (and any Mac equivalent) to provide bidi support on those
platforms which offer underlying support. It will only be as good as
the support offered by the underlying platform, only available in GUI
frames, and even then only if Emacs is compiled against those libraries,
but it is better than the current state of no bidi support at all. If
work is started now, I think we can get this in to Emacs 23. I don't
know how far emacs-bidi is from completion, but I'm guessing it will be
at least Emacs 24 material?
next prev parent reply other threads:[~2008-04-12 14:14 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 21:09 23.0.60; M-( and M-) should not be bound in ESC map Drew Adams
2008-04-09 21:32 ` Andreas Schwab
2008-04-09 22:15 ` Drew Adams
2008-04-10 6:33 ` David Hansen
2008-04-10 9:20 ` Reiner Steib
2008-04-10 8:31 ` Andreas Schwab
2008-04-10 12:55 ` Richard Stallman
2008-04-10 13:45 ` Paul R
2008-04-10 15:49 ` Alan Mackenzie
2008-04-10 15:45 ` Juanma Barranquero
2008-04-10 16:24 ` Alan Mackenzie
2008-04-10 16:15 ` Juanma Barranquero
2008-04-10 21:09 ` David Kastrup
2008-04-10 22:34 ` Juanma Barranquero
2008-04-11 2:23 ` Glenn Morris
2008-04-11 5:03 ` Thomas Lord
2008-04-11 8:03 ` tomas
2008-04-12 0:11 ` Richard Stallman
2008-04-12 1:13 ` Thomas Lord
2008-04-12 5:49 ` David Kastrup
2008-04-12 7:31 ` Alan Mackenzie
2008-04-12 14:03 ` Thomas Lord
2008-04-12 20:07 ` David Kastrup
2008-04-12 21:24 ` Thomas Lord
2008-04-12 20:34 ` Stephen J. Turnbull
2008-04-11 8:41 ` Paul R
2008-04-11 9:40 ` Juanma Barranquero
2008-04-10 17:10 ` Thomas Lord
2008-04-10 17:10 ` Paul R
2008-04-10 19:21 ` Stephen J. Turnbull
2008-04-12 0:11 ` Richard Stallman
2008-04-10 16:18 ` Drew Adams
2008-04-12 0:09 ` Richard Stallman
2008-04-12 0:09 ` Richard Stallman
2008-04-12 8:40 ` Nit-picking (was: 23.0.60; M-( and M-) should not be bound in ESC map) Eli Zaretskii
2008-04-12 9:35 ` Nit-picking Alan Mackenzie
2008-04-12 10:30 ` Nit-picking Eli Zaretskii
2008-04-12 11:46 ` Being constructive [Was: Nit-picking] Alan Mackenzie
2008-04-12 13:17 ` Eli Zaretskii
2008-04-12 14:14 ` Jason Rumney [this message]
2008-04-12 16:51 ` Eli Zaretskii
2008-04-12 17:16 ` Eli Zaretskii
2008-04-12 21:38 ` Mike Mattie
2008-04-12 15:06 ` 23.0.60; M-( and M-) should not be bound in ESC map Drew Adams
2008-04-13 1:58 ` 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=4800C3AB.8020409@gnu.org \
--to=jasonr@gnu.org \
--cc=acm@muc.de \
--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).