From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \definebodyfont not working for \typesetbuffer
Date: Sun, 16 Oct 2016 20:07:27 +0200 [thread overview]
Message-ID: <21c93365-2ef0-e127-56f8-5fe3efc0f487@gmx.es> (raw)
In-Reply-To: <5803BFF3.9000901@gmail.com>
On 10/16/2016 07:59 PM, Wolfgang Schuster wrote:
>> Pablo Rodriguez 16. Oktober 2016 um 19:56
>> [...]
>> As suggested by Wolfgang, \definebodyfont should work. It worked then
>> (https://mailman.ntg.nl/pipermail/ntg-context/2016/085260.html), but it
>> doesn’t work with latest beta from 2016.10.14 17:19.
>>
>> Could you confirm whether it is a bug or I am missing something?
>
> You have to put the command in the buffer because \typesetbuffer saves
> the content in a external file and which is then processed as separate
> document which doesn’t use settings from the main document.
Wolfgang,
I did it before sending the message and it didn’t work.
\startbuffer[buffer:inside]
\definebodyfont[17pt]
\definefontfamily[mainface][rm][TeX Gyre Pagella]
\setupbodyfont[mainface, 17pt]
\starttext
\input zapf
\stoptext
\stopbuffer
\starttext
\typesetbuffer[buffer:inside]
\stoptext
Neither does it work now.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-10-16 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 17:56 Pablo Rodriguez
2016-10-16 17:59 ` Wolfgang Schuster
2016-10-16 18:07 ` Pablo Rodriguez [this message]
2016-10-16 18:16 ` Wolfgang Schuster
2016-10-16 18:56 ` Pablo Rodriguez
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=21c93365-2ef0-e127-56f8-5fe3efc0f487@gmx.es \
--to=oinos@gmx.es \
--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).