ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Idris Samawi Hamid ادريس سماوي حامد" <Idris.Hamid@colostate.edu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Cambria official typescript (mis)behavior
Date: Wed, 02 Aug 2017 15:27:40 -0600	[thread overview]
Message-ID: <op.y4c4kevtejo439@desktop-mt1m160> (raw)
In-Reply-To: <7fc730f7-e8a5-b9d5-4e08-f6ceead66723@wxs.nl>

On Wed, 02 Aug 2017 15:17:07 -0600, Hans Hagen <pragma@wxs.nl> wrote:

> On 8/2/2017 11:05 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
>> On Wed, 02 Aug 2017 14:34:25 -0600, Hans Hagen <pragma@wxs.nl> wrote:
>>
>>> On 8/2/2017 10:21 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
>>>> Dear gang,
>>>>  There appears to be something awry with type-imp-cambria.mkiv or  
>>>> type-imp-dejavu.mkiv. Consider the following:
>>>>  =======
>>>> \setupbodyfont
>>>>    [cambria,12pt]
>>>>  \starttext
>>>> Test % {\it Test} {\bf Test} {\bi Test}
>>>> \stoptext
>>>> =======
>>>>  This produces a pdf with Cambria Italic instead of Cambria Regular.  
>>>> Uncommenting the other three options produces the expected results.
>>>>  Is this a bug or am I missing something? Awaiting your advice!
>>> it's ok here; it could depend on the cambria on your machine
>>  Cambria Regular : cambria.ttc
>> Cambria Italic  : cambriai.ttf
>>  Inspection shows cambria.ttc is indeed regular.
>>  The log file says
>> :
>> mkiv lua stats  > loaded fonts: 2 files: cambria.ttc, cambriai.ttf
>>  Updating to "current version: 2017.08.02 18:59" and purging the cache  
>> doesn't help
>>  Why is cambriai.ttf being loaded at all? Fresh log (today's beta)  
>> attached
>
> probably because it's the first 'name' that matches
>
> you can try
>
> cambria-x

=> LM

> cambria-y

=> LM

> cambria-a

=> LM

> as variants ; here i have an official cambria

I only have the one that comes with the latest update to Windows 10

(Never tested Cambria with ConTeXt till a few days ago (\definefont  
worked), and never tested the typescript till last night.)

Aditya's suggestion did something that seems to have fixed it, not sure  
what..

Idris
-- 
Idris Samawi Hamid, Professor
Department of Philosophy
Colorado State University
Fort Collins, CO 80512
___________________________________________________________________________________
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:[~2017-08-02 21:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 20:21 Idris Samawi Hamid ادريس سماوي حامد
2017-08-02 20:34 ` Hans Hagen
2017-08-02 21:05   ` Idris Samawi Hamid ادريس سماوي حامد
2017-08-02 21:15     ` Aditya Mahajan
2017-08-02 21:23       ` Idris Samawi Hamid ادريس سماوي حامد
2017-08-02 21:46         ` Aditya Mahajan
2017-08-03  0:41           ` Vladimir Lomov
2017-08-03  7:41           ` Henning Hraban Ramm
2017-08-03 13:22             ` Idris Samawi Hamid ادريس سماوي حامد
2017-08-02 21:17     ` Hans Hagen
2017-08-02 21:27       ` Idris Samawi Hamid ادريس سماوي حامد [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=op.y4c4kevtejo439@desktop-mt1m160 \
    --to=idris.hamid@colostate.edu \
    --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).