From: Idris Samawi Hamid <ishamid@colostate.edu>
Subject: bug in latest ConTeXt?
Date: Fri, 02 Jul 2004 12:51:58 -0600 [thread overview]
Message-ID: <opsaixcwtsu9mfh0@lamar.colostate.edu> (raw)
Hi syndicate,
I have found a serious problem in the latest ConTeXt: when using
\rotate[]{}, \raise does not seem to work probably. Consider the
following example, simplified from a larger macro:
=============test-rotate-c.tex================
\def\cupd{\leavevmode\rotate[rotation=180]{c}} % ConTeXt dependent!
\def\HAMZAH{\leavevmode\raise.9ex\hbox{\txx\cupd}{}}
\def\AYN {\leavevmode\raise.9ex\hbox{\txx c}{}}
\def\'{\HAMZAH}
\def\`{\AYN}
\starttext
\`ish\=a\'
\stoptext
=============================================
In ConTeXt-2003.2.11, both the `c' and the rotated `c' appear at
the same height. In the latest ConTeXt the rotated `c' is not as
high as the normal `c'.
Please advise;-)
Best
Idris
--
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
next reply other threads:[~2004-07-02 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 18:51 Idris Samawi Hamid [this message]
2004-07-06 23:01 ` Idris Samawi Hamid
2004-07-07 8:50 ` 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=opsaixcwtsu9mfh0@lamar.colostate.edu \
--to=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).