From: "Idris Samawi Hamid" <ishamid@colostate.edu>
To: "Mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Luatex (actually Aleph) and Bidi_Mirrored chars in RTL mode
Date: Mon, 09 Jun 2008 19:44:59 -0600 [thread overview]
Message-ID: <op.ucie49ymnx1yh1@your-b27fb1c401> (raw)
In-Reply-To: <20080610013600.GG18755@phare.normalesup.org>
Hi,
On Mon, 09 Jun 2008 19:36:00 -0600, Arthur Reutenauer
<arthur.reutenauer@normalesup.org> wrote:
>> Also, we need not be too slavish: The Yudit author has pointed out areas
>> where the bidi algorithm makes no sense or is deficient:
>>
>> http://www.yudit.org/bidi/surprise.html
>
> To be honest, this page dates back to half a dozen years ago and
> reflects Gáspár Sinai's positions at that time; there are hints that he
> has changed his mind at least slightly, as he started to make quite a
> scandal about possible "security problems" in the bidi algorithm and
> later backed off (http://yudit.org/security/). This is of course not to
> say that the bidi algorithm is perfect, because it's not, but I don't
> think that the link you quote makes a really strong point against it.
> In particular, I find that some of the recommandations Sinai criticizes
> are amazingly close to what we do in the TeX world ("formatting codes
> should be inserted" => mark up the text with direction-switching
> commands, etc.)
Granted. The main point is that we have to reinterpret bidi in way that
fits with TeX's/ConTeXt's needs, idiosyncracies, etc.... I don't believe
we need to treat the unicode bidi algorithm as canonical.
But I'm still studying the matter.
Best
Idris
--
Professor Idris Samawi Hamid, Editor-in-Chief
International Journal of Shi`i Studies
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-06-10 1:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 1:21 Khaled Hosny
2008-06-09 13:43 ` Arthur Reutenauer
2008-06-09 15:20 ` Hans Hagen
2008-06-09 17:01 ` Khaled Hosny
2008-06-09 21:08 ` Hans Hagen
2008-06-13 21:52 ` Khaled Hosny
2008-06-14 1:34 ` Idris Samawi Hamid
2008-06-15 17:26 ` Khaled Hosny
2008-06-15 20:32 ` Hans Hagen
2008-06-15 20:50 ` Idris Samawi Hamid
2008-06-15 20:58 ` Hans Hagen
2008-06-15 21:42 ` Idris Samawi Hamid
2008-06-16 16:14 ` Khaled Hosny
2008-06-15 20:37 ` Hans Hagen
2008-06-15 20:36 ` Hans Hagen
2008-06-10 1:07 ` Idris Samawi Hamid
2008-06-10 1:36 ` Arthur Reutenauer
2008-06-10 1:44 ` Idris Samawi Hamid [this message]
2008-06-10 7:34 ` Hans Hagen
2008-06-10 15:28 ` Arthur Reutenauer
2008-06-10 15:32 ` Hans Hagen
2008-06-10 21:30 ` Arthur Reutenauer
2008-06-18 5:40 ` Otared Kavian
2008-06-18 8:29 ` Arthur Reutenauer
2008-06-18 15:22 ` Idris Samawi Hamid
2008-06-18 15:44 ` Khaled Hosny
2008-06-18 19:50 ` Idris Samawi Hamid
2008-06-18 21:38 ` Khaled Hosny
2008-06-10 8:13 ` Hans Hagen
2008-06-10 15:29 ` Arthur Reutenauer
2008-06-10 16:24 ` Hans Hagen
2008-06-10 21:37 ` Arthur Reutenauer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=op.ucie49ymnx1yh1@your-b27fb1c401 \
--to=ishamid@colostate.edu \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).