FontLab Forum
2012-02-09, 03:47:51 *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Welcome to the FontLab forum, read how to use it! Update: Archives from old MSN forums are now available on our forum.
 
   Home   Help Search Calendar Downloads Tags Login Register  
Del.icio.us Digg FURL FaceBook Stumble Upon Reddit SlashDot

Pages: [1]
  Print  
Author Topic: Why even create OT for Arabic?  (Read 2979 times)
Ahmad Osman
Hero Member
*****

Karma: +0/-0
Lebanon Lebanon

Posts: 22


« on: 2009-12-30, 09:55:29 »

This is not a rhetoric question by the way, I really have ceased to know why.

When I learnt OT about a year ago, I understood that, at least so far as Arabic is concerned, OT was useful for three purposes:
1. To substitute isolated forms for glyphs for other forms (initial, medial, final, or isolated)
2. To create ligatures
3. To distinguish high vocalisation marks from low vocalisation marks, something which necessitates that low-glyph and high-glyph classes be created.

Working on Latin typefaces, I found out (please correct me if I were mistaken) that there are only so many preset ligatures that one can find in the unicode ranges, and that OT is also necessary for alternative forms. Great.

Working on Arabic typefaces, however, I found out that the Arabic glyph compartments were programmed as to perform the basic substitution operation (from isolated to other forms) without OT.

I also found out that basically all the ligatures that I could dream of were in the 'Arabic Presentation Forms-A' unicode range. Those preset ligatures seem to work fine without need for OT. Same for the vocalisation marks, which also got substituted by their low counterparts by sheer glyph programming (I suppose).

Given all of that, why would I as an Arabic typeface designer need OT?
Logged
Glagolitic
Sr. Member
****

Karma: +0/-0
United States United States

Posts: 15


« Reply #1 on: 2010-01-12, 15:33:54 »

You are correct. Rendering Arabic is usually the job of the OS rather than OT.

The precomposed arabic forms in Unicode are for compatibility — and are not actually used when entering text. Arabic text remains in decomposed form, while being correctly displayed by the OS with all forms.
« Last Edit: 2010-01-13, 06:19:22 by Alex Petrov (FontLab) » Logged
Luc[as]
Beta: FontLab Studio Win
Hero Member
***

Karma: +3/-0
Netherlands Netherlands

Posts: 132



WWW
« Reply #2 on: 2010-01-13, 15:31:58 »

What application and system were you using to test? In order to make Arabic work in a standard MS Word, you need OT programming. Without OT it might look acceptable in InDesign ME, but properly designed and positioned vocalisation can only work with a lot of programming in Volt.
Logged
Ahmad Osman
Hero Member
*****

Karma: +0/-0
Lebanon Lebanon

Posts: 22


« Reply #3 on: 2010-01-16, 05:34:04 »

To answer Luc(as), indeed I am designing typefaces to be used on Adobe InDesign ME, so apparently that's why I did not see the relevance.
Question to Glagolitic: What is OS? Something system-related?
Lots of thanks to both.
Logged
Glagolitic
Sr. Member
****

Karma: +0/-0
United States United States

Posts: 15


« Reply #4 on: 2010-01-16, 12:45:48 »

To answer Luc(as), indeed I am designing typefaces to be used on Adobe InDesign ME, so apparently that's why I did not see the relevance.
Question to Glagolitic: What is OS? Something system-related?
Lots of thanks to both.

OS = Operating System.

Logged
Tags: opentype  Arabic  substitution  ligatures 
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!