From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: hanneder--- via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: [NTG-context] Commercial fonts and diacritics
Date: Thu, 1 Jun 2023 12:42:59 +0200 [thread overview]
Message-ID: <077002ce-f4e9-5917-8352-d578c7abdb75@freedom.nl> (raw)
In-Reply-To: <20230601114727.Horde.eXn7gsvVtH2HeYAkm1kj-nJ@home.staff.uni-marburg.de>
On 6/1/2023 11:47 AM, hanneder--- via ntg-context wrote:
>
> I feel that I should have solved the following question myself---I have
> a long history of making
> diacritics for Sanskrit work in different incarnations of TeX since
> 1991---but I have never
> understood the technicalities of otf fonts.
>
> Currently I am trying to use high quality Adobe Fonts for Sanskrit
> texts, which need the following
> diacritics: āīūṛś ḍḷṭṣṃḥṛṝṣṅṇ (ideally also with capitals). The font
> Adobe Text Pro prints them
> perfectly, but Minion Pro does not.
>
> However, if you enter your own text on the fontshop website, it seems to
> work, and this is why I
> prematurely bought yet another new version of Minion Pro, hoping that it
> would work this time.
>
> If you look at font with fontforge, many utf code positions for Indic
> Transliteration are empty,
> i.e. Minionpro does not have the characters with diacritics, Adobe Text
> Pro has them. So far, so
> good (or not).
>
> The hotline of fontshop.com thinks that there is an OpenType feature
> that creates so-called
> Composits out of the elements. I can understand the mechanism, I guess I
> have tweaked something
> similar in pdflatex or OmegaTeX in the pre-otf era, but I have no idea
> whether one of these
> mechanism can be utilised in Xe-, Lua- Or ConTeXt nowadays. I was hoping
> that some fontfeatures
> (fakecombining=yes,compose=yes) would do the trick, but apparently they
> do not.
>
> In a sense this is no big deal. There are many nice fonts around (and
> those that come with ConTeXt
> are great), but I was used to printing books with an old Type-1 Minion
> (www.ctan.org/pkg/w-a-schmidt) and find it hard to accept that this
> should not be possible with the
> modern flavours of TeX.
>
>
> My system:
>
> This is LuaTeX, Version 1.16.0 (TeX Live 2023/Arch Linux)
> open source > level 1, order 1, name
> '/usr/share/texmf-dist/tex/context/base/mkiv/cont-yes.mkiv'
Can you try context lmtx instead? I get the dots there.
> Minimal example:
>
> \enableregime[utf]
^^ no need for this, it's the default
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2023-06-01 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 9:47 hanneder--- via ntg-context
2023-06-01 10:42 ` Hans Hagen 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=077002ce-f4e9-5917-8352-d578c7abdb75@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).