Re: [NTG-context] Arabic typesetting, one more
\usemodule[fnt-20,art-01]
\starttext
\def\sample{اللهِ\quad اللَّـهِ}
\setvariables [otftracker] [font=name:traditionalarabicnormal, size=24pt, features=arabic, direction=-1, title=Feature Check, sample=\sample]
\page
\setvariables [otftracker] [font=arabtype, size=24pt, features=arabic, direction=-1, title=Feature Check, sample=\sample]
\stoptext
Yes, again, kassra is set too low, in both fonts. But with traditionalarabic it is worse than with arabtype. What could be a way to fix this? Huseyin
On 5/8/2013 7:35 AM, "H. Özoguz" wrote:
\usemodule[fnt-20,art-01]
\starttext
\def\sample{اللهِ\quad اللَّـهِ}
\setvariables [otftracker] [font=name:traditionalarabicnormal, size=24pt, features=arabic, direction=-1, title=Feature Check, sample=\sample]
\page
\setvariables [otftracker] [font=arabtype, size=24pt, features=arabic, direction=-1, title=Feature Check, sample=\sample]
\stoptext
Yes, again, kassra is set too low, in both fonts. But with traditionalarabic it is worse than with arabtype. What could be a way to fix this?
fix the font ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Salaam, Huseyin,
I missed this and other threads, it's been busy here...
On Tue, 07 May 2013 23:35:25 -0600, H. Özoguz
But with traditionalarabic it is worse than with arabtype. What could be a way to fix this?
Traditional Arabic is a uniscribe-compliant font, but not a fully opentype font. Uniscribe also supports older, pre-unicode protocols. In other words, TraditionalArabic is platform-dependent. So unless M$ has updated it in a recent OS, it will not work in ConTeXt MkIV. Since XeTeX uses the local libraries, then mkii/xetex on windows might work. Best wishes Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523
On Sat, May 11, 2013 at 03:22:27PM -0600, Idris Samawi Hamid ادريس سماوي حامد wrote:
Salaam, Huseyin,
I missed this and other threads, it's been busy here...
On Tue, 07 May 2013 23:35:25 -0600, H. Özoguz
wrote: But with traditionalarabic it is worse than with arabtype. What could be a way to fix this?
Traditional Arabic is a uniscribe-compliant font, but not a fully opentype font. Uniscribe also supports older, pre-unicode protocols. In other words, TraditionalArabic is platform-dependent. So unless M$ has updated it in a recent OS, it will not work in ConTeXt MkIV.
It did (all its fonts actually), it now uses GPOS for mark placement.
Since XeTeX uses the local libraries, then mkii/xetex on windows might work.
XeTeX does not use any system libraries for its OpenType layout, in the past is was using ICU LayoutEngine and now it is using HarfBuzz, in all platforms (i.e. a third party library, but not a system one). However, HarfBuzz has heuristics to place marks based on glyph bounding boxes in the case of GPOS absence (a bit similar to TeX's \accent but knows which marks goes above or below or off the center). Regards, Khaled
participants (4)
-
"H. Özoguz"
-
Hans Hagen
-
Idris Samawi Hamid ادريس سماوي حامد
-
Khaled Hosny