On Tue, Sep 02, 2008 at 08:25:38PM +0200, Hans Hagen wrote:
> Khaled Hosny wrote:
> core-con.mkiv 20: \def\abjadnumerals
> #1{\ctxlua{converters.arabicnumerals(\number#1)}}
> core-con.mkiv 21: \def\abjadnodotnumerals
> #1{\ctxlua{converters.arabicnodotnumerals(\number#1)}}
> core-con.mkiv 22: \de
Khaled Hosny wrote:
> On Sat, Aug 23, 2008 at 12:46:47AM +0300, Khaled Hosny wrote:
>> It seems that there is a bug in converters.alphabetic function,
>> converters.alphabetic(0,"arabic") returns the western 0 (no matter what
>> is the selected language) while converters.alphabetic(1,"arabic") give
On Mon, Sep 01, 2008 at 07:26:43PM +0200, Khaled Hosny wrote:
> Now, I think I discovered another bug (or feature?), the function will
> ignore any zeros at the left which isn't what one expects.
This happen to be some thing in Lua itself:
s = 000123 print(s)
will give 123, so it have to be a stri
On Sat, Aug 23, 2008 at 12:46:47AM +0300, Khaled Hosny wrote:
>
> It seems that there is a bug in converters.alphabetic function,
> converters.alphabetic(0,"arabic") returns the western 0 (no matter what
> is the selected language) while converters.alphabetic(1,"arabic") gives
> the Arabic 0 not 1
It seems that there is a bug in converters.alphabetic function,
converters.alphabetic(0,"arabic") returns the western 0 (no matter what
is the selected language) while converters.alphabetic(1,"arabic") gives
the Arabic 0 not 1 and so one i.e. it looks like as if it starts
counting from zero.
This
