From: Khaled Hosny <khaledhosny@eglug.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Rendering of ZWNJ and ZWJ
Date: Thu, 12 Jun 2008 16:55:45 +0300 [thread overview]
Message-ID: <20080612135545.GB8400@khaled-laptop> (raw)
In-Reply-To: <op.ucibrziznx1yh1@your-b27fb1c401>
[-- Attachment #1.1: Type: text/plain, Size: 1744 bytes --]
On Mon, Jun 09, 2008 at 06:32:13PM -0600, Idris Samawi Hamid wrote:
> Hi Hans,
>
> On Mon, 09 Jun 2008 09:45:10 -0600, Hans Hagen <pragma@wxs.nl> wrote:
>
> > Khaled Hosny wrote:
> >> Using Luatex engine, ZWNJ and ZWJ chars are rendered incorrectly. If the
> >> font has a glyph for it, it does the expected behaviour (force
> >> non-joining or joining respectively) but the glyph get rendered while it
> >> shouldn't. But if the font has no glyphs for it, it has no effect at
> >> all. See the attached example.
> >
> > i uploaded a beta
> >
> > after analyzing i now remove the joiners
>
> Not sure if this is the best approach:
>
> Despite what MS Typography says, I think it's important to maintain the
> joiner info after analysis. If I select text from a pdf, the joiner info
> should be there. This is important for, eg, switching from Arabic-language
> to Farsi-language typography. So If I select some pdf text formatted
> according to Farsi rules, I should be able to save that text with the
> rules included.
>
> Can this be made an option, so fonts that contain zwj zwnj are not
> affected?
Well, I've very little ConTeXt knowledge to actually understand this. My
main point was that non-printable formatting characters like ZWNJ, ZWJ
should be font independent i.e. when I insert a ZWNJ it inhibits the
joining of Arabic letters without being printed, the font having or not
having a glyph for it shouldn't affect this. In the other hand, it
should be their so that when I copy the text I get it (since it is part
of the input and has semantical value).
Is this what we have here?
Regards,
Khaled
--
Khaled Hosny
Arabic localizer and member of Arabeyes.org team
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 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:[~2008-06-12 13:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 1:42 Khaled Hosny
2008-06-09 13:04 ` Hans Hagen
2008-06-09 15:45 ` Hans Hagen
2008-06-09 17:05 ` Khaled Hosny
2008-06-10 0:32 ` Idris Samawi Hamid
2008-06-10 16:45 ` Hans Hagen
2008-06-10 18:12 ` Idris Samawi Hamid
2008-06-10 18:52 ` Hans Hagen
2008-06-12 13:55 ` Khaled Hosny [this message]
2008-06-12 14:06 ` 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=20080612135545.GB8400@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).