From: Alan Braslau <braslau.list@comcast.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Compilation problem with the latest version of standalone context(Metafun)
Date: Tue, 17 Jul 2018 15:00:28 -0600 [thread overview]
Message-ID: <E5FD8D7D-80F0-43D9-9582-27C6548221F2@comcast.net> (raw)
In-Reply-To: <b82cf9d6-c9c9-2e71-49b0-573e5b9d902d@rik.users.panix.com>
\startusableMPgraphic ?
> On 17 Jul 2018, at 14:46, Rik Kabel <context@rik.users.panix.com> wrote:
>
> On 7/17/2018 16:40, Hans Hagen wrote:
>> On 7/17/2018 10:30 PM, Rik wrote:
>>> On 7/16/2018 10:24, Fabrice Couvreur wrote:
>>>> % macros=mkvi
>>>>
>>>> \setuppagenumbering[location=footer]
>>>>
>>>> \startusableMPgraphic{NumberHead}
>>>> draw outlinetext.f
>>>> ("\bf\namedheadnumber{chapter}")
>>>> (withcolor "lightgray")
>>>> ysized 50pt ;
>>>> \stopusableMPgraphic
>>>>
>>>>
>>>> \unexpanded\def\processMPheadnumber#1%
>>>> {\useMPgraphic{NumberHead}}
>>>>
>>>> \setuphead
>>>> [chapter]
>>>> [command=\HeadTitle,
>>>> headstyle=\ss,
>>>> numbercommand=\processMPheadnumber]
>>>>
>>>>
>>>> \unexpanded\def\HeadTitle#1#2%
>>>> {\framed
>>>> [frame=off,
>>>> bottomframe=on,
>>>> width=broad,
>>>> align={broad,nothyphenated,left}]
>>>> {#1\blank[nowhite]#2}}
>>>>
>>>> \starttext
>>>>
>>>> \dorecurse{6}{\startchapter
>>>> [title={Fist chapter}]
>>>> \input knuth
>>>> \stopchapter}
>>>>
>>>> \stoptext
>>>
>>> Using TL18 on Win64 it produces a large chapter number on the right side above the chapter name -- I do not know what it should look like, so I won't say it works. It clearly fails with the 2018-07-13 beta, producing an odd graphic where the MP-generated digit should be:
>>>
>>> and fails in the same manner with the 2018-07-17 beta.
>> define 'fails' ... a crash? can someone confirm it?
> By failure, I meant that it produces the graphic I posted, a bold outline around a small square in the area in which the enlarged digit is expected. Not a crash.
>
> --
> Rik
>
> ___________________________________________________________________________________
> 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://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-07-17 21:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 14:24 Fabrice Couvreur
2018-07-16 17:27 ` Hans Hagen
2018-07-16 17:42 ` Fabrice Couvreur
2018-07-17 10:36 ` Fabrice Couvreur
2018-07-17 15:43 ` Hans Hagen
2018-07-17 19:03 ` Pablo Rodriguez
2018-07-17 20:37 ` Fabrice Couvreur
2018-07-17 20:30 ` Rik
2018-07-17 20:40 ` Hans Hagen
2018-07-17 20:46 ` Rik Kabel
2018-07-17 21:00 ` Alan Braslau [this message]
2018-07-17 21:06 ` Hans Hagen
2018-07-18 8:35 ` Fabrice Couvreur
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=E5FD8D7D-80F0-43D9-9582-27C6548221F2@comcast.net \
--to=braslau.list@comcast.net \
--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).