ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Idris Samawi Hamid" <ishamid@colostate.edu>
To: "Burak Emir" <burak.emir@gmail.com>,
	"mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: typesetting Arabic today
Date: Sat, 07 Jun 2008 14:18:07 -0600	[thread overview]
Message-ID: <op.uceaohn6nx1yh1@your-b27fb1c401> (raw)
In-Reply-To: <ac0ce270806071309k54b38a0ao332daba1ac6bd0fb@mail.gmail.com>

Hi, Burak,

On Sat, 07 Jun 2008 14:09:14 -0600, Burak Emir <burak.emir@gmail.com>  
wrote:

> Hi again,
>
> On Mon, Jun 2, 2008 at 8:43 PM, Idris Samawi Hamid  
> <ishamid@colostate.edu>
> wrote:
>
>
>> http://wiki.contextgarden.net/Aleph_Guide
>>
>> was once the main guide. Aleph was a merge of etex and Omega, succeeded  
>> by
>> luatex. You can still use the old Omega way of doing things in luatex  
>> -- as
>> explained in that guide, but it's better to use the new mechanism and
>> opentype fonts.
>>
>
> My luatex is not working for the moment, I am using the context minimals
> distribution on MacOS X.
>
> Would the old Omega way documented on that page also work with the xetex
> engine?

No, XeTeX does not support Omega/Aleph commands. If you find an aleph  
binary for Mac I guess you could try that, but don't give up on luaTeX  
just yet, I'm sure someone on the list will figure out what's wrong....

Best wishes
Idris

-- 
Professor Idris Samawi Hamid, Editor-in-Chief
International Journal of Shi`i Studies
Department of Philosophy
Colorado State University
Fort Collins, CO 80523

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2008-06-07 20:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-01 16:31 Burak Emir
2008-06-02  6:29 ` Wolfgang Schuster
2008-06-02 18:43   ` Idris Samawi Hamid
2008-06-02 19:18     ` Idris Samawi Hamid
2008-06-04  0:24       ` Burak Emir
2008-06-06  6:44         ` Wolfgang Schuster
2008-06-06  7:43           ` Hans Hagen
2008-06-07 10:37             ` Burak Emir
2008-06-07 20:09     ` Burak Emir
2008-06-07 20:18       ` Idris Samawi Hamid [this message]
2008-06-07 20:48         ` Burak Emir
2008-06-07 20:58           ` Idris Samawi Hamid
2008-06-07 21:04           ` Mojca Miklavec
2008-06-07 21:11           ` Hans Hagen
2008-06-07 21:45             ` Burak Emir
     [not found]               ` <op.ucee5qyrnx1yh1@your-b27fb1c401>
2008-06-07 22:03                 ` Burak Emir
2008-06-07 22:28               ` Burak Emir
2008-06-08  6:22               ` Burak Emir

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=op.uceaohn6nx1yh1@your-b27fb1c401 \
    --to=ishamid@colostate.edu \
    --cc=burak.emir@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).