Hi Mathew,
I think you are being a bit unfair towards Vafa!
LaTeX, et al are highly complex. The advent of unicode has not made things
easier.
The problem is not that bidi or the other package is "faulty", but in the way it
is done, so that when then two are used together the result is not what
>
> Knowing that your attitude is that compatibility is everybody else's
> job and not yours, I sure wouldn't have been quick to reply to you if I
> were one of those package maintainers.
>
There are too many packages on CTAN, I do not know their number but let say
there are one thousands of them
On Fri, 23 Sep 2011, VAFA KHALIGHI wrote:
> When I started as the maintainer of bidi, I contacted some of the
> package/class authors unfortunately no one even bothered to reply back (at
> least saying, no I do not have time or I do not know how to do it) and
> indeed that is why bidi itself, suppo
Hi Vafa,
I kind of figured as much.
The only, I can do for you is to ask.
Can anybody. please help him. I assume many problems is that the
packages either do not support unicode
of are not designed to work with RTL. I am sure if the packages are
fixed other pro
>
> Vafa, have you tried asking the authors of the packages that you
> support(work around their short commings)
> to support, bidi or RTL. They are most likely not aware of the problems,
> because the designed their package
> only of LTR. Maybe you, can gather a group around you that will modify
Hi Nathan, Vafa,
TeX, LaTeX, Xe(La)TeX, Lua(La)Tex, etc come with a very steep learning
curve.
It was one of the reasons I stopped using LaTeX some 20 years ago.
Also, back then the packages were not stable and conflicted with each
other so if
really ne
Yes, of course you are right. However, many of the older LaTeX packages
are not being developed very actively any more (or not at all in some
cases) so it makes it difficult to decide what to use when one need the
functionality of some of the older packages but also wants to work with
unicode,
>
> For how long have bidi and ednotes been incompatible? François Charette ,
> who maintains arabxetex and works on polyglossia, wrote an example file
> showing how to use arabxetex + bidi with ednotes to produce critical
> editions, so I assumed there would be some effort to keep the packages
> c
By the way, I do not know why you are using ednotes.sty. If it is because of
footnote support, bidi package also allows you to do paragraph footnotes.
For more details, see bidi manual. ednotes is not supported by bidi and its
use together with bidi should be avoided.
On Thu, Sep 22, 2011 at 5:16
I could not be bothered looking through lineno.sty to see what setups they
have so this is another quick/dirty fix. The problem is that in the
definition of \MakeLineNo, they use \sbox, \sbox itself uses
\s...@color.bidi changes the definition of \set@colorwhen color/xcolor
package is loaded such t
Thanks, that works.
Is there anyway to control the placement of the numbers? They look good
besides the introductory material but once the text proper begins, they
are pressed right up against the text.
Here is a minimal example:
\documentclass{article}
\usepackage{pstricks}
\usepackage{pst
Put it before \begin{document}, in addition you need to put
\rightlinenumbers after \resetlinenumber\pagewiselinenumbers
On Thu, Sep 22, 2011 at 3:17 PM, Nathan Sidoli wrote:
> Thanks for this.
>
> Where are you putting this code?
>
> I tried in various places in the preamble. Does it need to be
Thanks for this.
Where are you putting this code?
I tried in various places in the preamble. Does it need to be put in one
of the packages?
On 11/09/22 2:35, VAFA KHALIGHI wrote:
bidi does not support lineno.sty and you are on your own if you decide
to use it but here is the fix:
\mak
bidi does not support lineno.sty and you are on your own if you decide to
use it but here is the fix:
\makeatletter
\@ifpackageloaded{color}{%
\def\makeLineNumberRight{%
\linenumberfont\hskip-\linenumbersep\hskip-\columnwidth
\hb@xt@\linenumberwidth{\hss\LineNumber}\hss}}{}
\makeatother
If yo
Well, as you guessed, it does seem to be something to do with the
interaction between bidi and pstricks.
Here is a minimal example with no bidi, which shows the line numbers
along with a figure, etc.
---
\documentclass{article}
\usepackage{pstricks}
\usepackage{pst-eps}
do you have a minimal example? Can you create one where bidi is not loaded
at all? maybe endnotes does not behave well with pstricks.
On Thu, Sep 22, 2011 at 12:48 AM, Nathan Sidoli
wrote:
> I have tried loading them in every possible order, but as soon as I load
> pstricks the marginal numbers
I have tried loading them in every possible order, but as soon as I load
pstricks the marginal numbers disappear.
On 11/09/21 23:43, VAFA KHALIGHI wrote:
No, I think it has to do with something that tikzpicture or pspicture
environment are in LTR mode by bidi. you can load endnotes anywhere
y
No, I think it has to do with something that tikzpicture or pspicture
environment are in LTR mode by bidi. you can load endnotes anywhere you want
but certainly bidi gives you error if you load tikz or pstricks after bidi,
thus you only will have to load tikz or pstricks before bidi.
2011/9/22 Zde
2011/9/21 VAFA KHALIGHI :
> I am not sure what is the actual problem but I can tell you what bidi does.
> bidi does the following:
>
Can it depend on the order in which the packages are loaded? This is
what I would try. My feeling is that the correct order would be tikz,
endnote, bidi.
> 1- makes
I am not sure what is the actual problem but I can tell you what bidi does.
bidi does the following:
1- makes l and r logical such that l means always left and r always means
right (in both RTL and LTR).
2- bidi automatically puts tikzpicture and pspicture envoronments in LTR
mode mainly for two
I realize this is not strictly speaking a XeTeX issue, but I am
typesetting a critical edition of an Arabic text using XeLaTeX with the
ednotes package and I want to be able to make the diagrams for the text
using either pstricks or TikZ so that the Arabic fonts can be changed in
the text and d
21 matches
Mail list logo
