bidi option regression error

[GoogleCodeExporter]

tufte-latex 3.5.0:

The attached tex source (Tufte-Latex3.5.0MinimalExample.tex using TeXLive 2010) 
complies xelatex with only the hyperref error " Option `pagecolor' is not 
available anymore."

However, when I add the "bidi" option, I get:

"! Package bidi Error: Oops! you have loaded package xcolor after bidi package."

I've attached the log file, which shows some additional errors.

In a more complex file with citations, I get the same bolixed citations as I 
reported in Issue #14: http://code.google.com/p/tufte-latex/issues/detail?id=14.

Original issue reported on code.google.com by Empirica...@gmail.com on 16 Jun 2011 at 11:39

Attachments:

• Tufte-Latex3.5.0MinimalExample.tex
• Tufte-Latex3.5.0MinimalExample.pdf
• Tufte-Latex3.5.0MinimalExample.log

[GoogleCodeExporter]

The uploaded file does not have the 'bidi' option enabled. Add that to get the 
error I reported.

Original comment by Empirica...@gmail.com on 16 Jun 2011 at 11:40

[GoogleCodeExporter]

I do not understand why tufte-latex tries to load bidi. The user can himself 
load the bidi package at the end and non of these problems would appear. If 
tufte-latex really tries to change any of bidi commands such as \@footnotetext, 
there is no need to load bidi. Use hopatch package:

\RequirePackage{hopatch}
\hopatch@AfterPackage{bidi}{tufte-latex changes to bidi}

I am actually making tufte-latex bidi-enabeled. I have decided to break it into 
smaller packages. So far I have done the part for the float part of tufte-latex 
and called it bidifloat. The following sample shows mainly an example of this 
package in RTL.

Original comment by vafa...@gmail.com on 16 Jun 2011 at 11:53

Attachments:

• test.pdf
• test.tex

[GoogleCodeExporter]

Also some of the internals that tufte-latex uses for bidi has changed. For 
instance the conditional \if@rl is changed to \if@RTL. However \if@rl is still 
supported. Some of the codes in tufte-latex related to bidi do nothing and I am 
not sure why they are written.

Original comment by vafa...@gmail.com on 16 Jun 2011 at 11:58

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Update: I downgraded to 3.0.0 and, although I still get the errors, "Oops! you 
have loaded package {xcolor, etc.} after bidi package", I can get a suitably 
typeset pdf.

@vafa: Far be it from me to suggest what the best way is to make tufte-latex 
and bidi to play nicely! :-) I appreciate your efforts; I'll be happy to test 
anything you come up with. My day job is as a researcher in ancient near 
eastern languages, especially ancient Hebrew, so I use bidi a lot. Your work 
makes me effective! Thanks.

Original comment by Empirica...@gmail.com on 16 Jun 2011 at 12:24

[GoogleCodeExporter]

That is because xcolor or a package that calls xcolor is loaded after bidi. 
bidi should be the last loaded package.

Original comment by vafa...@gmail.com on 16 Jun 2011 at 12:29

[GoogleCodeExporter]

I have finished bidi-izing the tufte-latex class. The two classes are 
respectively biditufte-handout and biditufte-book. There is no manual at the 
moment and you need to use tufte-latex manual. Please note that some macros and 
options have been added apart from what original tufte-latex offers, also some 
of the tufte-latex features which are meaningless in RTL typography have been 
omitted, as an example there is no need for soul, letterspace and macrotype 
packages. You will nead to install both bidi and xepersian experimental TDSs.

Download bidi experimental TDS from 
https://bitbucket.org/vafa/bidi/downloads/bidi-18-06-11.tds.zip

Download xepersian experimental TDS from 
https://bitbucket.org/vafa/xepersian/downloads/xepersian-18-06-11.tds.zip

Original comment by vafa...@gmail.com on 18 Jun 2011 at 8:40

[GoogleCodeExporter]

Wow!  Okay, there's a lot of stuff for me to look at here.

Kirk: When I add the bidi option to the .tex file you provided in comment #1, 
it compiles okay for me.  Can you add the 'debug' option and compile it again 
on your end and upload the .log file, please?

Vafa: The hopatch package didn't exist at the time I wrote this code for 
tufte-latex.  But to answer your question of 'why did you load bidi in the 
class file?', I plead ignorance. In the new code I'm working on, it does do as 
you suggest and patch the code if it detects particular packages have been 
loaded.

I've only started to look at the bidi-tufte code you wrote.  Would it be better 
if that compatibility code lived in the tufte-latex classes themselves?

Original comment by godbyk@gmail.com on 18 Jun 2011 at 6:07

[GoogleCodeExporter]

@Kevin: did you enable the 'bidi' option? The file did not have it enabled (my 
mistake). Attached is the same file with [bidi,debug] plus log file.

