From: Jeong Dal <haksan@me.com>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: removing many lines about font in log.
Date: Tue, 10 Nov 2020 22:46:21 +0900 [thread overview]
Message-ID: <50C805A5-BF8F-4D15-8975-C0F8CE85A9F2@me.com> (raw)
In-Reply-To: <5cd0e1b1-4f2f-2b02-1b42-9f76be9b9b3b@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2107 bytes --]
Dear Hans,
Thank you for the explanation.
Since those messages takes too many lines in the log file, I ask about it.
I prefer to suppress them. But, someone want to see them.
Since there is no problem to compile, it is OK to let them shown for some one want to know what happened.
Best regards,
Dalyoung
> 2020. 11. 10. 오전 1:12, Hans Hagen <j.hagen@xs4all.nl> 작성:
>
> On 11/8/2020 8:05 PM, Jeong Dal wrote:
>> Hi,
>> The following example creates so many lines of messages about fonts in the log.
>> \definefontfeature [default] [default] [script=hang,language=kor]
>> \starttext
>> \definedfont[file:notoserifcjkkrregular*default]
>> Korean sentences.
>> 한글이 아름답습니다.
>> \stoptext
>> fonts > 'fallback modern-designsize rm 12pt' is loaded
>> fonts > defining > font 'notoserifcjkkrregular', feature 'vert', script 'grek', no language 'kor'
>> fonts > defining > font 'notoserifcjkkrregular', feature 'vert', script 'latn', no language 'kor'
>> fonts > defining > font 'notoserifcjkkrregular', feature 'vert', script 'kana', no language 'kor'
>> fonts > defining > font 'notoserifcjkkrregular', feature 'vert', script 'cyrl', no language 'kor'
>> fonts > defining > font 'notoserifcjkkrregular', feature 'vert', script 'dflt', no language 'kor'
>> fonts > defining > f
>> ...
>> Is there a way to suppress messages?
>> Of course, there is no problem to get the output.
> it depends if you're interested in it ... i kept it for cases where users expect some feature to work while the font doesn't have it but I have no problem making it optional
>
> Hans
>
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl <http://www.pragma-ade.nl/> | www.pragma-pod.nl <http://www.pragma-pod.nl/>
> -----------------------------------------------------------------
[-- Attachment #1.2: Type: text/html, Size: 11775 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
___________________________________________________________________________________
next prev parent reply other threads:[~2020-11-10 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.560.1604837317.1206.ntg-context@ntg.nl>
2020-11-08 19:05 ` Jeong Dal
2020-11-09 16:12 ` Hans Hagen
2020-11-10 13:46 ` Jeong Dal [this message]
2020-11-10 17:02 ` Aditya Mahajan
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=50C805A5-BF8F-4D15-8975-C0F8CE85A9F2@me.com \
--to=haksan@me.com \
--cc=j.hagen@xs4all.nl \
--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).