[NTG-context] 10+ reasons why I still use MKII

Khaled Hosny khaledhosny at eglug.org
Fri May 14 15:10:30 CEST 2010

On Fri, May 14, 2010 at 02:54:49PM +0200, Hans Hagen wrote:
> On 14-5-2010 2:37, Khaled Hosny wrote:
> >On Thu, May 13, 2010 at 11:35:58PM +0200, Hans Hagen wrote:
> >>On 13-5-2010 11:26, Khaled Hosny wrote:
> >>>On Thu, May 13, 2010 at 10:25:06PM +0200, Hans Hagen wrote:
> >>>>On 13-5-2010 10:06, Khaled Hosny wrote:
> >>>>
> >>>>>Nothing special, I always expect interline space to be fixed, I don't
> >>>>>know if TeX always make interline spacing variable, but this wasn't an
> >>>>>issue with English text. However, with Arabic, Tashkil marks seems to
> >>>>>always cause a noticeable extra whitespace above the line.
> >>>>>See the uneven distribution of vertical whitespace in this example (it
> >>>>>can be even worse than this in reality):
> >>>>
> >>>>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)
> it's a gray area ... if we obey the ht/dp spec of a font (ascender
> and descender) we end up with an unpredictable mess (actually
> comparable to setting the baselineskip to 0pt and trusting the ht/dp
> of glyphs to force the right line spacing)
> in dtp there's aways this rather strict grid

At least it should be there as an option, and contrary to ht/dp of the
glyphs, typo ascender/descender are font wide values thus will be the
same for all lines (math is an exception).


 Khaled Hosny
 Arabic localiser and member of Arabeyes.org team
 Free font developer

More information about the ntg-context mailing list