On Mar 30, 2012 1:13 AM, "Matt Bellis" <matthew...@gmail.com> wrote:
>
> Hi all,
>
> I've been using tufte-latex for my class notes with great success. A recent upgrade under Debian unstable (texlive-binaries) has caused tufte-latex to stop building.
>
> If I do a fresh clone of the git repository and try ``pdflatex sample-handout", I get this....
>
> --- snip ---
>
> Package ifplatform Warning:
> shell escape is disabled, so I can only detect \ifwindows.
>
> ) (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
> ! I can't find file `"|kpsewhich -var-value=max_print_line"'.
> <to be read again>
> \relax
> l.57 ...kpsewhich -var-value=max_print_line"\relax
>
It looks like your new binaries have write18 disabled by default. Try adding -shell-escape to the pdflatex (or xelatex) call.
-Boris
On Fri, Mar 30, 2012 at 12:13 AM, Matt Bellis <matthew...@gmail.com> wrote:
> I've been using tufte-latex for my class notes with great success. A
> recent upgrade under Debian unstable (texlive-binaries) has caused
> tufte-latex to stop building.
>
> If I do a fresh clone of the git repository and try
> ``pdflatex sample-handout", I get this....
>
> --- snip ---
>
> Package ifplatform Warning:
> shell escape is disabled, so I can only detect \ifwindows.
>
> ) (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
> ! I can't find file `"|kpsewhich -var-value=max_print_line"'.
> <to be read again>
> \relax
> l.57 ...kpsewhich -var-value=max_print_line"\relax
>
> (Press Enter to retry, or Control-D to exit)
> Please type another input file name:
>
> --- snip ---
I haven't see this error before. If you're not running pdflatex when
shell-escape enabled, then it shouldn't be trying to run the kpsewhich
command.
I'm wondering if this is caused by the older Debian texlive-*
packages. I typically recommend that people install TeX Live from
upstream: http://kevin.godby.org/2012/02/13/installing-tex-live-in-ubuntu/
The Debian texlive packages (last I checked) are for TeX Live 2009.
If you're running xelatex, you can use any font on your system
<http://tex.stackexchange.com/a/18968/80>. If you want to still use
Palatino, etc., then they should work okay -- they just won't be
loaded automatically. Add the following to your preamble to load
them:
\usepackage[osf,sc]{mathpazo}
\usepackage[scaled=0.90]{helvet}
\usepackage[scaled=0.85]{beramono}
\usepackage[T1]{fontenc}
\usepackage{textcomp}
If you continue to have problems or have any further questions, please
let me know.
Thanks!
--Kevin Godby
It looks like your new binaries have write18 disabled by default. Try adding -shell-escape to the pdflatex (or xelatex) call.
1. -shell-escape allows tex to call external programs.
2. what do you get if you call this command:
kpsewhich -var-value=max_print_line
-B
I'm wondering if this is caused by the older Debian texlive-*
packages. I typically recommend that people install TeX Live from
upstream: http://kevin.godby.org/2012/02/13/installing-tex-live-in-ubuntu/
The Debian texlive packages (last I checked) are for TeX Live 2009.
If you're running xelatex, you can use any font on your system
<http://tex.stackexchange.com/a/18968/80>. If you want to still use
Palatino, etc., then they should work okay -- they just won't be
loaded automatically. Add the following to your preamble to load
them:
\usepackage[osf,sc]{mathpazo}
\usepackage[scaled=0.90]{helvet}
\usepackage[scaled=0.85]{beramono}
\usepackage[T1]{fontenc}
\usepackage{textcomp}
2. what do you get if you call this command:
kpsewhich -var-value=max_print_line
Look, your error log says this command gives an error, but when you call it manually, it works fine. Looks like a problem with PATH...
Can you add \listfiles in the beginning of your file and send the full log?
-B
On Fri, Mar 30, 2012 at 12:42 AM, Matt Bellis <matthew...@gmail.com> wrote:
> I'm running Debian unstable (sometimes, that's a whole other set of
> problems) and the texlive is from 2011.
>
> http://packages.debian.org/en/sid/texlive
Ah, okay. I haven't tried these packages yet.
> Great! Trying this now....which led to an interesting discovery. beramono
> is not on my laptop....nor is it in the Debian unstable repository, though
> it is still in testing and unstable. That's a question for the Debian folks,
> however.
>
> If I comment out the beramono line, I get this....
>
> ! LaTeX Error: Command \nobreakspace unavailable in encoding T1.
>
> Does that look familiar? Or is that an artifact of the commented
> beramono font?
It's not 'caused by the missing beramono package. It's caused by an
interaction between the T1 font-encoding and the fontspec package
(which Tufte-LaTeX loads automatically when you compile with XeLaTeX).
Try leaving out the fontenc and textcomp packages and see if
everything works okay.
--Kevin
Look, your error log says this command gives an error, but when you call it manually, it works fine. Looks like a problem with PATH...
Can you add \listfiles in the beginning of your file and send the full log?
It's not 'caused by the missing beramono package. It's caused by an
interaction between the T1 font-encoding and the fontspec package
(which Tufte-LaTeX loads automatically when you compile with XeLaTeX).
Try leaving out the fontenc and textcomp packages and see if
everything works okay.
>> Sure thing. Here's the sample-handout.log after adding \listfiles
Ok, I see you use the tufte files from the local directory. I wonder
what happens if you move them from it and try the system-wide
tufte-handout.cls?
-B
If you're compiling under XeLaTeX, try the following to use fonts
similar to those we use under pdfLaTeX:
% Use fonts similar to Palatino and Bera Mono
\setmainfont[Mapping=tex-text,Numbers=OldStyle]{TeX Gyre Pagella}%
provided with TeX Live
% TODO \setsansfont[Mapping=tex-text,Numbers=OldStyle,Scale=MatchLowercase]{...}
\setmonofont[Mapping=tex-text,Scale=MatchLowercase]{DejaVu Sans
Mono}% freely available from http://dejavu-fonts.org/
% Sets up the letterspacing -- spacing values may need to be adjusted
\renewcommand\allcapsspacing[1]{{\addfontfeature{LetterSpace=15}#1}}
\renewcommand\smallcapsspacing[1]{{\addfontfeature{LetterSpace=10}#1}}
You can set a sans serif font as well. If you're on a Mac, then Gill
Sans is available (and is what Tufte frequently uses). (The default
sans serif font used by the Tufte-LaTeX classes with pdfLaTeX is
Helvetica, but I think it's a poor pairing with Palatino.)
--Kevin