From: "Idris Samawi Hamid ادريس سماوي حامد" <ishamid@colostate.edu>
To: "Khaled Hosny" <khaledhosny@eglug.org>
Subject: Re: 10+ reasons why I still use MKII
Date: Fri, 14 May 2010 08:52:25 -0600 [thread overview]
Message-ID: <op.vco99nnepw6hmh@ishamid-pc> (raw)
In-Reply-To: <20100514123702.GA6064@khaled-laptop>
On Fri, 14 May 2010 06:37:02 -0600, Khaled Hosny <khaledhosny@eglug.org>
wrote:
>> >>for arabic you really need to set the interline space (idris might
>> >>have more input on this)
>> >>
>> >>- it has more height than depth
>> >
>> >Not always عٍ or فيٍ is as deep as high is أً.
>>
>> so for say 12pt arabic we should use 8pt ht and 8pt depth?
>
> I'm not sure about this, but I'd rather trust the font designer for
> knowing better about his font, and something like in the attached file
> (except it doesn't work :) see my other mail)
systems : begin file linespace.tex at line 7
! You can't use `\dimexpr' in horizontal mode.
<recently read> \dimexpr
\setstrutgridyes ...e \strutheightfactor \dimexpr
\normallineheight \fi
\str...
\setstrut ->\ifgridsnapping \setstrutgridyes
\else \setstrutgridnop \fi
<inserted text> ...nizefont \fi \spacing \plusone
\presetnormallineheight
\s...
\setfontparameters ...tsfalse \the \everybodyfont
\synchronizefontstrue
\dosetupspecifiedinterlinespaceindeed ...rameters
\updateraggedskips
...
l.24 \stopluacode
?
In any case, overly trusting the font designer is a bad idea in this
arena, particularly with Arabic fonts. For example, vowels are treated as
something of an afterthought even in "good" arabic fonts; yet they affect
linespace calculations. In a document with no vowels one can get away with
things you cannot get away with when they are extensively used; manual
control is essential. And "good" arabic fonts contain numerous errors
anyway.
This is part of the luatex/mkiv philosophy anyway; otherwise we'd just use
uniscribe or pango ;-)
Peace
Idris
--
Professor Idris Samawi Hamid, Editor-in-Chief
International Journal of Shi`i Studies
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
___________________________________________________________________________________
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:[~2010-05-14 14:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 13:48 Mojca Miklavec
2010-05-12 14:44 ` Taco Hoekwater
2010-05-12 15:15 ` Hans Hagen
2010-05-13 13:42 ` Mojca Miklavec
2010-05-13 13:55 ` luigi scarso
2010-05-13 14:16 ` Hans Hagen
2010-05-13 14:32 ` Khaled Hosny
2010-05-13 15:00 ` Hans Hagen
2010-05-13 17:08 ` Khaled Hosny
2010-05-13 21:09 ` Hans Hagen
2010-05-14 13:52 ` Henning Hraban Ramm
2010-05-13 18:46 ` Idris Samawi Hamid ادريس سماوي حامد
2010-05-13 20:06 ` Khaled Hosny
2010-05-13 19:31 ` Idris Samawi Hamid ادريس سماوي حامد
2010-05-13 21:05 ` Hans Hagen
2010-05-13 20:25 ` Hans Hagen
2010-05-13 21:26 ` Khaled Hosny
2010-05-13 21:35 ` Hans Hagen
2010-05-14 12:37 ` Khaled Hosny
2010-05-14 12:54 ` Hans Hagen
2010-05-14 13:10 ` Khaled Hosny
2010-05-14 14:52 ` Idris Samawi Hamid ادريس سماوي حامد [this message]
2010-05-13 18:34 ` Mojca Miklavec
2010-05-13 21:49 ` Hans Hagen
2010-05-14 5:23 ` Taco Hoekwater
2010-05-12 15:20 ` Aditya Mahajan
2010-05-12 15:23 ` Taco Hoekwater
2010-05-12 15:41 ` Aditya Mahajan
2010-05-12 15:45 ` Taco Hoekwater
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.vco99nnepw6hmh@ishamid-pc \
--to=ishamid@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).