From: Idris Samawi Hamid <ishamid@attbi.com>
Subject: Gamma bugs
Date: Sat, 04 May 2002 18:20:23 -0600 [thread overview]
Message-ID: <FBB9KGSO09SMKID8DCWRMKJG63QNH2U.3cd47ac7@c1909372-a> (raw)
In-Reply-To: <87adrfljtn.fsf@gundla.ch>
Dear ConTeXtnicians,
In Gamma (ConTeXt compiled with Omega: texexec --make --alone --tex=omega en) it appears that the Omega's otp execution interferes with a number of ConTeXt's
macros which are not sufficiently insulated. Consider the two files con-test3.tex and type-xxx.tex (cmss is the base font):
%=========con-test3=================
\usetypescriptfile[type-xxx]
\usetypescript[arabtest]
\setupbodyfont[omarab,10pt]
\def\latinunicode{\ocp\BasicLatinTexUni=lat2uni
\ocp\BasicLatinUniToFont=uni2lat
\ocplist\BasicLatinOCP=
\addbeforeocplist 1 \BasicLatinTexUni
\addbeforeocplist 1 \BasicLatinUniToFont
\nullocplist
\pushocplist\BasicLatinOCP}
\def\texencoding{\clearocplists}
%\latinunicode
\showframe[text]
\starttext%
\showbodyfont%
\showbodyfontenvironment[omarab]
This is a test {\bfc This is a test} {\tfc This is a test} {\tfx This is a
test}
\switchtobodyfont[12pt] This is a test {\tfc This is a test}
\switchtobodyfont[big] This is a test {\tfc This is a test}
\switchtobodyfont[small] This is a test {\tfc This is a test}
\switchtobodyfont[8pt] This is a test {\tfc This is a test}
\switchtobodyfont[10pt] This is a test {\tfc This is a test}
\switchtobodyfont[12pt] This is a test {\tfc This is a test}
\switchtobodyfont[global] This is a test {\tfc This is a test}
\stoptext
%=========type-xxx==================
\starttypescript [naskh] [omega] [name]
\definefontsynonym [OmegaArabic] [cmss10] % [omarab]
\definefontsynonym [OmegaArabic-Bold] [cmssbx10] % [omarabb]
\definefontsynonym [Naskh] [OmegaArabic]
\definefontsynonym [NaskhBold] [OmegaArabic-Bold]
\stoptypescript
\starttypescript [naskh] [omega] [size]
\definebodyfont
[20.7pt,17.3pt,14.4pt,12pt,11pt,10pt,9pt,8pt,7pt,6pt]
[rm]
[tf=Naskh sa 1,
bf=NaskhBold sa 1]
\stoptypescript
\starttypescript [arabtest]
\definebodyfontenvironment
[omarab]
[default]
[interlinespace=2.8ex]
\definetypeface [omarab] [rm] [naskh] [omega] [omega] %[rscale=1.6]
\stoptypescript
===========================
If you leave \latinunicode uncommented then con-test3 will compile like an ordinary ConTeXt job. Uncomment it and funny things happen:
1. Whenever the text size is whatever size \setupbodyfont defaults to, \tfa, \tfb, \tfc, and \tfd will do nothing at all. So in con-test3,
\switchtobodyfont[10pt] This is a test {\tfc This is a test}
will reproduce <This is a test> twice at 10pt. Interestingly, \tfx and \tfxx work fine. If you change the setup to \setupbodyfont[omarab,12pt] then the line
\switchtobodyfont[12pt] This is a test {\tfc This is a test}
will reproduce <This is a test> twice at 12pt.
This is really weird. I am at a loss at where to start. Where are \tf<variable> defined so that I can look at the \def's and see if I can modify them somehow (though
ConTeXt's macros are really scary)?
Hans mentioned that omega crashes on his system but I hope he or someone else here can test this and help me find an answer.
2. I mentioned the once before but I was rather unclear then and hope to be more clear and also more general this time:
\showlayout, \showbodyfont, and \showbodyfontenvironment[omarab] do funny things when the otp's are loaded. \showlayout actually causes omega to crash.
\showgrid does not print the margin numbers (probably because they are isolated from the otp list). I think the solution is to
a. make sure the macros are isolated from the otp's being executed (although the grid line numbers in \showgrid are an exception here);
b. give an option to these commands for which font to print the chart out in general. For example, \showbodyfontenvironment[omarab][cmr] would mean to print the
fontenvironment table in cmr. \showbodyfont[omarab][cmr][\myocplist bt] would show sample characters transcribed by `b' and `t' from omarab but print the table and
verbatim commands in cmr. \myocplist would have to grouped so it affects nothing but the sample characters.
I am rather afraid to mess around with the ConTeXt macros myself. They look rather frightening. Please don't make me do it:-)..
Your help is greatly appreciated!
Best wishes
Idris
==========================
Dr. Idris Samawi Hamid
Depatment of Philosophy
Colorado State University
Fort Collins, CO 80526
next prev parent reply other threads:[~2002-05-05 0:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-30 20:58 Non breaking small space Nigel King
2002-05-02 14:12 ` John Culleton
2002-05-03 23:09 ` Nigel King
2002-05-06 0:09 ` Hans Hagen
2002-05-06 19:31 ` "LaTeX compatibility module" (was: Non breaking small space) Henning Hraban Ramm
2002-05-08 0:28 ` Idris Samawi Hamid
2002-05-08 8:59 ` Taco
2002-05-06 0:11 ` Non breaking small space Hans Hagen
2002-05-06 12:53 ` Eckhart Guthöhrlein
2002-05-06 12:58 ` John Culleton
2002-05-04 20:49 ` Patrick Gundlach
2002-05-05 0:20 ` Idris Samawi Hamid [this message]
2002-05-05 1:46 ` defining environments Idris Samawi Hamid
2002-05-05 10:11 ` Henning Hraban Ramm
2002-05-05 11:32 ` Patrick Gundlach
2002-05-05 23:34 ` Gamma bugs Hans Hagen
2002-05-09 19:49 ` Non breaking small space 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=FBB9KGSO09SMKID8DCWRMKJG63QNH2U.3cd47ac7@c1909372-a \
--to=ishamid@attbi.com \
/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).