ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Joel via ntg-context <ntg-context@ntg.nl>
Cc: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Subject: Re: Why isn't bold + italics working together?
Date: Sat, 29 Jan 2022 18:01:00 +0100	[thread overview]
Message-ID: <f9314b95-1f6e-6b8d-533a-5e7455b8f815@gmail.com> (raw)
In-Reply-To: <735410994.1987397.1643467584760@mail.yahoo.com>

Joel via ntg-context schrieb am 29.01.2022 um 15:46:
> I am finishing the final touches on a manuscript, which I hope to send 
> to a publisher later today and noticed this problem where bold and 
> italic text isn't rendered at the same time.
> 
> I am using the EB Garamond font in my document. I set it up exactly as 
> shown below. Strangely, bold works, italics works, but when bold and 
> italics are together, it only display in italics, it doesn't display a 
> bold italic text. I've confirmed the `EBGaramond-BoldItalic.otf` font is 
> present and seems just fine. I've also tried by just using the default 
> ConTeXt font and the error still appears, also in 
> live.contextgarden.net. I tried searching the mailing list, as this 
> seems like something that must have come up, but couldn't find any 
> question about this.
> 
> Why won't it render both?

See Adams answer.

> \starttypescript[serif] [garamond]
> \definefontsynonym[Serif] [file:~/.fonts/12/EBGaramond-Regular.otf]
> \definefontsynonym[SerifBold] [file:~/.fonts/12/EBGaramond-Bold.otf]
> \definefontsynonym[SerifItalic] [file:~/.fonts/12/EBGaramond-Italic.otf]
> \definefontsynonym[SerifBoldItalic] [file:~/.fonts/12/EBGaramond-BoldItalic.otf]
> \stoptypescript

Don't use absolute paths in \definefontsynonym, when you use a local 
folder for your font files set the path with \usefontpath.

%%%% begin snippet
\usefontpath [~/fonts/12/]

\starttypescript [serif] [garamond]
     \definefontsynonym [Serif] [file:EBGaramond-Regular.otf]
     ...
\stoptypescript
%%%% end snippet

Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________

      parent reply	other threads:[~2022-01-29 17:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <735410994.1987397.1643467584760.ref@mail.yahoo.com>
2022-01-29 14:46 ` Joel via ntg-context
2022-01-29 16:19   ` Adam Reviczky via ntg-context
2022-01-29 16:57     ` Wolfgang Schuster via ntg-context
2022-01-29 17:03       ` Denis Maier via ntg-context
2022-01-29 22:21         ` Otared Kavian via ntg-context
2022-01-29 17:01   ` Wolfgang Schuster via ntg-context [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=f9314b95-1f6e-6b8d-533a-5e7455b8f815@gmail.com \
    --to=ntg-context@ntg.nl \
    --cc=wolfgang.schuster.lists@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).