From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Gamma bugs
Date: Mon, 06 May 2002 01:34:42 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20020506012758.02d32cf0@remote-1> (raw)
In-Reply-To: <FBB9KGSO09SMKID8DCWRMKJG63QNH2U.3cd47ac7@c1909372-a>
At 06:20 PM 5/4/2002 -0600, Idris Samawi Hamid wrote:
>%=========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}
this kind of defs are best done with the filter definition macros
>\def\texencoding{\clearocplists}
so, is \clearocplists a primitive ? [can you mail me a properly pdf'd or
ps'd manual of omega; i can only generate an ugly unreadable bitmap version
with missing charactrers]
>If you leave \latinunicode uncommented then con-test3 will compile like an
>ordinary ConTeXt job. Uncomment it and funny things happen:
hm, maybe we need to hook some otp disabling code to the framework that
reads system files
\
>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.
the latest fptex binaries work, so i can now generate an omega format (at
the cost of large mem values)
>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
this maybe due to otp lookahead (omega is a hungry program); i got quite
some \CLOBBERED (funny enough an undefined primitive) messages to the screen;
>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.
that's for later,
>I am rather afraid to mess around with the ConTeXt macros myself. They
>look rather frightening. Please don't make me do it:-)..
not needed, there are enough hooks to get things done properly
btw, adding
\definetypeface [omarab] [tt] [mono] [computer-modern] [default]
to the xxx file helps -)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-05-05 23:34 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 ` Gamma bugs Idris Samawi Hamid
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 ` Hans Hagen [this message]
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=5.1.0.14.1.20020506012758.02d32cf0@remote-1 \
--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).