From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/95768 Path: news.gmane.org!.POSTED!not-for-mail From: Mohammad Hossein Bateni Newsgroups: gmane.comp.tex.context Subject: Re: Bug in CONTEXT/LuaTeX or just buggy font Date: Wed, 10 Aug 2016 11:19:35 -0400 Message-ID: References: Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6841771173643342135==" X-Trace: blaine.gmane.org 1470842418 7944 195.159.176.226 (10 Aug 2016 15:20:18 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 10 Aug 2016 15:20:18 +0000 (UTC) To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Wed Aug 10 17:20:14 2016 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bXVIj-0001qV-VN for gctc-ntg-context-518@m.gmane.org; Wed, 10 Aug 2016 17:20:14 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 4252814A1E; Wed, 10 Aug 2016 17:19:51 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N0DrO8Ewp91j; Wed, 10 Aug 2016 17:19:50 +0200 (CEST) Original-Received: from zapf.ntg.nl (localhost [IPv6:::1]) by zapf.ntg.nl (Postfix) with ESMTP id 4911E14A23; Wed, 10 Aug 2016 17:19:50 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 09F0014A1F for ; Wed, 10 Aug 2016 17:19:49 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl Original-Received: from zapf.ntg.nl ([127.0.0.1]) by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mlN3x9pvUz0e for ; Wed, 10 Aug 2016 17:19:48 +0200 (CEST) Original-Received: from mail-oi0-f52.google.com (mail-oi0-f52.google.com [209.85.218.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by zapf.ntg.nl (Postfix) with ESMTPS id A727E14A1E for ; Wed, 10 Aug 2016 17:19:37 +0200 (CEST) Original-Received: by mail-oi0-f52.google.com with SMTP id c15so63632609oig.0 for ; Wed, 10 Aug 2016 08:19:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=aUaKpIVJhWww3uGoC0gzHTSkQ+ab5N4R6z5x8+3hGkM=; b=Nnmow0MgoOQB7vOpPQ+nfptv9wArRpfsrv706+D9zxTUF51pA7318OyfSIr67xtvKO fSV5KgOzxyJs8ACxy2fBV9gA/C0DDnwYKR8JltJnxDukn2pte7KRAc5Z/Vq1sYSzUC9n CGX2gyEROhvwXv5fBeyIurgy4U9D0tiiCf9KrgokeIkhxodv29mLkByw6xFuA3P/1McX 0Fk1MTazbJV3WnGxCpSXemkf4cCP1dv8inRiGPCsVrakuib1qcq+tz67RTDim3hVpOia eA/OB1Mqpbbx38IF0ZmixfBNqX011vVBpPHF3wz4MgqxWSccvW8SXK3jwobexz8vmf8P gBng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=aUaKpIVJhWww3uGoC0gzHTSkQ+ab5N4R6z5x8+3hGkM=; b=JtX40PI7hLF3/sluj+Bb9iPVZJkw8i8iSzA2cw9wnPnZ6ICkd7gmG824AsQZBeepy0 ERiYClHe1nD1lQEVUkb9Z1kFusgDgE98B5DjALyu0E/zIQmSsrGiO/HfBxalKqsYrEAp d0d+M/LgKFts9OCNANCpuy4AzqFUVuxlXGtaGk8KDUryBYSCypa6a+ksJlTy6Imws7lO tDeI9qIMjj5yfrskWlK0iEYLlcmuS/PuJQymIWcSRZN1kclYRdHVcyBAZhmLcegSORbA B8f5VWuecvk8+2o88At+MYWmXEc7RBRSAIcPw2DBmlIlsnJkCRa8yv71d2IvNwRD2ZyV 0XQQ== X-Gm-Message-State: AEkoouv81vNJQ8x63KEG43kpgp9wGBKQvuG/y02/ZvvFxbrTquVwvyTQ4UvJoPKVQKxr1uRLI3aqsgRQ3qoOlQ== X-Received: by 10.157.34.48 with SMTP id o45mr2331983ota.37.1470842375747; Wed, 10 Aug 2016 08:19:35 -0700 (PDT) Original-Received: by 10.157.45.77 with HTTP; Wed, 10 Aug 2016 08:19:35 -0700 (PDT) In-Reply-To: X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.16 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntg-context-bounces@ntg.nl Original-Sender: "ntg-context" Xref: news.gmane.org gmane.comp.tex.context:95768 Archived-At: --===============6841771173643342135== Content-Type: multipart/alternative; boundary=001a113e572853c5be0539b92da8 --001a113e572853c5be0539b92da8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, Aug 10, 2016 at 11:03 AM, Hans Hagen wrote: > On 8/9/2016 10:41 PM, Mohammad Hossein Bateni wrote: > >> Hello, >> >> I have a bunch of simple fonts for Arabic/Persian. These fonts lack >> Latin characters, etc., so I use fallbacks to work with them. >> >> I just noticed that \high does not work with them, and have not been >> able to pinpoint the issue. See the MWE below. >> >> >> \starttypescript [serif][samim][name] >> \definefontsynonym[Serif][Samim] >> \stoptypescript >> >> \definetypeface [myfont][rm] [serif][samim][default] >> \setupbodyfont [myfont] >> >> \starttext >> %\definedfont[Samim*arabic] >> =DB=B1=DB=B2=DB=B3\high{=DB=B4}=DB=B5=DB=B6. >> \stoptext >> >> >> I am using Persian digits because the font lacks Latin digits as I >> mentioned. If I use the \definedfont approach, I don't see the >> character =DB=B4 (argument of \high) at all. With the typescript approa= ch, >> the same character /is/ typeset but is /not/ raised; it appears on the >> baseline but with smaller size. >> >> Any ideas why this is happening? Could it be that some parameters, for >> instance, \exheight are not properly set/read for this font? Actually, >> I looked at the non-math fontdimens in syst-fnt.mkiv, and everything >> except \slantperpoint (expected) and \exheight (awkward) is non-zero. I >> don't know where \exheight comes from=E2=80=94perhaps from the height of= glyph >> for 'x', which the font lacks=E2=80=94however, \emheight is 12pt, althou= gh the >> font also lacks a glyph for 'm'. >> >> I am also attaching the font in case that helps. >> > > Normally one sets up a proper bodyfont (and environment if needed) while > you use just a simple font switch and that one is unrelated to any other > font setting. > Thanks! But what does a `proper' bodyfont contain beside defining rm, ss, tt and mm for 'myfont' above (with regular, bold, italic, and bolditalic)? The above was a MWE but in my real example I am setting up these things that I mentioned in a larger typescript. How can I modify the font or the typescript definitions (or the environment) to get \exheight right? > > I'll add two new commands: \sx and \sxx so that you can say: > > \setuplow [style=3D\sx] > \setuphigh[style=3D\sx] > If I do this, this will not get attached to the font; right? For instance, if I define two bodyfonts 'myfonta' and 'myfontb', and switch between them in the document, then I have to stick to these two setups if one font, say 'myfonta', is problematic. Is that correct? for such cases. However, as these are derived relative scales they are > normally not compatible with \tx and txx sizes. > > Hans > > ----------------------------------------------------------------- > Hans Hagen | PRAGMA ADE > Ridderstraat 27 | 8061 GH Hasselt | The Netherlands > tel: 038 477 53 69 | www.pragma-ade.nl | 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/list > info/ntg-context > webpage : http://www.pragma-ade.nl / http://tex.aanhet.net > archive : http://foundry.supelec.fr/projects/contextrev/ > wiki : http://contextgarden.net > ____________________________________________________________ > _______________________ --001a113e572853c5be0539b92da8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Wed, Aug 10, 2016 at 11:03 AM, Hans Hagen <pragma@wxs.nl>= wrote:
On 8/9/2016 10:4= 1 PM, Mohammad Hossein Bateni wrote:
Hello,

