From: Khaled Hosny <khaledhosny@eglug.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug in mark to ligature handling
Date: Wed, 4 Mar 2009 14:46:03 +0200 [thread overview]
Message-ID: <20090304124603.GA12832@khaled-laptop> (raw)
In-Reply-To: <49AE6A94.8090002@wxs.nl>
[-- Attachment #1.1.1: Type: text/plain, Size: 1011 bytes --]
On Wed, Mar 04, 2009 at 12:48:36PM +0100, Hans Hagen wrote:
> Khaled Hosny wrote:
>> Marks don't get positioned correctly unless all marks are supplied, if
>> one mark is omitted, the next mark will be positioned at the first
>> anchor point, not in the second one etc, in some cases it'll even not
>> positioned on the anchor point at all.
>>
>> In the attached sample, the first word in the line is correct,
>> subsequent ones aren't.
>> (The font used:
>> http://raqm.googlecode.com/svn/trunk/fonts/simplenaskhi/SimpleNaskhi.ttf)
>
> can you check the new beta?
It is fixed in the beta, thanks.
Now I found another bug, when having two marks on the same base glyph,
the first one is positioned correctly but not the second one.
See the attached sample (I swapped the marks on the next word).
>
> btw, use \starttext ... \stoptext and not \bye
Will do, thanks.
Regards,
Khaled
--
Khaled Hosny
Arabic localiser and member of Arabeyes.org team
Free font developer
[-- Attachment #1.1.2: ligatures.tex --]
[-- Type: text/x-tex, Size: 320 bytes --]
\pagedir TRT\bodydir TRT\pardir TRT\textdir TRT
\definefontfeature[otfnaskhi]
[mode=node,language=dflt,script=arab,
init=yes,medi=yes,fina=yes,calt=yes,
rlig=yes,liga=yes,dlig=yes,curs=yes,
mark=yes,mkmk=yes]
\starttext
\font\test=SimpleNaskhi*otfnaskhi at 48pt\test
تِّ : تِّ
\stoptext
[-- Attachment #1.1.3: ligatures.pdf --]
[-- Type: application/pdf, Size: 11053 bytes --]
[-- 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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-03-04 12:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 22:13 Khaled Hosny
2009-03-04 8:37 ` Hans Hagen
2009-03-04 10:56 ` Khaled Hosny
2009-03-04 11:48 ` Hans Hagen
2009-03-04 12:46 ` Khaled Hosny [this message]
2009-03-04 14:14 ` Hans Hagen
2009-03-04 16:25 ` Khaled Hosny
2009-06-12 16:30 ` Khaled Hosny
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=20090304124603.GA12832@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).