Original comment by Empirica...@gmail.com on 18 Jun 2011 at 9:52

Attachments:

• Tufte-Latex3.5.0MinimalExample.tex
• Tufte-Latex3.5.0MinimalExample.log

[GoogleCodeExporter]

@Kirk: I did enable bidi previously and didn't see any errors.  Looking through 
the log file you supplied, I don't see any errors there, either.

What error message are you getting?  Or what problems do you see with the 
generated PDF?

Original comment by godbyk@gmail.com on 18 Jun 2011 at 9:57

[GoogleCodeExporter]

@Kevin: Hmmm. The debug option didn't preserve the error messages. I wonder 
why? Attached is the log file without the 'debug' option. The errors are there.

Original comment by Empirica...@gmail.com on 18 Jun 2011 at 10:01

Attachments:

• Tufte-Latex3.5.0MinimalExample.log

[GoogleCodeExporter]

@Kirk: I'm not sure what weirdness is happening there.  I've bumped the version 
number of the tufte-common.def file in svn to help with debugging.  Can you 
download that file and try it?  (You'll need to have the hardwrap package 
installed, too: <http://ctan.org/pkg/hardwrap>.)

Original comment by godbyk@gmail.com on 18 Jun 2011 at 10:13

[GoogleCodeExporter]

Oh! I should mention that I'm using xelatex. In my efforts to create a minimal 
example, I did not use any xelatex special features. If you do use pdflatex, 
you should get an error that only xetex and luatex are supported by bidi....

Original comment by Empirica...@gmail.com on 18 Jun 2011 at 10:14

[GoogleCodeExporter]

The main purpose of writing biditufte was that you can see how it is done and 
then you can apply it in original tufte-latex, whenever the required code from 
biditufte to tufte is applied, I will delete biditufte. 

Original comment by vafa...@gmail.com on 19 Jun 2011 at 12:43

[GoogleCodeExporter]

I can't do an svn checkout:

svn checkout http://tufte-latex.googlecode.com/svn/trunk/ tufte-latex-read-only
svn: Server sent unexpected return value (502 Bad Gateway) in response to 
PROPFIND request for '/svn/!svn/vcc/default'

Looks like the server has changed to something like 'code.google.com', but 
substituting that doesn't work, either. :-(

Original comment by Empirica...@gmail.com on 19 Jun 2011 at 1:21

[GoogleCodeExporter]

A few hours later I could check out r169. It was some sort glitch with the 
server that cleared up. Testing now...

Original comment by Empirica...@gmail.com on 19 Jun 2011 at 9:22

[GoogleCodeExporter]

Attached is the log file generated by the test file with [bidi,debug] using 
tufte-latex r169. Hope it helps. :-)

Original comment by Empirica...@gmail.com on 19 Jun 2011 at 9:30

Attachments:

• Tufte-Latex3.5.0MinimalExample.log

[GoogleCodeExporter]

@Kirk: Okay, it looks like that was compiled with version 3.5.0 (located in 
/usr/local/texlive/2010/texmf-dist/tex/latex/tufte-latex/tufte-common.def) 
instead of r169 (version 3.5.2).

Try dropping the r169 version of the tufte-common.def file into the same 
directory as your .tex file and see if you still have the issue.

Original comment by godbyk@gmail.com on 19 Jun 2011 at 9:34

[GoogleCodeExporter]

I discovered a problem with my local texmf links (I'm running MacTeX at the 
moment). Here is the log file for r169.

Original comment by Empirica...@gmail.com on 19 Jun 2011 at 9:51

Attachments:

• Tufte-Latex3.5.0MinimalExample.log

[GoogleCodeExporter]

Okay, that version was compiled with 3.5.2, but I'm not seeing any errors in 
the log file.

Original comment by godbyk@gmail.com on 19 Jun 2011 at 9:54

[GoogleCodeExporter]

Yes, I noticed that with the test file. So I went back to my complex document 
where all this began. And bidi did not cause a problem. But I couldn't test it 
further, because I got a new error, which I'm not sure is "pilot error" or a 
real bug. I will file that one separately.

Original comment by Empirica...@gmail.com on 19 Jun 2011 at 10:27

[GoogleCodeExporter]

@vafa: I neglected to thank you for the work you did on adapting tufte-latex to 
bidi. I haven't had the time yet to play with the experimental tufte-latex 
classes, but I will.

@Kevin: Since the problems I had originally were due to a bad path on my box, 
I'm curious as to whether you will incorporate vafa's modifications at some 
point.

Original comment by Empirica...@gmail.com on 20 Jun 2011 at 10:29

[GoogleCodeExporter]

@Kirk: Yes, I'm currently working to identify and extract the changes that Vafa 
made so they may be incorporated into the mainstream TL classes.

Original comment by godbyk@gmail.com on 20 Jun 2011 at 6:59