ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Monospace Fonts for Verbatim
Date: Tue, 10 Jan 2006 14:25:12 +0100	[thread overview]
Message-ID: <43C3B5B8.4000504@wxs.nl> (raw)
In-Reply-To: <1C7A1FE7-90DC-4A1F-A2E6-31F6815A5EA8@louspringer.com>

Louis Springer wrote:

> I have a typescript I am using for a custom font, but the custom font  
> has no monospace variant appropriate for verbatim text. I'm  
> attempting to use Courier or some other monospace font for verbatim  
> and maintain my custom font for normally typeset serf text.
>
> My broken typescript is as follows:
>
> \starttypescript [map][sunsans,sunserif][texnansi]
> \loadmapfile[texnansi-sun-sunsans.map]
> \loadmapfile[texnansi-sun-sunserif.map]
> \stoptypescript
>
> % sans serif
> \starttypescript [sans] [sunsans] [name]
> \definefontsynonym[Sans]                [SunSans-Regular]
> \definefontsynonym[SansItalic]            [SunSans-Italic]
> \definefontsynonym[SansBold]            [SunSans-RegularDemi]
> \definefontsynonym[SansBoldItalic]        [SunSans-Regular-BoldOblique]
> \stoptypescript
>
>
> \starttypescript [sans] [sunsans] [texnansi]
> \usetypescript[sans][fallback]
> \definefontsynonym[SunSans-Heavy][texnansi-SunSans-Heavy] 
> [encoding=texnansi]
> \definefontsynonym[SunSans-Italic][texnansi-SunSans-Italic] 
> [encoding=texnansi]
> \definefontsynonym[SunSans-Regular-Bold][texnansi-SunSans-Regular- 
> Bold][encoding=texnansi]
> \definefontsynonym[SunSans-Regular-BoldOblique][texnansi-SunSans- 
> Regular-BoldOblique][encoding=texnansi]
> \definefontsynonym[SunSans-Regular][texnansi-SunSans-Regular] 
> [encoding=texnansi]
> \definefontsynonym[SunSans-RegularDemi][texnansi-SunSans-RegularDemi] 
> [encoding=texnansi]
> \stoptypescript
>
>
> %serif
> \starttypescript [serif] [sunserif] [name]
> \definefontsynonym[Serif]                [SunSerif-Regular]
> \definefontsynonym[SerifItalic]            [SunSerif-Italic]
> \definefontsynonym[SerifBold]            [SunSerif-Regular-Bold]
> \definefontsynonym[SerifBoldItalic]        [SunSerif-Regular-Bold-Italic]
> \stoptypescript
>
>
> \starttypescript [serif] [sunserif] [texnansi]
> \usetypescript[serif][fallback]
> \definefontsynonym[SunSerif-Italic][texnansi-SunSerif-Italic] 
> [encoding=texnansi]
> \definefontsynonym[SunSerif-Regular-Bold-Italic][texnansi-SunSerif- 
> Regular-Bold-Italic][encoding=texnansi]
> \definefontsynonym[SunSerif-Regular-Bold][texnansi-SunSerif-Regular- 
> Bold][encoding=texnansi]
> \definefontsynonym[SunSerif-Regular][texnansi-SunSerif-Regular] 
> [encoding=texnansi]
> \stoptypescript
>
> %monospace
> \starttypescript [mono] [sunserif] [name]
> \usetypescript[mono][fallback]
> \definefontsynonym[Serif]                [Mono]
> \stoptypescript

hm, why this way? (It's Mono btw)

>
>
> The last bit (around the comment "monospace") is my apparently futile  
> attempt to get the verbatim to use the default monospace font. I get  
> the desired results with a kludge if I replace
>
> \definefontsynonym[Serif]                [SunSerif-Regular]
>
> with
>
> \definefontsynonym[Serif]                [Mono]
>
> but this affects "normally" typeset serif. Ideally,  I would like to  
> have in the  SunSerif-Regular typeface for non-verbatim serif text.

\definetypeface[somesun][rm][serif][sunserif][default]
\definetypeface[somesun][ss][sans][sunsans][default]
\definetypeface[somesun][tt][mono][modern][default][rscale=.9]
\definetypeface[somesun][mm][math][modern][default][rscale=.9]

so, you don't need to define some fake sun mono

Hans

      parent reply	other threads:[~2006-01-10 13:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-07 16:57 Louis Springer
2006-01-07 20:46 ` Willi Egger
2006-01-10 13:25 ` Hans Hagen [this message]

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=43C3B5B8.4000504@wxs.nl \
    --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).