ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: Issue with italics
Date: Mon, 26 Feb 2024 15:02:34 +0100	[thread overview]
Message-ID: <D3DBD31C-626E-4BE6-B417-AF410B746D2F@uni-bonn.de> (raw)
In-Reply-To: <17C43816-195C-4B1C-AA12-90B5F6B61FC0@free.fr>

I just tried your example with the latest version of GFSDidot (the older version I had on my system did not show some diacritics; this problem disappeared when I installed the latest), and the italics are there, I don’t see any problem in the pdf. If you want the Greek displayed in Theano, you will have to add “force=yes” to your definition of the fallback family:

\definefallbackfamily
    [mainface]
    [rm]
    [Theano Didot]
    [preset=range:greek,force=yes]

Your text cannot have two main languages, so 

\mainlanguage[fr]

If you want hyphenation for your Greek passages, you can add

\setuplanguage [fr] [patterns={fr,agr}]

The line where you have polytonic Greek does not use precomposed characters, but combinations of greek characters and diacritics; this will probably not work in recent context versions that expect actual unicode input. 

I hope I have really understood what you want: GFSDIdot for the French text and Theano for Greek?

HTH

Thomas

> On 26. Feb 2024, at 13:32, Jean-Pierre Delange <adeimantos@free.fr> wrote:
> 
> Dear list,
> 
> When handling the preamble to a document in which I would like to treat the text in French, with sometimes italics text and phrases in ancient Greek, I encounter the following difficulty:
> if I use TeX Gyre Pagella as the main font, everything works fine, except for the Ancient Greek text, which I don't like the look of. But the Greek text is displayed, as are the French italics. On the other hand, if I use GFS Didot as the main font and Theano Didot for the Greek, the italics disappear and the Greek text looks better. The CTX version I use is: mtx-context | current version: 2024.01.24 22:39.
> 
> Herewith are two MWE attachments (*.tex + *.pdf) with different fonts. What am I missing ? Thanks for your answers.
> 
> JP



___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2024-02-26 14:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 12:32 [NTG-context] " Jean-Pierre Delange
2024-02-26 13:03 ` [NTG-context] " Denis Maier via ntg-context
2024-02-26 13:09   ` Denis Maier via ntg-context
2024-02-26 14:02 ` Thomas A. Schmitz [this message]
2024-02-26 17:41   ` Jean-Pierre Delange
2024-02-26 17:53     ` Wolfgang Schuster
2024-02-26 18:09       ` Jean-Pierre Delange

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=D3DBD31C-626E-4BE6-B417-AF410B746D2F@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.de \
    --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).