From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Arabic with LuaTeX vs. XeTeX
Date: Mon, 9 Jun 2008 11:13:06 +0200 [thread overview]
Message-ID: <E3E43AFF-D4F6-4649-BAAC-62FE615E891D@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
Dear all,
I just read the thread started by Burak Emir about "Typesetting Arabic
today", and tried to typeset the sample sent by Idris Samawi Hamid.
One of the Arabic or Persian fonts that I have and LuaTeX can find is
Nadeem (working on Mac OS X 10.5.3), but what I get after typesetting
is the following attached PDF: all the characters are typeset with
their isolated form. However typestting the same text with XeConTeXt
or XeTeX gives a nice result.
So my question is, what should I add or subtract from the font
features parameters to get a correct result?
[-- Attachment #2: test-lua.pdf --]
[-- Type: application/pdf, Size: 20572 bytes --]
[-- Attachment #3: Type: text/plain, Size: 1468 bytes --]
The source file is as follows:
% engine=luatex
\starttext
\definefontfeature
[test]
[analyze=yes,
mode=node,
language=dflt,
script=arab,
aalt=yes,
init=yes,
medi=yes,
fina=yes,
isol=yes,
liga=yes,
mset=yes]
\font\TradArabic = Nadeem*test at 18pt
\startbuffer[paragraph]
الحمدلله حمد معترف بحمده، مغترف من
بحار مجده، بلسان
الثناۤء شاكرا، ولحسن الاۤئه ناشرا؛
الذي خلق الموت والحيوة، والخير
والشر، والنفع والضر، والسكون والحركة،
والأرواح
والأجسام، والذكر والنسيان.
\blank
اَلْحَمْدُ لِلّٰهِ حَمْدَ مُعْتَرِفٍ
بِحَمْدِهٖ، مُغْتَرِفٌ مِنْ بِحَارِ
مَجْدِهٖ، بِلِسَانِ
الثَّنَاۤءِ شَاكِرًا، وَلِحُسْنِ
اٰلاۤئِهٖ نَاشِرًا؛ اَلَّذِيْ خَلَقَ
الْمَوْتَ وَالْحَيٰوةَ، وَالْخَيْرَ
وَالشَّرَّ، وَالنَّفْعَ وَالضَّرَّ،
وَالسُّكُوْنَ وَالْحَرَكَةَ،
وَالْأَرْوَاحَ
وَالْأَجْسَامَ، وَالذِّكْرَ
وَالنِّسْيَانَ.
\stopbuffer
\start
\TradArabic
\pardir TRT \textdir TRT
\getbuffer[paragraph]
\stop
\stoptext
[-- Attachment #4: 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 reply other threads:[~2008-06-09 9:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 9:13 Otared Kavian [this message]
2008-06-09 9:23 ` Wolfgang Schuster
2008-06-09 11:38 ` Otared Kavian
2008-06-09 15:09 ` Burak Emir
2008-06-09 15:21 ` Otared Kavian
2008-06-09 16:07 ` Hans Hagen
2008-06-09 16:43 ` Otared Kavian
2008-06-09 16:53 ` Mojca Miklavec
2008-06-09 20:45 ` Otared Kavian
2008-06-09 21:09 ` Hans Hagen
2008-06-09 21:40 ` Oliver Buerschaper
2008-06-09 17:00 ` Hans Hagen
2008-06-09 17:03 ` Burak Emir
2008-06-09 11:52 ` Khaled Hosny
2008-06-09 12:00 ` Wolfgang Schuster
2008-06-09 14:52 ` Idris Samawi Hamid
2008-06-09 23:25 ` Idris Samawi Hamid
2008-06-10 8:09 ` 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=E3E43AFF-D4F6-4649-BAAC-62FE615E891D@gmail.com \
--to=otared@gmail.com \
--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).