From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Idris Samawi Hamid <ishamid@colostate.edu>
Subject: Re: \framed (and others) don't honor directional switches
Date: Fri, 03 Apr 2009 23:08:48 +0200 [thread overview]
Message-ID: <49D67AE0.7050304@wxs.nl> (raw)
In-Reply-To: <20090403204723.GA28189@khaled-laptop>
Khaled Hosny wrote:
> On Fri, Apr 03, 2009 at 02:55:56PM +0200, Hans Hagen wrote:
>> Khaled Hosny wrote:
>>> framed, framedtext, TEXpage (and may be others), no longer honor
>>> directional switches. I'm sure TEXpage at least was OK a month ago.
>>>
>>> \pagedir TRT\bodydir TRT\pardir TRT\textdir TRT
>>> \starttext
>>> \startTEXpage
>>> \input tufte
>>> \stopTEXpage
>>> \framed{Hello world}
>>> \startframedtext
>>> \input tufte
>>> \stopframedtext
>>> \startbackground
>>> \input tufte
>>> \stopbackground
>>> \stoptext
>> if so then it's a side effect of changesin the engine (changes in rl
>> handling are dangerous because macro packages are internally lr in many
>> aspects (like positioning data relative to other data) and patching each
>> macro for rl is non trivial (due to possible side effects) so first we
>> need to be sure that the luatex engine is okay
>
> I tried to debug thus further, compiling the following document with
> both plain and context formats, in plain all boxes are TRT (the part of
> the log after "Completed box being shipped out [1]"), while in context
> all boxes are TLT except that hbox that contains the text. Though I
> don't know how much relevant is this or what it does actually mean.
>
> \pagedir TRT
> \bodydir TRT
> \pardir TRT
> \textdir TRT
> \tracingall
> Hello \hbox{World}
> \bye
you can comment this in cont-new.mkiv
% \def\pagedir{\expandafter\gobblethreearguments}
% \def\bodydir{\expandafter\gobblethreearguments}
i'm trying to figure out what dirs make sense (even when all are enabled
the alignment is no 100% ok; for instance, why should bodydir influence
textdir and pardir (i.e. when i would expect the content to be rl
independent of page/bodydir
(we need some higher level interface and not these low level *dir commands)
best is if you and idris sort this out (is part of idris onthology)
-----------------------------------------------------------------
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:[~2009-04-03 21:08 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 [this message]
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
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=49D67AE0.7050304@wxs.nl \
--to=pragma@wxs.nl \
--cc=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).