I have a bunch of simple fonts for Arabic/Persian.=C2=A0 These fonts lack Latin characters, etc., so I use fallbacks to work with them.

I just noticed that \high does not work with them, and have not been
able to pinpoint the issue.=C2=A0 See the MWE below.


\starttypescript [serif][samim][name]
=C2=A0 \definefontsynonym[Serif][Samim]
\stoptypescript

\definetypeface [myfont][rm] [serif][samim][default]
\setupbodyfont [myfont]

\starttext
%\definedfont[Samim*arabic]
=DB=B1=DB=B2=DB=B3\high{=DB=B4}=DB=B5=DB=B6.
\stoptext


I am using Persian digits because the font lacks Latin digits as I
mentioned.=C2=A0 If I use the \definedfont approach, I don't see the character =DB=B4 (argument of \high) at all.=C2=A0 With the typescript appr= oach,
 the same character /is/ typeset but is /not/ raised; it appears on the
baseline but with smaller size.

Any ideas why this is happening?=C2=A0 Could it be that some parameters, fo= r
instance, \exheight are not properly set/read for this font?=C2=A0 Actually= ,
I looked at the non-math fontdimens in syst-fnt.mkiv, and everything
except \slantperpoint (expected) and \exheight (awkward) is non-zero.=C2=A0= I
don't know where \exheight comes from=E2=80=94perhaps from the height o= f glyph
for 'x', which the font lacks=E2=80=94however, \emheight is 12pt, a= lthough the
font also lacks a glyph for 'm'.

