From: Willi Egger <w.egger@boede.nl>
Subject: Re: Fonts in Metapost
Date: Sat, 02 Jul 2005 13:58:34 +0200 [thread overview]
Message-ID: <42C6816A.4030302@boede.nl> (raw)
In-Reply-To: <42C66C48.4030209@student.kuleuven.be>
Hi Wolfgang,
usually I compile the MetaPost fiures into a pdf. I refer to the
pictures then by \externalfigure[metapost-pdf][page=1] or similar.
Willi
Wolfgang Zillig wrote:
> Hello all,
>
> finaly I solved my problem: I had my metapost graphic in an external
> file and used it with:
>
> \startuseMPgraphic{test}
> \input mp.mp ;
> \stopuseMPgraphic
>
> \useMPgraphic{test}
>
> or
>
> \startbuffer[test1]
> \input mp.mp
> \stopbuffer
>
> \processMPbuffer[test1,graphic]
>
> in both cases I get the graphic but the font switching does not work.
> When I copy the content of my graphic file into "\startuseMPgraphic
> \stopuseMPgraphic" or "\startbuffer \stopbuffer" I works. Is there an
> explanation for this behaviour? I thought \input would be equal to
> typing it directly.
>
> What is the best way to handle multiple graphics when I want to use the
> font switching mechanismn? Any advice?
>
> Thanks alot
> Wolfgang
>
> Willi Egger wrote:
>
>> Hi Wolfgang,
>>
>> I do hope that I am not missing something. But I think, that you
>> should say in the MPenvironment:
>> \setupbodyfont[Cmbr,12pt]
>>
>> Otherwise the setupbodyfont command does not know which font to setup.
>>
>> Willi
>>
>> Wolfgang Zillig wrote:
>>
>>> Hello,
>>>
>>> I have problems with changeing the font in Metapost. I defined my own
>>> typescripts somewhere and I also have a mapfile for that fonts. In
>>> normal text it workes fine (even math).
>>>
>>> Now I want to change the font in MP as well (my text is included as
>>> label("test",(200,200));):
>>>
>>> %normal stups:
>>> \loadmapfile[cmbright.map] %it seems that the mapfile is loaded
>>> only once
>>> \usetypescriptfile[type-cmbr]
>>> \usetypescript[Cmbr]
>>> \setupbodyfont[12pt]
>>>
>>> \startMPenvironment
>>> \loadmapfile[cmbright.map] %it seems that the mapfile is loaded
>>> only once
>>> \usetypescriptfile[type-cmbr]
>>> \usetypescript[Cmbr]
>>> \setupbodyfont[12pt]
>>> \stopMPenvironment
>>>
>>> But I always get the standard CMR output.
>>>
>>> Did I miss a step somewhere?
>>>
>>> Has anyone an idea what's going wrong?
>>>
>>> Thanks for any help!
>>>
>>> Wolfgang
>>>
>>>
>>> _______________________________________________
>>> ntg-context mailing list
>>> ntg-context@ntg.nl
>>> http://www.ntg.nl/mailman/listinfo/ntg-context
>>
>>
>> _______________________________________________
>> ntg-context mailing list
>> ntg-context@ntg.nl
>> http://www.ntg.nl/mailman/listinfo/ntg-context
>>
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2005-07-02 11:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 16:01 Wolfgang Zillig
2005-07-01 16:58 ` Willi Egger
2005-07-01 17:44 ` Wolfgang Zillig
2005-07-02 10:28 ` Wolfgang Zillig
2005-07-02 11:58 ` Willi Egger [this message]
2005-07-02 20:34 ` Willi Egger
2005-07-03 10:49 ` Wolfgang Zillig
2005-07-03 17:26 ` Willi Egger
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=42C6816A.4030302@boede.nl \
--to=w.egger@boede.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).