From: Yue Wang <yuleopen@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Hans Hagen <pragma@wxs.nl>
Subject: bug in \setuparranging
Date: Thu, 22 Sep 2011 02:07:57 -0400 [thread overview]
Message-ID: <CA+C1juaam7q1EGjss87aT94xD2f6wKGtkg3fwbQFm=q-xb6Caw@mail.gmail.com> (raw)
Hi, Hans:
There's a bug in \setuparranging.
The following case is easy to be understood:
- I try to typeset "zapf" into a A4 landscape paper
- For the final output pdf, I want to rotate all the pages by 270 degrees.
This sounds strange. But it is useful in vertical typesetting of CJK
language. (for example, use xetex font definition's :vertical feature
to rotate all the fonts used, typeset on normal paper, and rotate the
page back. I certainly hope someday I can use MKIV's muti-dir omega
features, but now it's broken so this is the best way I can find)
The code is listed below:
\setuppapersize[A4,landscape][A4]
\setuppaper [nx=1,ny=1]
\setuparranging [XY, rotated, 270]
\setupcolors [state=start]
\setupbackgrounds [page][page][background=screen]
\setuppagenumbering [state=stop]
\starttext
\input zapf
\stoptext
The bug:
- in MKIV, it output no pages at all
- in MKII (both xetex and pdftex), the output page is not, however,
A4. but rather a square page with width=height=A4 height.
I hope this bug can be fixed soon.
By the way, are there other ways to rotate pages other than
setuparranging? From my daily use I found setup arranging is pretty
buggy. sometimes it even affects the layout of the contents. So most
time I have to compile a pdf, and than use setup arranging to
rearrange the pdf again to make the contents safe.
Yue Wang
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2011-09-22 6:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 6:07 Yue Wang [this message]
2011-09-22 8:54 ` Yue Wang
2011-09-22 16:38 ` Aditya Mahajan
2011-09-22 20:34 ` Yue Wang
2011-09-22 20:46 ` Aditya Mahajan
2011-09-22 20:59 ` Yue Wang
2011-09-22 21:04 ` Aditya Mahajan
2011-10-02 2:10 ` Yue Wang
2011-10-02 7:46 ` Wolfgang Schuster
2011-10-03 17:15 ` Yue Wang
2011-10-03 17:49 ` Hans Hagen
2011-10-03 18:51 ` Yue Wang
2011-10-03 18:07 ` Wolfgang Schuster
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='CA+C1juaam7q1EGjss87aT94xD2f6wKGtkg3fwbQFm=q-xb6Caw@mail.gmail.com' \
--to=yuleopen@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).