From: Mohammad Hossein Bateni <bateni@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug in CONTEXT/LuaTeX or just buggy font
Date: Wed, 10 Aug 2016 11:19:35 -0400 [thread overview]
Message-ID: <CAMHZ1dZwruixd+FT6nBdOZ1Caa8V1-3dwAb=X6DGmA1ff=gkXQ@mail.gmail.com> (raw)
In-Reply-To: <bb23a914-aa54-364e-fa14-6862ec1d81b1@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 3561 bytes --]
On Wed, Aug 10, 2016 at 11:03 AM, Hans Hagen <pragma@wxs.nl> 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]
>> ۱۲۳\high{۴}۵۶.
>> \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 ۴ (argument of \high) at all. With the typescript approach,
>> 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—perhaps from the height of glyph
>> for 'x', which the font lacks—however, \emheight is 12pt, although 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=\sx]
> \setuphigh[style=\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
> ____________________________________________________________
> _______________________
[-- Attachment #1.2: Type: text/html, Size: 5165 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-10 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 20:41 Mohammad Hossein Bateni
2016-08-10 15:03 ` Hans Hagen
2016-08-10 15:19 ` Mohammad Hossein Bateni [this message]
2016-08-10 15:31 ` 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='CAMHZ1dZwruixd+FT6nBdOZ1Caa8V1-3dwAb=X6DGmA1ff=gkXQ@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).