I am also attaching the font in case that helps.

Normally one sets up a proper bodyfont (and environment if needed) while yo= u use just a simple font switch and that one is unrelated to any other font= setting.

Thanks!=C2=A0 But what does a= `proper' bodyfont contain beside defining rm, ss, tt and mm for 'm= yfont' above (with regular, bold, italic, and bolditalic)?=C2=A0 The ab= ove was a MWE but in my real example I am setting up these things that I me= ntioned in a larger typescript.=C2=A0 How can I modify the font or the type= script definitions (or the environment) to get \exheight right?
= =C2=A0

I'll add two new commands: \sx and \sxx so that you can say:

=C2=A0 =C2=A0 \setuplow [style=3D\sx]
=C2=A0 =C2=A0 \setuphigh[style=3D\sx]

= =C2=A0If I do this, this will not get attached to the font; right?=C2=A0 Fo= r instance, if I define two bodyfonts 'myfonta' and 'myfontb= 9;, and switch between them in the document, then I have to stick to these = two setups if one font, say 'myfonta', is problematic.=C2=A0 Is tha= t correct?

for such cases. However, as these are derived relative scales they are norm= ally not compatible with \tx and txx sizes.

Hans

-----------------------------------------------------------------=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 H= ans Hagen | PRAGMA ADE
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Ridderstraat 27 | 8061 GH = Hasselt | The Netherlands
=C2=A0 =C2=A0 =C2=A0 =C2=A0tel: 038 477 53 69 | www.pragma-ade.nl | www.p= ragma-pod.nl
-----------------------------------------------------------------=
_________________________________________________________________= __________________
If your question is of interest to others as well, please add an entry to t= he Wiki!

maillist : ntg-cont= ext@ntg.nl / http://www.ntg.nl/mailman/listin= fo/ntg-context
webpage=C2=A0 : http://www.pragma-ade.nl / http://tex.aanhet.net
archive=C2=A0 : http://foundry.supelec.fr/project= s/contextrev/
wiki=C2=A0 =C2=A0 =C2=A0: http://contextgarden.net
_________________________________________________________________= __________________

--001a113e572853c5be0539b92da8-- --===============6841771173643342135== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv IGh0dHA6Ly90ZXguYWFuaGV0Lm5ldAphcmNoaXZlICA6IGh0dHA6Ly9mb3VuZHJ5LnN1cGVsZWMu ZnIvcHJvamVjdHMvY29udGV4dHJldi8Kd2lraSAgICAgOiBodHRwOi8vY29udGV4dGdhcmRlbi5u ZXQKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX18= --===============6841771173643342135==--