From: Otared Kavian via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Otared Kavian <otared@gmail.com>
Subject: Re: Metafun, difficulty with graphical element in the margin
Date: Sat, 19 Mar 2022 16:52:36 +0100 [thread overview]
Message-ID: <7FAAE442-1CCD-474D-966F-6A77F9D672F8@gmail.com> (raw)
In-Reply-To: <C21D2BAD-A970-4621-B1A7-564979E22190@boede.nl>
Hi Willi,
Your test file works fine if I place
\setups{Thumb-pictures}
before \starttext (using version 2022.03.12 17:56 LMTX).
However in the file you sent the choice of the command
\setups{Thumb-pictures}
is between chapter A and B, which seems starnge to me...
Best regards: Otared K.
> On 18 Mar 2022, at 20:29, Willi Egger via ntg-context <ntg-context@ntg.nl> wrote:
>
> Good evening!
>
> I have a dictionary where I would like to include thumb-pictures in the margin. — When I use the attached code with a single \startchapter...\stopchapter, it works. However if I add another \startchapter…\stopchapter before loading the setups for the thumb-picture metafun throws an error about not having complete information for performing a transformation.
>
> I am currently using the before last version of LMTX-ConTeXT (January 21st 2022).
>
> Could someone try to compile?
>
> Thanks, kind regards
>
> Willi<test-thumb-picture.tex><test-thumb-picture.pdf>___________________________________________________________________________________
> 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:[~2022-03-19 15:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 19:29 Willi Egger via ntg-context
2022-03-19 5:41 ` śrīrāma via ntg-context
2022-03-19 8:39 ` Hans Hagen via ntg-context
2022-03-19 15:52 ` Otared Kavian via ntg-context [this message]
2022-03-19 20:42 ` Willi Egger via ntg-context
2022-03-19 22:39 ` Otared Kavian via ntg-context
2022-03-20 15:46 ` Willi Egger via ntg-context
2022-03-20 10:28 ` Wolfgang Schuster via ntg-context
2022-03-20 15:53 ` Willi Egger via ntg-context
2022-03-20 16:00 ` Wolfgang Schuster via ntg-context
2022-03-20 16:05 ` Willi Egger via ntg-context
2022-03-20 16:21 ` Wolfgang Schuster via ntg-context
2022-03-21 9:04 ` Willi Egger via ntg-context
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=7FAAE442-1CCD-474D-966F-6A77F9D672F8@gmail.com \
--to=ntg-context@ntg.nl \
--cc=otared@gmail.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).