Re: [NTG-context] wrong behaviour with ConTeXt unicode bidi

2013-09-11 Thread Vafa Khalighi
I tried the latest beta; it fixes the problem I mentioned but breaks something else: \starttext \setupalign[r2l] \definefont[arabicfont][Arial*arabic at 20pt] \setupdirections[bidi=global,method=default] \hbox dir TRT{\arabicfont (1984)} \stoptext If you have \hbox dir TLT, you get

Re: [NTG-context] Gray unit

2013-09-11 Thread Hans Hagen
On 9/10/2013 8:04 PM, Christian Prim wrote: Hello the physical unit Gray has Gy as symbol (see http://en.wikipedia.org/wiki/Gray_(unit) ). Context returns Gr. MWE: \starttext \unit{1 Gray} \stoptext Thanks for fixing this little bug. patched

Re: [NTG-context] wrong behaviour with ConTeXt unicode bidi

2013-09-11 Thread Vafa Khalighi
Also the itemize environment is broken too (perhaps same issue is here too): \setupitemize[left=(, right=), margin=4em, stopper=] \starttext \setupalign[r2l] \definefont[arabicfont][Arial*arabic at 20pt] \setupdirections[bidi=global,method=default] \arabicfont \startitemize[a] \item اولی \item

Re: [NTG-context] wrong behaviour with ConTeXt unicode bidi

2013-09-11 Thread Hans Hagen
On 9/11/2013 1:34 PM, Vafa Khalighi wrote: Also the itemize environment is broken too (perhaps same issue is here too): \setupitemize[left=(, right=), margin=4em, stopper=] \starttext \setupalign[r2l] \definefont[arabicfont][Arial*arabic at 20pt] \setupdirections[bidi=global,method=default]

[NTG-context] imposition 2SIDE: feature request

2013-09-11 Thread Thomas A. Schmitz
I know this is a bit silly, but maybe useful for a few people: the 2SIDE arrangement is nice for printing out and previewing book pages on A4 landscape. However, the arrangement has even and odd pages swapped. Would it be possible to define a scheme which does exactly the same as 2SIDE, but

Re: [NTG-context] wrong behaviour with ConTeXt unicode bidi

2013-09-11 Thread Khaled Hosny
On Wed, Sep 11, 2013 at 02:37:35PM +0200, Hans Hagen wrote: anyway, it would be nice to see where the three methods fail: Of the three, method one seems to give correct results on all the given tests (I’m yet to test with my own documents). I’m skeptical that bidi can be implemented in a one

Re: [NTG-context] Replacement with a predefined table?

2013-09-11 Thread Hans Hagen
On 9/11/2013 7:10 PM, H. Özoguz wrote: Is the following possible in ConText? I want to define a table like this: 1: Hans 2: Wolfgang 3: Aditja 4: Marco in which I can look up by a function, which allows the following command: \name{number}. E.g. This is \name{3} should compile to This

[NTG-context] Replacement with a predefined table?

2013-09-11 Thread H. Özoguz
Is the following possible in ConText? I want to define a table like this: 1: Hans 2: Wolfgang 3: Aditja 4: Marco ... in which I can look up by a function, which allows the following command: \name{number}. E.g. This is \name{3} should compile to This is Aditja. For my purpose, the table

Re: [NTG-context] wrong behaviour with ConTeXt unicode bidi

2013-09-11 Thread Hans Hagen
On 9/11/2013 5:24 PM, Khaled Hosny wrote: On Wed, Sep 11, 2013 at 02:37:35PM +0200, Hans Hagen wrote: anyway, it would be nice to see where the three methods fail: Of the three, method one seems to give correct results on all the given tests (I’m yet to test with my own documents). I’m

Re: [NTG-context] Kashide in ConTeXt

2013-09-11 Thread Idris Samawi Hamid ادريس سماوي حامد
Salaam, Vafa,On Tue, 10 Sep 2013 09:34:23 -0600, Vafa Khalighi persian-...@tug.org wrote:it is about stretching words.It can be done manually, of course, by just manual insertions ofU+0640. Did you mean something else by 'manual'?As for automatic, it is in the pipeline and my hope is it will be