ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jeong Dal via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Jeong Dal <haksan@me.com>
Subject: Re: context manuals -- absence of \definefontfamily
Date: Tue, 4 Jan 2022 21:53:48 +0900	[thread overview]
Message-ID: <06AE22E3-2C00-4078-96E5-7C7293199A58@me.com> (raw)
In-Reply-To: <mailman.1.1641294002.10048.ntg-context@ntg.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1876 bytes --]

Dear Aditya and Youssef Cherem,

To: Aditya,
> 
> There is the talk that Wolfgang gave in this year's context meeting:
> 
> https://meeting.contextgarden.net/2021/talks/2021-09-23/definefontfamily.pdf
> 
Thank you for letting me know the talk which gives me more understanding about \definefontfamily.

To: Youssef Cherem,

Recently, Wolfgang helped me to define a font family as following, and I hope that it gives you some idea to use \definefontfamily.

\definefallbackfamily [nanum] [rm] [Tex Gyre Pagella]
  [range={basiclatin,latinsupplement,latinextendeda,latinextendedb}, 
   force=yes]
\definefallbackfamily [nanum] [rm] [Noto Serif CJK KR]
  [range={cjkunifiedideographs},force=yes]
\definefontfamily [nanum] [rm] [Nanum Myeongjo OTF]
  [   it={style:regular,features:{*,slanted}},
      bi={style:bold,features:{*,slanted}},force=yes]

Explanation:
1. I use Korean font whose family name is “Nanum Myeongjo OTF” as main font. Since it doesn’t have italic style and bold italic style, I add [it=… , bi=…] to simulate the styles.

2. Since I want to use English character in "TeX Gyre Pagella”. I add it in the first \definefallbackfamily with an option [range={…},force=yes] which restrict the use of font to Latin characters.

3. We use chinese characters also in the Korean sentences. But "Nanum Myeongjo OTF” doesn’t have Chinese characters. So I add another font “Noto Serif CJK KR” which contains Chinese character with the option [range={cjkunified…},force=yes] in the second \definefallbackfamily.

There are two font families more,  sans and mono which is similar as rm.
It is really nice to use \definefontfamily which saves a lot of work to define fonts. 

Thanks Wolfgang.
If there are something should changed in the above definition, please tell me what to do.

Best regards,

Dalyoung



[-- Attachment #1.2: Type: text/html, Size: 7585 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

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

       reply	other threads:[~2022-01-04 12:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1641294002.10048.ntg-context@ntg.nl>
2022-01-04 12:53 ` Jeong Dal via ntg-context [this message]
2022-01-03 20:41 Youssef Cherem via ntg-context
2022-01-03 22:16 ` Hans Hagen via ntg-context
2022-01-03 23:21   ` Aditya Mahajan via ntg-context
2022-01-04 22:07   ` Arthur Rosendahl via ntg-context
2022-01-05  8:01     ` Hans Hagen via ntg-context

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=06AE22E3-2C00-4078-96E5-7C7293199A58@me.com \
    --to=ntg-context@ntg.nl \
    --cc=haksan@me.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).