ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Figures are misplaced with \pagedir TRT\bodydir TRT
Date: Wed, 03 Sep 2008 08:52:58 +0200	[thread overview]
Message-ID: <48BE344A.5050104@wxs.nl> (raw)
In-Reply-To: <op.ugvj7pokfkrasx@your-b27fb1c401>

Idris Samawi Hamid ادريس سماوي حامد wrote:
> On Tue, 02 Sep 2008 15:58:21 -0600, Hans Hagen <pragma@wxs.nl> wrote:
> 
>> i'm wondering ... why do we need pagedir and bodydir?
> 
> =========
> http://www.ctan.org/tex-archive/systems/omega/
> 
> \pagedir  The direction for pages (\shipout).
> \bodydir  The direction for vboxes, including the main body of text.
> =========
> 
> Think of footnote numerals etc. IIRC: Without \pagedir TRT\bodydir TRT the  
> footnote numerals will appear on the left despite \pardir and \textdir.
> 
> I still don't completely _separately_ understand \pagedir TRT\bodydir TRT,  
> but together they seem to make sense to me. Taco once started explainig  
> these two to Hans and I a few months back but that thread was never  
> completed... I'll look up where we left things off.

among the pending issues was 'where do we explicitly need to set it and 
when do we need to compensate for it'

for some reason inserts (the figure) are sensitive to it and it might be 
some interference as well as a missing explicit dir reversal

[omega provides these mechanisms but i think that there was never a full 
blown macro package using them, i.e. mixed direction support and such; 
there might be many places where we need to add dir-checking code to 
context; a few places already have it]


-----------------------------------------------------------------
                                           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:[~2008-09-03  6:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-02 18:33 Khaled Hosny
2008-09-02 20:50 ` Khaled Hosny
2008-09-02 21:34   ` Khaled Hosny
2008-09-02 21:45     ` Hans Hagen
2008-09-03  6:54   ` Hans Hagen
2008-09-02 21:58 ` Hans Hagen
2008-09-02 22:17   ` Idris Samawi Hamid ادريس سماوي حامد
2008-09-03  6:52     ` Hans Hagen [this message]
2008-09-03  6:55     ` Hans Hagen
2008-09-03  0:11   ` Idris Samawi Hamid ادريس سماوي حامد
2008-09-03  1:56     ` Khaled Hosny
2008-11-27  1:31 ` Khaled Hosny

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=48BE344A.5050104@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).