Dear gang,
Consider the following example:
==
\setupdirections[bidi=global,method=one]
\startTEXpage[offset=1em,width=14in]
\definedfont[almfixed*arabic]
\switchtobodyfont[almfixed*arabic]
\switchtobodyfont[almfixed]
% \addff{arabic}
\startbuffer[]
\startlines
الثَّعْلَبُ
On 4/3/2023 7:50 AM, Max Chernoff via ntg-context wrote:
Hi Hans,
This test file:
\setupdirections[bidi=global,method=one]
\starttext
\hbox{$\varepsilon$-TeX}
\stoptext
gives the following error:
callback error:
...ext/tex/texmf-context/tex/context/base/mkxl/typo
Hi Hans,
This test file:
\setupdirections[bidi=global,method=one]
\starttext
\hbox{$\varepsilon$-TeX}
\stoptext
gives the following error:
callback error:
...ext/tex/texmf-context/tex/context/base/mkxl/typo-duc.lmt:618: attempt to
index a nil value (local 'before
designed specifically for that kind of
> stuff). A missing seeting?
>
>
>
> Best,
>
> Denis
>
>
>
> \definefontfamily[notok][rm][SBL Hebrew][features=hebrew]
>
> \definefontfamily[ok][rm][Linux Libertine O][features=hebrew]
>
>
>
> \setupdirectio
nis
\definefontfamily[notok][rm][SBL Hebrew][features=hebrew]
\definefontfamily[ok][rm][Linux Libertine O][features=hebrew]
\setupdirections[bidi=global,method=unicode]
\starttext
Ok:
{\switchtobodyfont[notok]
חִיוּחוחַ
}
Broken:
{\switchtobodyfont[notok]
חִיוּחוֹחַ
}
Linux Libertine works in both cases:
), and
appear between parenthesis
% numbers in footer should use Arabic numbers (e.g. 0123456789), and
without parenthesis
%
% MWE uses dejavu for English and Amiri for and Arabic. Amiri is availble
at https://www.amirifont.org/
\mainlanguage[en-gb]
\setupdirections[bidi=global,method=one
Problems I and II are apparently solved in the latest update. As for III,
the following works:
\definefont[ARABICFONT][file:almfixed.otf*arabic at 28pt]
\noheaderandfooterlines
\setupwhitespace[big]
% \starttext
\startTEXpage[offset=1ex]
% \setupdirections[bidi=global,method=one
]
% \setupinterlinespace[line=4.2ex]
\starttext
% \startTEXpage[offset=1ex]
\setupdirections[bidi=global,method=one]
\righttoleft
\ARABICFONT
خَ % a
خَل
% \stopTEXpage
\stoptext
==
Three bugs:
I. If we use start|stoptex and comment start|stopTeXpage, then both
lines 19 and 21 give
][file:UthmanTN1_Ver10.otf*arabic at 28pt]
% \definefont[ARABICFONT][file:almfixed.otf*arabic at 28pt]
\disabledirectives[filters.utf.reorder]
\noheaderandfooterlines
\setupwhitespace[big]
% \setupinterlinespace[line=4.2ex]
\starttext
% \startTEXpage[offset=1ex]
\setupdirections[bidi=global,method=one
and simplified the example, removing the
spaceskip and delimitedtext.
New example, in which I get a spurious line after the third and fourth
Walt Kelly entries:
%% Demonstration of spurious line insertion on full paragraph with bidi
\setupdirections [bidi=on,method=unicode
e same installation./
%% Demonstration of spurious line insertion on full paragraph with
bidi active
\setupdirections [bidi=on,method=unicode]
\definepapersize [Testing]
[width=6.69in]
\setuppapersize [Testing]
\setuplayout [wid
With the latest LMTX standalone (ConTeXt ver: 2021.06.18) the Syriac text
is not printed.
\setupdirections[bidi=global, method=unicode]
\definefontfeature
[syriac]
[syriac]
[language=dflt, script=syrc]
\definefallbackfamily[mainface][rm][Estrangelo Edessa]
[range={syriac},
features
ration of spurious line insertion on full paragraph with
bidi active
\setupdirections [bidi=on,method=unicode]
\definepapersize [Testing]
[width=6.69in]
\setuppapersize [Testing]
\setuplayout [width=fit,
backspace
Hagen <j.ha...@xs4all.nl> escribió:On 1/7/2021 3:04 PM, Jairo A. del Rio wrote:> Hmm, it works for Persian because this uses less diacritics than Arabic. > The following fails with LMTX:> > \definefontfamily[main][serif][notonaskharabic][features=arabic]> > \setupdirection
fails with LMTX:
> >
> > \definefontfamily[main][serif][notonaskharabic][features=arabic]
> >
> > \setupdirections[bidi=global,method=one]
> >
> > \setupbodyfont[main]
> >
> > \starttext
> >
> > \obeylines
> >
> > %
> https://www.letsstartthink
On 1/7/2021 3:04 PM, Jairo A. del Rio wrote:
Hmm, it works for Persian because this uses less diacritics than Arabic.
The following fails with LMTX:
\definefontfamily[main][serif][notonaskharabic][features=arabic]
\setupdirections[bidi=global,method=one]
\setupbodyfont[main]
\starttext
Hmm, it works for Persian because this uses less diacritics than Arabic.
The following fails with LMTX:
\definefontfamily[main][serif][notonaskharabic][features=arabic]
\setupdirections[bidi=global,method=one]
\setupbodyfont[main]
\starttext
\obeylines
%https://www.letsstartthinking.org
init=yes,medi=yes,fina=yes,isol=yes,
>
>liga=yes,dlig=yes,rlig=yes,clig=yes,
>
>mark=yes,mkmk=yes,kern=yes,curs=yes]
>
> \definefontfamily[main][serif][sakkalmajalla][features=arabic]
>
> \setupbodyfont[main]
>
> \setupdirections[bidi=global]
,fina=yes,isol=yes,
liga=yes,dlig=yes,rlig=yes,clig=yes,
mark=yes,mkmk=yes,kern=yes,curs=yes]
\definefontfamily[main][serif][sakkalmajalla][features=arabic]
\setupbodyfont[main]
\setupdirections[bidi=global]
\starttext
أهلاً وسهلاً
\stoptext
Is that a bug or are more features
lable for testing:
>> > |
>> >
>> > |
>> > \mainlanguage[arabic] \definefontfeature [arabic]
>> > [mode=node,language=dflt,script=arab,
>> > init=yes,medi=yes,fina=yes,isol=yes,
>> > liga=yes,dlig=yes,
sting:
> > |
> >
> > |
> > \mainlanguage[arabic] \definefontfeature [arabic]
> > [mode=node,language=dflt,script=arab,
> > init=yes,medi=yes,fina=yes,isol=yes,
> > liga=yes,dlig=yes,rlig=yes,clig=yes,
> > mark=yes,mkmk=yes,kern=yes,curs=yes]
>
]
[mode=node,language=dflt,script=arab,
init=yes,medi=yes,fina=yes,isol=yes,
liga=yes,dlig=yes,rlig=yes,clig=yes,
mark=yes,mkmk=yes,kern=yes,curs=yes]\definefontfamily[main][serif][sakkalmajalla][features=arabic]\setupbodyfont[main]\setupdirections[bidi=global]\starttext
أهلاً وسهلاً
the effect!
%\setupdirections[bidi=global,method=unicode]
\mainlanguage[de]
\setupitaliccorrection[global, always]
\setupbodyfontenvironment[default][em=italic]
\setupfontprotrusion [quality] [left=0]
\definefontfeature[default][default][
script=latn,
protrusion=quality
,stretch]
\setupdirections[bidi=global,method=unicode]
\starttext
\starttabulate[|p|p|]
\NC Text
\NC Translation
\NC\NR
\NC\setupalign[r2l]\input ward
\NC\input ward
\NC\NR
\stoptabulate
\stoptext
==
But, this here fails:
\setupalign[verytolerant,stretch]
\setupdirections
Denis Maier schrieb am 26.09.2020 um 22:39:
Am 23.09.2020 um 16:04 schrieb Wolfgang Schuster:
Denis Maier schrieb am 23.09.2020 um 14:14:
Hi,
this example produces correctly aligned right-to-left text:
\setupalign[verytolerant,stretch]
\setupdirections[bidi=global,method=unicode
Am 23.09.2020 um 16:04 schrieb Wolfgang Schuster:
Denis Maier schrieb am 23.09.2020 um 14:14:
Hi,
this example produces correctly aligned right-to-left text:
\setupalign[verytolerant,stretch]
\setupdirections[bidi=global,method=unicode]
\starttext
\starttabulate[|p|p|]
\NC Text
e just added a new fontfallbac:
> \definefallbackfamily[mainface][rm][Scheherazade] [range=arabic,
> force=yes, features=arabic]
>
> Bidi is activated with \setupdirections[bidi=global,method=unicode]
>
> Is that enough for Arabic? Or are there other things I need to take care
> of?
Denis Maier schrieb am 23.09.2020 um 14:14:
Hi,
this example produces correctly aligned right-to-left text:
\setupalign[verytolerant,stretch]
\setupdirections[bidi=global,method=unicode]
\starttext
\starttabulate[|p|p|]
\NC Text
\NC Translation
\NC\NR
\NC\setupalign[r2l]\input
Hi,
this example produces correctly aligned right-to-left text:
\setupalign[verytolerant,stretch]
\setupdirections[bidi=global,method=unicode]
\starttext
\starttabulate[|p|p|]
\NC Text
\NC Translation
\NC\NR
\NC\setupalign[r2l]\input ward
\NC\input ward
\NC\NR
\stoptabulate
=hebrew,
force=yes, features=hebrew]
%\definefontfamily[mainface][rm][Tex Gyre Pagella]
%\setupbodyfont[mainface]
\setupalign[r2l]
\setupdirections[bidi=global,method=unicode]
\starttext
פאדא וג̇ד אפעאל אללה תעאלי עלי ג̇איה̈ אלאחכאם ואלאתסאק נחו כלקה̈
אלאנסאן עלי עג̇יב צורתה ותכֿטיטה̈ וחואסה
Hi
Just wondering what the current support for Arabic is. Does anyone know?
My document works fine for Hebrew and I've just added a new fontfallbac:
\definefallbackfamily[mainface][rm][Scheherazade] [range=arabic,
force=yes, features=arabic]
Bidi is activated with \setupdirections[bidi
On 6/3/2019 12:12 PM, Denis Maier wrote:
Hi,
the subject line says it already. What's the difference between
\setupdirections[bidi=global,method=one] and
\setupdirections[bidi=global,method=two]? In which case should I use
`method=one`, when is `method=two` better?
you can use method
Hi,
the subject line says it already. What's the difference between
\setupdirections[bidi=global,method=one] and
\setupdirections[bidi=global,method=two]? In which case should I use
`method=one`, when is `method=two` better?
Best,
Denis
On 5/15/2019 11:48 PM, Alan Bowen wrote:
The following:
\setupdirections[bidi=global]
\definefallbackfamily[mainface][serif][SBL
Hebrew][range={0591-05F4,FB1D-FB4F}]
\definefontfamily[mainface][serif][TeX Gyre Termes]
\setupbodyfont[mainface, 10pt]
\starttext
\setupalign[rtl
The following:
\setupdirections[bidi=global]
\definefallbackfamily[mainface][serif][SBL
Hebrew][range={0591-05F4,FB1D-FB4F}]
\definefontfamily[mainface][serif][TeX Gyre Termes]
\setupbodyfont[mainface, 10pt]
\starttext
\setupalign[rtl]{
ﬡﬡﬢ
}
\setupalign[ltr]
Thanks, Hans!
With \setupdirections[bidi=global,method=three], the footers are placed
correctly. But the *left* footer still does not get RTL treatment. Adding
\setupdirections[bidi=global,method=three] inside startsetups does not help.
Method three has this "bug": a word with
On 2/5/2019 12:36 AM, Mohammad Hossein Bateni wrote:
Hello,
This is perhaps /related/ to what Alan Bowen reported. Not the same,
since I don't get compilation errors.
use method "three"
(I'll add "unicode" method which will take the latest version.)
Hans
Hello,
This is perhaps *related* to what Alan Bowen reported. Not the same, since
I don't get compilation errors.
Here's a MWE. See explanation of bad behavior below.
\setupdirections[bidi=global,method=one]
\definefont[Ar][dejavusans*arabic]
\setupfootertexts[\setups{L}][\setups{R
The latest beta complains and stops when I try to process a book that has
\setupdirections[bidi=global, method=one]
for several, scattered phrases in Arabic and Hebrew (which I do not read).
It works, however, when I set
method=two
or
method=three.
What is the difference between these methods
n file
/Users/bowen1/Desktop/TestTeX/test-02.tex: ?
\setupdirections[bidi=global, method=one]%<——
\defineitemgroup[CList][levels=2]
\setupCList[1][n, broad, packed, autointro, repeat, continue]
[itemalign=flushright,
left={},right={},stopper={.},
margin=0pc,
before={\setupinterlinespace[off]
\s
On 1/27/2019 7:15 PM, Rik Kabel wrote:
That allows the compilation to complete, but method=three breaks other
stuff. Try this:
\starttext
\setupdirections [bidi=on,method=three]
\rightaligned{(( How is this?}
\stoptext
(I also see problems with boxes set in the margin where
On 1/27/2019 12:07, Hans Hagen wrote:
On 1/27/2019 12:59 AM, Rik Kabel wrote:
Here is a much-closer-to minimal example.
\setupregister [index] [maxwidth=4cm]
\setupdirections [bidi=on,method=two]
\starttext
.\index{Mairzy doats and dozy doats and liddle lamzy divey}
\placeindex
On 1/27/2019 12:59 AM, Rik Kabel wrote:
Here is a much-closer-to minimal example.
\setupregister [index] [maxwidth=4cm]
\setupdirections [bidi=on,method=two]
\starttext
.\index{Mairzy doats and dozy doats and liddle lamzy divey}
\placeindex
\stoptext
With the \setupdirections
And shorter still, isolating the problem to something in \limitatetext:
\setupdirections [bidi=on,method=two]
\starttext
\limitatetext {Mairzy doats and dozy doats and liddle lamzy divey} {4cm}
\stoptext
--
Rik
Here is a much-closer-to minimal example.
\setupregister [index] [maxwidth=4cm]
\setupdirections [bidi=on,method=two]
\starttext
.\index{Mairzy doats and dozy doats and liddle lamzy divey}
\placeindex
\stoptext
With the \setupdirections line removed, all is well. However, that line
tex/context/base/mkiv/typo-dub.lua:496: attempt to index
local 'stacktop' (a nil value)
Removing the maxwidth constraint, or setting it to a much wider value,
allows error-free compilation.
Without \setupdirections[bidi=on,method=two] there is no problem, but
without it RTL texts are not hand
)
local nxt=getnext(start)
local dir=getdirection(start) --<--
if dir==lefttoright then
return nxt,1,1
Many thanks for your report, Ulrike.
This was the same problem that prevented the compilation of the
following code:
\setupdirections[bidi=on, method=
of the code:
>>
>> pardirstate=function(start)
>> local nxt=getnext(start)
>> local dir=getdirection(start) --<--
>> if dir==lefttoright then
>> return nxt,1,1
>
> Many thanks for your report, Ulrike.
>
> This was the
On 1/10/2019 5:13 PM, Pablo Rodriguez wrote:
This was the same problem that prevented the compilation of the
following code:
\setupdirections[bidi=on, method=two]
\starttext
\input zapf
\stoptext
this is unlikely as you don't use generic ... probably another fix
dir=getdirection(start) --<--
> if dir==lefttoright then
> return nxt,1,1
Many thanks for your report, Ulrike.
This was the same problem that prevented the compilation of the
following code:
\setupdirections[bidi=on, method=two]
\starttext
\input zapf
\stoptex
it appears, is bidi. I have tried
all documented options (but not all combinations) for
\setupdirections, and the only one under which there is no problem is
"off". With bidi active, there is a spurious space wherever a
linebreak is introduced. As the example demonstrates, this is no
l documented options (but not all combinations) for
\setupdirections, and the only one under which there is no problem is
"off". With bidi active, there is a spurious space wherever a
linebreak is introduced. As the example demonstrates, this is not a
function of the compounds,
not all combinations) for \setupdirections, and
the only one under which there is no problem is "off". With bidi active,
there is a spurious space wherever a linebreak is introduced. As the
example demonstrates, this is not a function of the compounds, but of
hyphenation in general.
tached and below:
===
\setupdirections[bidi=global]
\setupwhitespace[big]
\setupnotation[footnote][style={\setupwhitespace[big],\setupdirections[bidi=global]}]
\starttext
\definedfont[file:almfixed.otf*arabic at 14pt]
Test امتحان test \par Test امتحان test
\startfootnote
\definedfont[file:almfixed.ot
to handle footnote typography options? On the surface,
it appears to be overkill. For the declaration
\setupdirections[bidi=global]
shouldn't that mean that bidi is applied, well, globally?
The same holds for \setupalign[verytolerant], for example, that does
not get applied to a (figure,tabl
it appears to be overkill. For the declaration
\setupdirections[bidi=global]
shouldn't that mean that bidi is applied, well, globally?
The same holds for \setupalign[verytolerant], for example, that does
not get applied to a (figure,table) caption...
These environments (captions, footnotes, ..
On Thu, 21 Jun 2018 06:20:45 -0600
Idris Samawi Hamid ادريس سماوي حامد wrote:
> Many thanks. Question: Is this use of setups now the "official" or
> preferred way to handle footnote typography options? On the surface,
> it appears to be overkill. For the declaration
>
&
not know how heavy setupdirections is, but this method, I guess,
applies that command *once per page*. It might be too much, but it's the
price you pay for correct bidi formatting. For example, I hate to see that
I need to babysit page numbers (LTR) within Farsi text (RTL) in headers but
that's life
Salaam, Mohammad Hossein, Otared,
On Wed, 20 Jun 2018 15:27:56 -0600, Mohammad Hossein Bateni
wrote:
\startsetups[bidi:footnotes]
\setupdirections[bidi=on]
\stopsetups
\setupnotes[footnote][setups=bidi:footnotes]
On Wed, 20 Jun 2018 22:31:05 -0600, Otared Kavian wrote:
% begin
Hi Idriss,
As Mohammad Hossein pointed out, adding a setups solves both problems you
mentioned (font declaration and bidi in footnotes):
% begin test-bidi-footnote.tex
\setupdirections[bidi=global]
\startsetups[bidi:footnotes]
\setupdirections[bidi=on]
\definedfont[file:almfixed.otf*arabic
maybe something like this would help:
\startsetups[bidi:footnotes]
\setupdirections[bidi=on]
\stopsetups
\setupnotes[footnote][setups=bidi:footnotes]
but I did not test it now.
On Wed, Jun 20, 2018 at 5:26 PM Idris Samawi Hamid ادريس سماوي حامد <
idris.ha...@colostate.edu> wrote:
Dear gang,
In the attached/following example, bidi is not applied in the footnote:
\setupdirections[bidi=global]
\starttext
\definedfont[file:almfixed.otf*arabic at 14pt]
Test امتحان test
\startfootnote
\definedfont[file:almfixed.otf*arabic at 14pt]
Test امتحان test
\stopfootnote{}
\stoptext
On 6/7/2018 3:20 AM, Idris Samawi Hamid ادريس سماوي حامد wrote:
Greetings,
mtx-context | current version: 2018.06.02 22:34
In the following, bidi does not work:
===
\setupdirections[bidi=global]
\starttext
\definedfont[file:almfixed.otf*arabic at 14pt]
Test امتحان test
\righttoleft
Greetings,
mtx-context | current version: 2018.06.02 22:34
In the following, bidi does not work:
===
\setupdirections[bidi=global]
\starttext
\definedfont[file:almfixed.otf*arabic at 14pt]
Test امتحان test
\righttoleft
Test امتحان test
\stoptext
===
See attached. This used
; attached. MWE follows.
>
> \definefontfamily [myfamily] [serif] [arabictypesetting] [features=arabic]
> \setupbodyfont[myfamily]
> \setupalign[r2l]
> \setupdirections[bidi=global,method=two]
>
> \setupmixedcolumns[register][direction=reverse]
>
> When you have a
gn[r2l]
\setupdirections[bidi=global,method=two]
\setupmixedcolumns[register][direction=reverse]
When you have a font with large ascender/descender you can increase the
linespacing (line key) or change the height/depth (height and depth
keys) values for \strut.
\startsetups[register:interlin
Same problem, item (6) of email below, observed with arabtype font. See
attached. MWE follows.
\definefontfamily [myfamily] [serif] [arabictypesetting] [features=arabic]
\setupbodyfont[myfamily]
\setupalign[r2l]
\setupdirections[bidi=global,method=two]
\setupmixedcolumns[register
ts]
4 >> \setmainfont[KFGQPC Uthman Taha Naskh][features=arabic,range=arabic]
5 \setcharacterstripping[1]
6 \setupinterlinespace[line=7ex]
7
8 \setupdirections[bidi=on,method=one]
9 \setupalign[r2l]
10
11
12 \starttext
13
14 \tfb
Thanks,
~MHB
On Sat, Apr 30, 2016 a
kh][features=arabic,range=arabic]
5 \setcharacterstripping[1]
6 \setupinterlinespace[line=7ex]
7
8 \setupdirections[bidi=on,method=one]
9 \setupalign[r2l]
10
11
12 \starttext
13
14 \tfb
Thanks,
~MHB
On Sat, Apr 30, 2016 at 1:06 PM, Hans Hagen <pra...@wxs.nl> wrote:
> On 4/29
ith extra space below. See attached PDF and the MWE. (I could not
reproduce this with DejaVuSans or ALM Fixed.)
\definefontfamily [myfamily] [serif] [Scheherazade] [features=arabic]
\setupbodyfont[myfamily]
\setupalign[r2l]
\setupdirections[bidi=global,method=two]
\setupmixedcolumns[register]
local 'i' (a nil value)
tex error > tex error on line 7 in file
C://Users/rik/Desktop/comp_body.tex: ?
Code:
\setupdirections [bidi=global]
\definefont [hebrew] [default] [lang=heb,ccmp=yes,script=hebr]
\definefont [Hebrew] [sileotsr*hebrew sa .9]
\startt
On 4/29/2016 12:00 PM, Mohammad Hossein Bateni wrote:
Actually the MWE may help:
\usemodule[simplefonts]
\setmainfont[KFGQPC Uthman Taha Naskh][features=arabic,range=arabic]
\setcharacterstripping[1]
\setupdirections[bidi=on,method=one]
\setupalign[r2l]
\starttext
\tfb
الْحَمْدُ
\stoptext
Actually the MWE may help:
\usemodule[simplefonts]
\setmainfont[KFGQPC Uthman Taha Naskh][features=arabic,range=arabic]
\setcharacterstripping[1]
\setupdirections[bidi=on,method=one]
\setupalign[r2l]
\starttext
\tfb
الْحَمْدُ
\stoptext
—MHB
On Fri, Apr 29, 2016 at 5:52 AM, Mohammad Hossein
if there is already a way to tell ConTeXt to do it in the
> right way, or Hans has to look into the righttoleft mechanism.
> > The same issue appears in the table mechanism.
> >
> > By the way, the option
> > [direction=reverse]
> > seems to have no effect at al
look into the righttoleft mechanism.
> The same issue appears in the table mechanism.
>
> By the way, the option
> [direction=reverse]
> seems to have no effect at all in Right-to-Left environment.
>
> %%% begin example-RtoL-reverse.tex
> \usemodule[simplefonts]
> \setmainfont[A
the table mechanism.
>
> By the way, the option
> [direction=reverse]
> seems to have no effect at all in Right-to-Left environment.
>
> %%% begin example-RtoL-reverse.tex
> \usemodule[simplefonts]
> \setmainfont[ALM Fixed][features=arabic,range=arabic]
>
> \setupdirections
environment.
%%% begin example-RtoL-reverse.tex
\usemodule[simplefonts]
\setmainfont[ALM Fixed][features=arabic,range=arabic]
\setupdirections[bidi=global,method=two]
\setupalign[righttoleft]
\starttext
آزمایش نوشتن از راست به چپ
\startitemize[columns,two][direction=reverse]
\item First
\item
umbers in the main body are
written from right to left. I'm starting to wonder whether it does anything
nontrivial at all.
\usemodule[simplefonts]
\setmainfont[ALM Fixed][features=arabic,range=arabic]
\setupdirections[bidi=global,method=two]
\setupalign[r2l]
\starttext
سال ۲۰۱۶
2016
\stoptext
nontrivial at all.
> >
> > \usemodule[simplefonts]
> > \setmainfont[ALM Fixed][features=arabic,range=arabic]
> >
> > \setupdirections[bidi=global,method=two]
> > \setupalign[r2l]
> >
> > \starttext
> >
> > سال ۲۰۱۶
> >
> > 201
eft. I'm starting to wonder whether it does
> anything nontrivial at all.
>
> \usemodule[simplefonts]
> \setmainfont[ALM Fixed][features=arabic,range=arabic]
>
> \setupdirections[bidi=global,method=two]
> \setupalign[r2l]
>
> \starttext
>
> سال ۲۰۱۶
>
> 2016
Unfortunately when I use method=two for bidi, the numbers in the main body
are written from right to left. I'm starting to wonder whether it does
anything nontrivial at all.
\usemodule[simplefonts]
\setmainfont[ALM Fixed][features=arabic,range=arabic]
\setupdirections[bidi=global,method=two
Thanks, Hans! This does solve the problem with the list of numbers. And
actually if I add a numberstyle field, I can the section heads the way I
like. Here is the setup that worked. (I will update Wiki later.)
\setupdirections[bidi=global,method=two]
\setupalign[r2l]
\def\LTR#1{{\lefttoright
abic]
\setupdirections[bidi=global,method=default]
\setupalign[r2l]
\starttext
اعداد ۱، ۲، ۳ و ۴ را در نظر بگیرید.
اعداد 1، 2، 3 و 4 را در نظر بگیرید.
اعداد 1, 2, 3 و 4 را در نظر بگیرید.
\stoptext
I expect the numbers 1, 2, 3 and 4 to appear in the same order from
right to left. However, the vi
Hans & Wolfgang,
Do you have suggestions here? How can I get the behavior I want for the
section head numbers?
In fact, the following may be quite relevant.
\usemodule[simplefonts]
\setmainfont[ALM Fixed][features=arabic,range=arabic]
\setupdirections[bidi=global,method=default]
\setupa
the following
(aligned to the right).
elpmas 1
txet 1-1
txet 2-1
txet 3-1
...
txet 10-1
Here's the first attempt.
%% Attempt 1
\setupalign[r2l]
\starttext
\placecontent
\chapter{sample}
\dorecurse{10}{\section{text}}
\stoptext
The result is:
elpmas 1
txet 1-1
...
txet 01-1
Then I add "\setupdirec
{\getmarking[chapter]}]
Ideally \setupdirections[bidi] or something like that should be used, as I
mentioned in the other thread; that'll fix a bunch of other problems, as
well
I did enable \setupdirections[bidi=global] and it did not help.
Here is how it was solved. I could not use your solution
nd I can use my hacky solution and mix \lefttoright
and \righttoleft to get it right. But is it possible to extend the
\setupdirections[bidi=on] to apply to parts other than the main text? I
just noticed this does not apply to footnotes either. Having numbers in
the TRL footnote text produces
rsian. Then the text of the
header is partly LTR and part RTL.
This is still simple and I can use my hacky solution and mix
\lefttoright and \righttoleft to get it right. But is it possible to
extend the \setupdirections[bidi=on] to apply to parts other than the
main text? I just noticed thi
e my hacky solution and mix \lefttoright
> and \righttoleft to get it right. But is it possible to extend the
> \setupdirections[bidi=on] to apply to parts other than the main text? I
> just noticed this does not apply to footnotes either. Having numbers in
> the TRL footnote tex
Code:
\mainlanguage[arabic]
\setupdirections[bidi=global]
\definefontfeature
[arabic]
[mode=node,language=dflt,script=arab,
init=yes,medi=yes,fina=yes,isol=yes,
liga=yes,dlig=yes,rlig=yes,tlig=yes,
calt=yes,trep=yes,clig=yes,
mark=yes,mkmk=yes,kern=yes,curs=yes
This makes all the text LTR, for instance if one has an English word
embedded in the RTL text, that will be shown incorrectly. Or even if one
of the headers (say, on the left side) is plain English.
Why wouldn't something like the following work?
\startsetups setup:bidi
\setupdirections[bidi
One hacky way to fix it is the following:
\setupheadertexts
[{\getmarking[chapter]}][{\lefttoright\pagenumber}]
[{\lefttoright\pagenumber}][{\getmarking[chapter]}]
Ideally \setupdirections[bidi] or something like that should be used, as I
mentioned in the other thread
Mohammad Hossein Bateni gmail.com> writes:
>
>
> One hacky way to fix it is the following:
>
> \setupheadertexts [{\getmarking[chapter]}]
[{\lefttoright\pagenumber}] [{\lefttoright\pagenumber}]
[{\getmarking[chapter]}]
>
>
> Id
appear correctly. I couldn't
> figure out a similar mechanism for figure numbers, though. The example
> does not use Indic numbers, which does not have any effect on the problem.
>
>
> \setupdirections[bidi=global,method=two]
> \setupalign[r2l]
>
> %% If we don't provide
footnote numbers
>> are fine. Section numbers need some care to appear correctly. I couldn't
>> figure out a similar mechanism for figure numbers, though. The example
>> does not use Indic numbers, which does not have any effect on the problem.
>>
>>
>> \s
On 1/17/2016 7:47 PM, Ibn Saeed wrote:
I have also made a post at tex.stackexchange.com
I am trying to get Arabic Chapter Name in the header and some arabic text in
the margins using ConTeXt MarkIV
Here is the code:
\mainlanguage[arabic]
\setupdirections[bidi=global]
\definefontfeature
I have also made a post at tex.stackexchange.com
I am trying to get Arabic Chapter Name in the header and some arabic text in
the margins using ConTeXt MarkIV
Here is the code:
\mainlanguage[arabic]
\setupdirections[bidi=global]
\definefontfeature
[arabic]
[mode=node,language=dflt,script
roblem.
\setupdirections[bidi=global,method=two]
\setupalign[r2l]
%% If we don't provide the numbercommand, we'll see reverse numbering
starting from 10.
\setuphead[chapter,title,section,subject][numbercommand=\righttoleft]
%% The following does not accept any numbercommand but it has
numberconv
are fine. Section numbers need some care to appear correctly. I couldn't
figure out a similar mechanism for figure numbers, though. The example
does not use Indic numbers, which does not have any effect on the problem.
\setupdirections[bidi=global,method=two]
\setupalign[r2l]
%% If we don't provide
:
\setupinteraction[state=start]
\setupreferencing[left=, right=, interaction=all]
\setupdirections[bidi=on,method=two]
\starttext
\section[sectionone]{Section one}
No text after the first line:\\\about[sectionone]
Misplaced text
\stoptext
Text after \about
1 - 100 of 207 matches
Mail list logo
