From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: Indic fonts with MkIV and
Date: Sat, 19 Dec 2020 20:06:43 +0100 [thread overview]
Message-ID: <8ada508f-2837-e4cd-e1ce-125d1e2e6036@gmx.es> (raw)
In-Reply-To: <d122ff4f-5611-c722-0017-1dcc1252f0be@zydenbos.net>
On 12/19/20 2:59 PM, Robert Zydenbos wrote:
> On 19.12.20 09:10, Wolfgang Schuster wrote:
>
> YES… YES!
> YES YES YES YES YES YES (I'm trying to express enthusiasm.) That's it!
>
> The remaining question here is: where do I find such magical
> expressions like "features=kannada-one"? (Why "kannada-one"?
> "One"???) If I know that, then (so I assume) I could do the very same
> with the other Indian scripts which I use in my work.
Hi Robert,
this is from font-pre.mkxl (and I assume font-pre.mkiv [I mean, the same
file for MkIV and LMTX).
The features for Indic scripts seem to be (sorry, I’m totally ignorant
outside the Latin or Greek scripts): devanagari-one, bengali-one,
gujarati-one, gurmukhi-one, kannada-one, malayalam-one, oriya-one,
tamil-one, telugu-one.
There are one versions, because they are also two counterparts
(devanagari-two, bengali-two, gujarati-two, gurmukhi-two, kannada-two,
malayalam-two, oriya-two, tamil-two, telugu-two).
What the OpenType specification includes as script tags
(https://docs.microsoft.com/en-us/typography/opentype/spec/scripttags)
contains second versions for what might be some (or all [I’m afraid I
don’t know]) Indic scripts.
Why are second versions? Using their own words:
“The OpenType script tags can also correlate with a particular OpenType
Layout implementation, with the result that more than one script tag may
be registered for a given Unicode script (e.g. 'deva' and 'dev2').”
I hope the description above might help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2020-12-19 19:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 1:47 Robert Zydenbos
2020-12-19 2:42 ` Jairo A. del Rio
2020-12-19 14:06 ` Robert Zydenbos
2020-12-19 8:10 ` Wolfgang Schuster
2020-12-19 13:59 ` Robert Zydenbos
2020-12-19 19:06 ` Pablo Rodriguez [this message]
2020-12-19 19:46 ` Hans Hagen
2020-12-19 20:27 ` Pablo Rodriguez
2020-12-19 21:12 ` Pablo Rodriguez
2020-12-20 0:00 ` Robert Zydenbos
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=8ada508f-2837-e4cd-e1ce-125d1e2e6036@gmx.es \
--to=oinos@gmx.es \
--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).