ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Khaled Hosny <khaledhosny@eglug.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: footnotes when using RtL (Arabic)
Date: Tue, 5 Oct 2010 16:53:08 +0200	[thread overview]
Message-ID: <20101005145307.GA5991@khaled-laptop> (raw)
In-Reply-To: <4F8A3562-26EA-4312-BCC2-AAA11D7BE5FB@fastmail.fm>

On Tue, Oct 05, 2010 at 03:18:31PM +0100, Talal Al-Azem wrote:
> Thanks Wolfgang. That makes that matter clearer. But how do I get those Arabic footnotes to be right aligned as well?
> 
> May I also ask: what is the purpose, at least in my example that I'm learning from, of:
> \definefontfeature[arabic][default][mode=node,script=arabic] ?

The first argument is the name of the new feature set, the second is an
optional feature set to be inherited. Actually, ConTeXt already has a
predefined "arabic" feature and you can just use it.

Regards,
 Khaled

-- 
 Khaled Hosny
 Arabic localiser and member of Arabeyes.org team
 Free font developer
___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2010-10-05 14:53 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 12:48 Talal Al-Azem
2010-10-05 13:28 ` Wolfgang Schuster
2010-10-05 14:18   ` Talal Al-Azem
2010-10-05 14:53     ` Khaled Hosny [this message]
2010-10-05 15:07     ` Wolfgang Schuster
2010-10-05 15:18       ` Talal Al-Azem
2010-10-05 15:25       ` Hans Hagen
2010-10-05 15:55         ` Talal Al-Azem
2010-10-05 16:20           ` Hans Hagen
2010-10-05 21:19   ` Hans Hagen
2010-10-05 21:50     ` Talal Al-Azem
2015-07-21 19:56 talazem
2015-07-30 13:00 ` talazem
2015-07-30 14:26   ` Pablo Rodriguez
2015-07-30 14:43     ` talazem
2015-07-30 15:08       ` Pablo Rodriguez
2015-07-30 17:54     ` Wolfgang Schuster
2015-07-30 18:15       ` Idris Samawi Hamid ادريس سماوي حامد
2015-07-30 18:17       ` talazem
2015-07-30 18:18       ` Pablo Rodriguez
2015-07-30 18:37       ` talazem
2015-07-30 19:04         ` Wolfgang Schuster
2015-07-30 23:51           ` talazem
2015-07-31  8:39             ` Hans Hagen
2015-07-31 11:07               ` talazem
2015-07-31 12:05                 ` Idris Samawi Hamid ادريس سماوي حامد
2015-07-31 14:47                 ` Hans Hagen
2015-08-01 22:36                 ` talazem
2015-08-02  7:52                   ` Pablo Rodriguez
2015-08-02  9:20                     ` talazem
2015-08-02 10:02                       ` talazem
2015-08-02 10:47                         ` Pablo Rodriguez
2015-08-02 11:09                           ` talazem
2015-08-02 11:11                           ` Pablo Rodriguez
2015-08-03 19:14                             ` talazem

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=20101005145307.GA5991@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).