From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Missing "missing character" warning
Date: Fri, 25 May 2012 09:50:00 +0200 [thread overview]
Message-ID: <CAG5iGsBcY1UB15264+D0h2YW2Uayw2caoG=YK=-DcqDY=OzjOA@mail.gmail.com> (raw)
In-Reply-To: <CAG5iGsDZ1BLy_TAF3RH9_FtpvVBnJdMtRAyDAy-cmPJbT9SWZw@mail.gmail.com>
On Fri, May 25, 2012 at 9:45 AM, luigi scarso <luigi.scarso@gmail.com> wrote:
> On Fri, May 25, 2012 at 9:40 AM, Hans Hagen <pragma@wxs.nl> wrote:
>> On 25-5-2012 09:15, Marco Pessotto wrote:
>>>
>>>
>>> Hello all.
>>>
>>> Reading the manual “Fonts in ConTeXt” I found the following statement
>>> (p.97):
>>>
>>> “In both cases we end up with a message in the log file and a resulting
>>> file with missing data”. [When the font doesn't provide a glyph].
>>>
>>> Now, the only case when the warning is issued is using mkii with xetex
>>> (texexec -xtx), not with mkiv. (Unsurprisingly, the file with missing
>>> data is always there :-)
>>>
>>> Minimal example:
>>>
>>> %% start
>>> \mainlanguage[hr]
>>>
>>> \starttext
>>> Ja sam sȃm, i sȃm sam došao da izvršim pravdu.
>>> \stoptext
>>> %% stop
>>>
>>> The name of the char is: LATIN SMALL LETTER A WITH INVERTED BREVE (0x0203)
>>>
>>> So:
>>>
>>> $ context prova.tex
>>>
>>> $ grep -i -E '(warn|miss)' prova.*
>>> [ match nothing ]
>>>
>>> $ texexec --xtx prova.tex
>>>
>>> $ grep -i -E '(warn|miss)' prova.*
>>> prova.log:Missing character: There is no ȃ in font
>>> [lmroman12-regular]:+liga;+kern;mappi
>>> prova.log:Missing character: There is no ȃ in font
>>> [lmroman12-regular]:+liga;+kern;mappi
>>>
>>> It's not a regression, since the behaviour is the same with the last
>>> year ConTeXt.
>>
>>
>> You can add this:
>>
>> \checkcharactersinfont
>>
>> and get missing characters reported to the terminal. Unfortunately I forgot
>> () when adapting this command to the command namespace ...
>>
>> \unexpanded\def\checkcharactersinfont {\ctxcommand{checkcharactersinfont()}}
>>
>> (fixed in next beta)
>>
>> Hans
>
> Also
>
> enabletrackers[fonts.missing]
> \mainlanguage[hr]
> \starttext ȃ\stoptext
Uh I mean
\enabletrackers[fonts.missing]
\mainlanguage[hr]
\starttext ȃ\stoptext
--
luigi
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-05-25 7:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 7:15 Marco Pessotto
2012-05-25 7:40 ` Hans Hagen
2012-05-25 7:45 ` luigi scarso
2012-05-25 7:50 ` luigi scarso [this message]
2012-05-25 7:52 ` Hans Hagen
2012-05-25 7:59 ` Marco Pessotto
2012-05-28 16:26 ` Marco Pessotto
2012-05-28 17:00 ` Hans Hagen
2012-05-28 17:11 ` Marco Pessotto
2012-05-28 18:51 ` Mojca Miklavec
2012-05-28 19:15 ` Hans Hagen
2012-05-28 19:20 ` Hans Hagen
2012-05-25 7:48 ` Marco Pessotto
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='CAG5iGsBcY1UB15264+D0h2YW2Uayw2caoG=YK=-DcqDY=OzjOA@mail.gmail.com' \
--to=luigi.scarso@gmail.com \
--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).