From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Luatex (actually Aleph) and Bidi_Mirrored chars in RTL mode
Date: Tue, 10 Jun 2008 09:34:42 +0200 [thread overview]
Message-ID: <484E2E92.7050200@wxs.nl> (raw)
In-Reply-To: <op.ucie49ymnx1yh1@your-b27fb1c401>
Idris Samawi Hamid wrote:
> 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.
i think that we should stick to things that make sense; with tex we're
often talking of tagged sources and anything ambiguous should be tagged;
in a sense this is not even related to arab at all, take an url ... i
can imagine an url-algorithm, but it could never be perfect (just see
what some programs that try to do it sometimes make of it)
if for instance ( ) are officially not symbols but open/close thingies,
then we need to deal with them (although i then wonder why we have no
proper open/close code point for them instead of reusing the ascii ()
which have for users some expected visual appearance, but in that
respect unicode puzzles me on a daily basis)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 7:34 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
2008-06-10 7:34 ` Hans Hagen [this message]
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=484E2E92.7050200@wxs.nl \
--to=pragma@wxs.nl \
--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).