ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: r2l alignment and linenumbering conflict?
Date: Tue, 4 Aug 2015 01:30:38 +0200	[thread overview]
Message-ID: <55BFF99E.3030902@wxs.nl> (raw)
In-Reply-To: <58706331-074F-44A0-91CD-269C37EC8FEF@gmail.com>

On 8/3/2015 9:25 PM, Otared Kavian wrote:
> Hi Hans, Idris, Talal,
>
> Some years ago we had a discussion on the issue, but I don’t remember where we ended up…
> In my opinion, I think that the numberings should be maned as follows:
>
> arabicnumerals: should be  ١,٢,٣,٤,٥,٦,٧,٨,٩,٠
>
> persiannumerals: should be ۱ ۲ ۳ ۴ ۵ ۶ ۷ ۸ ۹ ۰
>
> abjadnumerals: should be الف، ب، ج، د، ه، و، ز،…..
>
> As of today it seems that « persiannumerals » results in what should be named abjadnuemrals, and this is not correct.

so you and idris and tatal has to come to some agreement on that

we have these alphabetic ones

arabicnumerals
persiannumerals
arabicexnumerals

and some special ones

abjadnumerals
abjadnodotnumerals

(these use small, medium, large chars and do special things with 10 100 
1000)

and now

arabicdecimals
persiandecimals

see core-con.lua

Hans

-----------------------------------------------------------------
                                           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
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2015-08-03 23:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30 15:30 talazem
2015-08-01 15:37 ` talazem
2015-08-01 18:04   ` Pablo Rodriguez
2015-08-01 18:35   ` Idris Samawi Hamid ادريس سماوي حامد
2015-08-01 18:47   ` Wolfgang Schuster
2015-08-02  9:24     ` talazem
2015-08-02 11:51       ` Idris Samawi Hamid ادريس سماوي حامد
2015-08-02 13:31         ` talazem
2015-08-02 17:15           ` Idris Samawi Hamid ادريس سماوي حامد
2015-08-02 20:46             ` talazem
2015-08-03 13:54             ` talazem
2015-08-03 14:56               ` Hans Hagen
2015-08-03 15:13                 ` Hans Hagen
2015-08-03 15:42                   ` Idris Samawi Hamid ادريس سماوي حامد
2015-08-03 15:56                     ` Hans Hagen
2015-08-03 16:17                       ` Idris Samawi Hamid ادريس سماوي حامد
2015-08-03 16:06                     ` Idris Samawi Hamid ادريس سماوي حامد
2015-08-03 19:25                 ` Otared Kavian
2015-08-03 23:30                   ` Hans Hagen [this message]
2015-08-04 16:25                     ` Otared Kavian
2015-08-03 15:19               ` Hans Hagen
2015-08-03 16:29                 ` talazem
2015-08-03 16:52                   ` talazem
2015-08-04  3:46                     ` talazem
2015-08-04 21:06                       ` 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=55BFF99E.3030902@wxs.nl \
    --to=pragma@wxs.nl \
    --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).