From: Mohammad Hossein Bateni <bateni@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "Khaled Hosny" <khaledhosny@eglug.org>,
"Idris Samawi Hamid ادريس سماوي حامد" <Idris.Hamid@colostate.edu>
Subject: Re: Problem with Quran KFGQPC Uthman Taha Naskh font
Date: Fri, 29 Apr 2016 06:00:19 -0400 [thread overview]
Message-ID: <CAMHZ1daZDH8Ohjy1hiv-JUgnsUbw13hwuu9Ar1X0=rJN6pLWRA@mail.gmail.com> (raw)
In-Reply-To: <CAMHZ1dZxgVoruApuuwNbp58NK=cJaY=Nz-U2Jsc6vKPY3ktCoQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 4000 bytes --]
Actually the MWE may help:
\usemodule[simplefonts]
\setmainfont[KFGQPC Uthman Taha Naskh][features=arabic,range=arabic]
\setcharacterstripping[1]
\setupdirections[bidi=on,method=one]
\setupalign[r2l]
\starttext
\tfb
الْحَمْدُ
\stoptext
—MHB
On Fri, Apr 29, 2016 at 5:52 AM, Mohammad Hossein Bateni <bateni@gmail.com>
wrote:
> Thanks, Hans! The problem is *almost* fixed in the latest beta, version:
> 2016.04.27 10:18. I didn't think something had changed in the past two
> weeks; that's why I hadn't tried with the latest version.
>
> There is only one word where I notice bad placement of diacritics when
> using CONTEXT. Compare this
> <http://mhbateni.com/context/bug-01/word-context.png> and this
> <http://mhbateni.com/context/bug-01/word-chrome.png>.
>
> BTW context gave the following "warning" about not being able to access
> the data. Is that because it was the first run of a new installation?
>
> system > lua > compiling
>> '/Users/bateni/context.newest/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/data/names.tma'
>> into
>> '/Users/bateni/context.newest/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/data/names.tmc'
>> system > lua > dumping
>> '/Users/bateni/context.newest/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/data/names.tma'
>> into
>> '/Users/bateni/context.newest/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/fonts/data/names.tmc'
>> stripped
>> fonts > names > accessing the data table failed
>
>
> —MHB
>
> On Fri, Apr 29, 2016 at 4:42 AM, Hans Hagen <pragma@wxs.nl> wrote:
>
>> On 4/29/2016 5:01 AM, Mohammad Hossein Bateni wrote:
>>
>>> The attachments in the email below were too big for the list (>100KB).
>>> I uploaded them here <http://mhbateni.com/context/bug-01/>.
>>>
>>> On Thu, Apr 28, 2016 at 10:20 PM, Mohammad Hossein Bateni
>>> <bateni@gmail.com <mailto:bateni@gmail.com>> wrote:
>>>
>>> Hi,
>>>
>>> I am not sure whether I'm missing certain features in the font
>>> definition or whether there is actually some bug in how CONTEXT or
>>> LuaTeX for that matter handles this font. It might as well be that
>>> there is something wrong with the font
>>> <http://fonts.qurancomplex.gov.sa/?page_id=608>, though I doubt
>>> that.
>>>
>>> Attached is my simple test program and the PDF output, which is
>>> annotated to show the problems. You can compare with the reference
>>> PNG file I generated via rendering in Chrome. I hope you can see
>>> the annotations where I have pointed out the incorrect typesetting,
>>> otherwise you can compare the two outputs to notice the difference:
>>> for the most part, some diacritics that are not placed in the right
>>> location (both vertically and horizontally).
>>>
>>> I am using Mac OS X with CONTEXT current version: 2016.04.13 16:46.
>>>
>>
>> can you check the context + beta from the contextgarden?
>>
>>
>> -----------------------------------------------------------------
>> Hans Hagen | PRAGMA ADE
>> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>> tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl
>> -----------------------------------------------------------------
>>
>> ___________________________________________________________________________________
>> 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: 6305 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-04-29 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMHZ1dZG=ftVKpT13YCWQuT5DX5kVNJyieDdeP9WMyGY-HFWPw@mail.gmail.com>
2016-04-29 3:01 ` Mohammad Hossein Bateni
2016-04-29 8:42 ` Hans Hagen
2016-04-29 9:52 ` Mohammad Hossein Bateni
2016-04-29 10:00 ` Mohammad Hossein Bateni [this message]
2016-04-30 17:06 ` 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='CAMHZ1daZDH8Ohjy1hiv-JUgnsUbw13hwuu9Ar1X0=rJN6pLWRA@mail.gmail.com' \
--to=bateni@gmail.com \
--cc=Idris.Hamid@colostate.edu \
--cc=khaledhosny@eglug.org \
--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).