ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: "Idris Samawi Hamid ادريس سماوي حامد" <ishamid@colostate.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \framed (and others) don't honor	directional switches
Date: Fri, 03 Apr 2009 23:28:29 +0200	[thread overview]
Message-ID: <49D67F7D.40005@wxs.nl> (raw)
In-Reply-To: <op.urtxtlv5fkrasx@your-b27fb1c401>

Idris Samawi Hamid ادريس سماوي حامد wrote:
> On Fri, 03 Apr 2009 15:08:48 -0600, Hans Hagen <pragma@wxs.nl> wrote:
> 
>> 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)
> 
> Indeed. We may also need Taco's help; he's about the only one I know who 
> precisely understands the distinction between \pardir and \bodydir. I 
> did some extensive testing on this nearly two years ago and could hardly 
> make sense of it. The user should never have to touch \pardir or 
> \bodydir and we need a higher level command. Not sure if the same will 
> work at the macro level.
> 
> I'll search for Taco's old detailed explanations of these two and 
> forward them to you and Khalid.

there has been changes (consistency cleasups) to the engine so you might 
want to run some tests again; first we need to be absolutely sure of the 
engine backend does things right (i.e. as we expect)

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
___________________________________________________________________________________

  reply	other threads:[~2009-04-03 21:28 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 [this message]
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=49D67F7D.40005@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).