ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Khaled Hosny <khaledhosny@eglug.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Arabic protrosion
Date: Mon, 6 Apr 2009 22:20:37 +0200	[thread overview]
Message-ID: <20090406202037.GB6176@khaled-laptop> (raw)
In-Reply-To: <op.uryvrilxfkrasx@your-b27fb1c401>


[-- Attachment #1.1: Type: text/plain, Size: 2446 bytes --]

On Mon, Apr 06, 2009 at 07:30:33AM -0600, Idris Samawi Hamid ادريس سماوي حامد wrote:
> On Mon, 06 Apr 2009 00:40:12 -0600, Khaled Hosny <khaledhosny@eglug.org>  
> wrote:
>
>> The attached patch adds Arabic coma, semicolon, full stop (used in Urdu)
>> and question mark to font-ext.lua for protrusion.
>> Now, combined with glyph expansion, I don't get any overfull boxes.
>
> Arabic-script microtypography is one of the cornerstones of the Oriental  
> TeX project. We've been studying this matter for some time now:
>
> Because of
>
> a) the normal wide spacing around Arabic punctuation, and
>
> b) the large size of Arabic punctuation relative to Latin,
>
> I'm not sure that protrusion of Arabic-script punctuation is a good idea. 
> It needs a lot of thought, and a lot of testing, before adding it to the  
> system.

Indeed, more testing is needed, but since neither protrusion nor
expansion is on by default, I think it is safe to have them now so we
can do more testing and tune it later, when someone enables hz features,
he should no enough to judge himself about the quality of the result and
he can always turn it back off and will lose nothing.

> As for glyph expansion, I don't see how that works at all with 
> the current model, except perhaps with very horizontal fonts. But in that 
> case all that's needed is smart tatweel, not glyph expansion. For hq 
> fonts the current glyph expansion model will mess up the contextual 
> connections.

I think the minimal font expansion, that we have, is very unlikely to be
noticed by the reader, but I completely agree that great care should be
taken, I've been reading some Arabic book few months ago and I'm pretty
sure they used the font expansion feature of InDesign because it was
very visible and annoying.

>
> Although one can certainly do things with the current model of protrusion 
> and hz, we need more, much more. Khaled, send me some tests off-list and  
> I'll examine them in light of the overall analysis as we prepare for  
> adding Arabic microtypography support, hopefully pretty soon.

I was preparing some test files, when I accidentally removed all files
that I was working on recently, since I don't have a backup, it'll take
some time.

> سلام
وعليكم السلام

Regards,
 Khaled


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

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      parent reply	other threads:[~2009-04-06 20:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06  6:40 Khaled Hosny
     [not found] ` <op.uryvrilxfkrasx@your-b27fb1c401>
2009-04-06 13:46   ` Hans Hagen
2009-04-06 20:20   ` Khaled Hosny [this message]

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=20090406202037.GB6176@khaled-laptop \
    --to=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).