From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \framed (and others) don't honor directional switches
Date: Sun, 05 Apr 2009 11:14:48 +0200 [thread overview]
Message-ID: <49D87688.1000908@wxs.nl> (raw)
In-Reply-To: <20090404150558.GA15057@khaled-laptop>
Khaled Hosny wrote:
> On Sat, Apr 04, 2009 at 12:35:30PM +0200, Hans Hagen wrote:
>> Khaled Hosny wrote:
>> indeed, so we're looking into it now (an dlet's forget about the
>> page/bodydir for the moment)
>>
>> since textdir and pardir go hand-in-hand i suggest the following
>>
>> \setuplayout[direction=r2l] % also influences general layout issues
>
> I assume that will mirror all layout elements like double sided page
> numbering, right and left pages etc. right?
yes, the thing that idris identified in his onthology (which might have
white spots); we start on this once some other arabic font subsystem,
has been completed
>> \setupalign [r2l] % textdir and pardir
>> \setuparranging[direction=r2l] % will flush pages backward
>>
>> so l2r and r2l values; as they are part of the align mechanism then,
>> they are automatically part of all commands that have a align key
>
> This sounds very good for me.
ok, the next beta will have the \setupalign and align= available
> While we are in it, I'd suggest that the current implicit bidi to be
> revised, currently it is broken. I suggest to be implement Unicode BiDi
> algorithm[1], and the "higher-level protocols[2]" part is worthy
> investigating. Also, I think it should be decoupled from character
> mirroring, so that one can enable mirroring while explicitly setting
> text direction. Also, some characters that had assigned mirrored
> property in Unicode 5.0.0 has been reversed in later revisions[3]
> because it "affects deployed data" (the source of all evil!), this
> includes quotation marks, so we need to handle mirroring of those
> characters as part of the suggested higher-level protocols as well.
hm, this character mirroring is kind of evil anyway (as it can also
intefere with font features)
i'll look into it later (first need to finish a few things)
the problem with bidi is that it it has to work ok with the already
present (of triggered) TRT / TLT nodes which is not that trivial
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
___________________________________________________________________________________
prev parent reply other threads:[~2009-04-05 9:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 12:35 Khaled Hosny
2009-04-03 12:55 ` Hans Hagen
2009-04-03 20:47 ` Khaled Hosny
2009-04-03 21:08 ` Hans Hagen
2009-04-03 21:25 ` Idris Samawi Hamid ادريس سماوي حامد
2009-04-03 21:28 ` Hans Hagen
2009-04-03 21:17 ` Hans Hagen
2009-04-03 23:48 ` Khaled Hosny
2009-04-04 10:35 ` Hans Hagen
2009-04-04 15:05 ` Khaled Hosny
2009-04-05 9:14 ` Hans Hagen [this message]
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=49D87688.1000908@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).