From: Hans Hagen <pragma@wxs.nl>
Subject: Re: more footnotes:-)
Date: Thu, 29 Jul 2004 09:46:24 +0200 [thread overview]
Message-ID: <4108AB50.3030403@wxs.nl> (raw)
In-Reply-To: <410D9171@webmail.colostate.edu>
ishamid wrote:
>[please forward to list]
>
>
>>===== Original Message From Hans Hagen <pragma@wxs.nl> =====
>>% program=aleph output=dvipdfmx
>>
>>% the next texexec will automatically generate pdf which is handy for
>>scit eusers -)
>>
>>\setupcolors[state=start]
>>
>>\starttext
>>
>>
>
>Ok, here is a modified test file. The headers on pages 1 and 2 should be the
>same throughout the entire document. Of course, when I make the temporary
>global direction switch, the location of the headers get switched too. My
>problem is that I have not been able to create a combination of \setupheaders
>and \setuppagenumbering so that I can adjust the headers during the temporary
>direction switch so that it appears that the header locations remain constant:
>
>
...
Last night I played a bit with aleph.
One of the things that we need to keep in mind with omega is that the fact that it can typeset in multiple directions does not mean that this automatically works out well when turned on. Layout issues as well as language specific issues are up to macro packages. Omega is not a multi language or multi directional typesetting system by itself, but can be used to build one.
Now, before we start hacking around, and thereby mess up context, we need to figure out a way to deal with these issues, so the main question is how directional typesetting is related to document design.
- directions change per paragraph, rest of doc unchanged
- directions change per document, all components are influenced
- directions change per document, some components are influenced
- etc
so, what should happen with
- page ornaments (headers, footers etc): locations and content
- graphics: placements and content and captions
- tables: structure and content
- mp graphic: text and graphics
- main text: indentation, skips, text, ...
Of course one can say that we need to have all possibilities, but i tend to stick to those that make sense. Are there any resources on for instance right-left book design/typography?
I don't know how many users are interested in these matters; maybe we should discuss this off list
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
-----------------------------------------------------------------
next parent reply other threads:[~2004-07-29 7:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <410D9171@webmail.colostate.edu>
2004-07-29 7:46 ` Hans Hagen [this message]
2004-07-28 14:47 ishamid
2004-07-29 7:10 ` Hans Hagen
2004-07-29 15:37 ` Idris Samawi Hamid
-- strict thread matches above, loose matches on Subject: below --
2004-07-23 17:32 Idris Samawi Hamid
2004-07-28 13:09 ` Hans Hagen
2004-07-22 18:22 ishamid
2004-07-28 13:51 ` 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=4108AB50.3030403@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).