From: Mohammad Hossein Bateni <bateni@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem loading font KFGQPC Uthman Taha Naskh font
Date: Sun, 21 Aug 2016 11:49:08 -0400 [thread overview]
Message-ID: <CAMHZ1dbuyEHpXa4DEccVoROO5pYj-gyHKecAaUFrBLCFb6zuqw@mail.gmail.com> (raw)
In-Reply-To: <57B9B3AA.40807@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1758 bytes --]
remaking the format produced no change but removing those files from the
cache did solve the problem.
thanks a lot!
On Sun, Aug 21, 2016 at 9:59 AM, Wolfgang Schuster <
schuster.wolfgang@gmail.com> wrote:
> Mohammad Hossein Bateni <bateni@gmail.com>
> 21. August 2016 um 12:53
> Hello,
>
> The code snippet at the end used to work a few months ago when I reported
> a rendering bug. But now the font does not load and I see the following
> error. (It's not an issue with simplefonts because \definedfont[KFGQPCUthmanTahaNaskh*arabic]
> does not work either. the font is published here
> <http://fonts.qurancomplex.gov.sa/wp-content/uploads/2012/06/UthmanTN1-Ver10.zip>
> .
>
> Remake the format (context --make en) or delete the font entries
> (uthmantn1-ver10.tma|tmc) in the cache ($TEXMF/texmf-cache/luatex-
> cache/context/<HASH>/fonts/otl/). Please try both suggestions and report
> which of them helped.
>
> BTW: The simplefonts module has been replaced with the \definefontfamily
> command (different syntax but included in the core).
>
> %%%% begin example
> \definefontfamily[testfont][rm][KFGQPC Uthman Taha Naskh][features=arabic]
>
> \setupbodyfont[testfont]
>
> \starttext
> ...
> \stoptext
> %%%% end example
>
> Wolfgang
>
> ____________________________________________________________
> _______________________
> 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
> ____________________________________________________________
> _______________________
>
[-- Attachment #1.2: Type: text/html, Size: 3535 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-08-21 15:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-21 10:53 Mohammad Hossein Bateni
2016-08-21 13:41 ` Hans Hagen
2016-08-21 13:59 ` Wolfgang Schuster
2016-08-21 15:49 ` Mohammad Hossein Bateni [this message]
2016-08-21 16:06 ` Mohammad Hossein Bateni
2016-08-21 16:17 ` Wolfgang Schuster
2016-08-21 16:19 ` Mohammad Hossein Bateni
2016-08-21 18:01 ` Wolfgang Schuster
2016-08-21 20:59 ` Hans Hagen
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=CAMHZ1dbuyEHpXa4DEccVoROO5pYj-gyHKecAaUFrBLCFb6zuqw@mail.gmail.com \
--to=bateni@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).