New answers tagged texlive
3
With the current version of mdframed the behaviour is nearly equal. The shown distance of the older version was a bug where I didn't regard parskip at the beginning of the environment. The default behaviour of mdframed ought be skipabove=skipbelow=0pt whereby by using parskip the option was skipabove=\parskip
If you use the current version you will get the ...
3
It looks like you are using a distribution which either does not properly activate installed map files.
First, your invocation of updmap is wrong. You cannot call updmap with the full path of a map file, please see the man page of updmap --help for correct syntax. The normal solution would be to call
updmap-sys --enable Map sansmathaccent.map
which ...
4
You don't say from what TeX distribution you upgraded. The breqn package has undergone big changes, one of which, unfortunately, makes it not to cooperate well with Xy-pic.
You can return to the normal behavior with some trick:
\documentclass[10pt]{letter}
\usepackage{amsmath}
\usepackage{amsthm}
\usepackage{amsfonts}
\usepackage{amssymb}
...
0
That has happened with me for some packages before, but I run on linux. That is, I can get around this by cancelling that package from installing and installer will move to the next package.
Is there a way to cancel one package without ending the whole operation in Windows?
If not, you could try cancelling and re-starting. The installer should pick up ...
5
Viewing already installed documentation
Assuming you use GNU/Linux, you can view the documentation by typing
texdoc <package name>
into your terminal (e.g. texdoc amsmath).
Viewing online documentation
Go to http://texdoc.net/ and enter the package name in the input field. Choose the documentation that best fits your needs.
Regrading your ...
2
I cannot reproduce the problem (pdflatex, latex + dvips + ps2pdf, xelatex):
\listfiles
\documentclass{article}
\usepackage{wrapfig}
\usepackage[colorlinks]{hyperref}
\usepackage[demo]{graphicx}
\usepackage[english]{babel}
\usepackage{blindtext}
\begin{document}
\begin{equation}E=mc^2\label{ref}\end{equation}
\begin{wrapfigure}{R}{0.5\textwidth}
...
2
find `kpsewhich --var-value TEXMFDIST` -name *.cls
and if you have also a local tree:
find `kpsewhich --var-value TEXMFLOCAL` -name *.cls
5
TeX Live maintains some text files where all packages/classes etc. are listed. The files are called ls-R and there's one for each main tree. In order to find all installed document classes in your main path you can do the following command:
grep "\.cls" `kpsewhich --var-value TEXMFDIST`/ls-R > $HOME/allcls.txt
After this process you have a file ...
0
I use exactly the same preamble than yours, but I think you must have your files in a directory with you theme name for each .sty
/usr/local/texlive/2012/texmf-dist/tex/latex/beamer/themes/color/Uni/beamercolorUni.sty
/usr/local/texlive/2012/texmf-dist/tex/latex/beamer/themes/outer/Uni/beamerouterUni.sty
...
8
I have to disagree and advise with a few points:
Debian/wheezy contains TeX Live 2012, the latest released version of TeX Live
TeX Live 2013 prerelease will soon be uploaded the Debian/sid (maybe today if I manage it)
linking apt-get with tlmgr update as you suggested is a very bad idea, since by now tlmgr does not return proper error codes, which means ...
0
Thanks @Tobias Schula. I just used the wrong Font path for the Adobefonts. After I repeat the the installation with the right path /opt/Adobe/Reader9/Resource/Font/ everything worked fine for me again.
1
After reading all the helpful suggestions,the first thing I did was uninstall all the "texlive" ports. I googled "how to uninstall ports in Macports" and found two good websites.
The first one is actual guide to "Macports": http://guide.macports.org/
The second site, which really solved my questions was this one: ...
0
As Evince can open pdf.gz file, I just created a texmf.cnf file in $HOME/texmf/texdoc containing this line:
viewer_pdf = (evince %s) &
and the command texdoc pgf worked(on ubuntu 13.04). Hope that's help.
0
To update just one package (mdframed in your case) of the TeX Live, use the following command:
tlmgr update mdframed
5
In the distribution documentation is separated from run time files, but it isn't essential that you do that, so if in doubt (or in a hurry) just leave all the files together in a directory in your input path.
Whether you need to run texhash afterwards depends where you put them. Some directories are marked as being hashed so if the new files are not hashed ...
0
To locate binaries open the shell and type
$ whence latex
3
First of all, you cannot see LaTeX like other fancy applications. In other words LaTeX installation does not include GUI.
If LaTeX is installed successfully, then you can simply call it from your terminal. To check if it is really installed, type this in the terminal:
$ latex -v
This should output the version information of installed LaTeX.
If that is ...
1
The following works, but is a poor hack. The reason is that what we "really" want to do is get TeX to use the Culmus fonts whenever possible (or maybe always), rather than the older Hebrew fonts.
It is based on the pertinent instructions in the babel package documentation, which @MarioSE's answer refers to, and is adapted to TeXLive 2012 (it had last been ...
1
If you go to the babel package's CTAN site (available here) you'll notice there are a couple of important pdfs:
1) The package documentation 1 & 2
2) The installing support for hebrew
Please refer to Chapter 63 of the package documentation for specific information regarding the Hebrew language, and to Chapter 64 for information regarding ...
2
On writing this question, I found a definitive answer in the TEX (Live) on Debian guide on tug.
This part explains the best option and why:
The central configuration file /etc/texmf/texmf. cnf is special, as it
defines all search paths for (almost) all programs in the TEX world.
All the paths mentioned above are defined in it, but other behaviour
...
7
It is possible to add documentation files to already installed packages issuing the following commands in any terminal (both commands may need root privileges depending on how you installed Tex Live in the first place and the second is UNIX only):
tlmgr option docfiles 1
sets the docfiles option to 1, i.e. from now on tlmgr will download and install ...
8
The Web page you refer (Testing the installation) is indeed not very informative about LuaTeX.
It's not really possible to test fonts with opentype-info.tex by two reasons:
the file doesn't enable the font loading mechanism for LuaTeX;
it has specific XeTeX commands that LuaTeX can't understand.
A small test file might be
\def\myfontname{Latin Modern ...
5
you mix a lot of things: first things first: What do you think is missing in TL2012 that was available in TL2011 or before, and will be available in TL2013?
My guess there is nothing like this.
Now for the rest;
1) older TL releases
Yes, we do not keep track, there is not enough capacity to keep it around.
2) TL2012
You can still install it with the ...
3
You can always install the packages you need in ~/texmf and they will have priority over the packages of texlive. You are not stuck. Just keep texlive 2012 and install what you need localy in you Home-directory. There have been descriptions for sophisticated cases, see here e.g.
1
Best bet (unless you really know what you are doing, in which case you won't ask this here...) is to install whatever TeX the Linux distribution ships. The distribution will take care of updating and keeping it nicely integrated with the other packages.
4
use rsync, eg:
rsync -av --delete --exclude="mactex*" ftp.math.utah.edu::texlive/tlpretest /tmp/tlpretest
then run sudo /tmp/tlpretest/install-tl
After installing updates are possible with:
sudo tlmgr --all --self -repository=http://www.math.utah.edu/pub/texlive/tlpretest/ update
But remeber that you have to put the 2013 binary path into your PATH ...
1
Try this kind of folder structure. I had the same error but overcome by using like this.
\chapter{Introduction}
\ifpdf
\graphicspath{{Introduction/IntroductionFigs/PNG/}{Introduction/IntroductionFigs/PDF/}{Introduction/IntroductionFigs/}}
\else
\graphicspath{{Introduction/IntroductionFigs/EPS/}{Introduction/IntroductionFigs/}}
\fi
1
Not a real answer, just an attempt to narrow down the problem. I can't reproduce the symptoms with the following Python code (version 2.7.2 on MacOS X):
utfcheck.py:
#!/usr/bin/python
problemString = u'educator'+unichr(39)+u's and '+unichr(0xc3)
documentTemplate=r"""\documentclass{article}
\usepackage[utf8]{inputenc}
\begin{document}
%s
\end{document}
...
0
For TeXstudio, the answer is go to Options/Configure TeXstudio/Commands/pdflatex
"/bin/texliveonfly" %.tex
0
This actually wasn't that hard (just non-obvious). I was trying to select one of the texdists from /Library/TeX/Distributions (makes sense to me!), but the correct place to look is in /Library/TeX/Root. Then, you can switch the TeX distro using the System Panel, and TeX Live Utility will work properly.
I still have no idea where TeX Live Utility settings ...
4
https://lists.dante.de/pipermail/ctan-ann/2013-April/date.html lists all updates and new packages for April on CTAN. If there is no license problem then all new packages will also be on TeXLive 2013
9
Let's say you had a more specific question, like: "what new LaTeX packages are there in TeX Live 2013?"
After TL2013 comes out and you install it side by side to TL2012, assuming you've not changed the default install directory, you could do something like this (UNIX systems only):
ls /usr/local/texlive/2012/texmf-dist/tex/latex/ > 2012list & ls ...
3
The TeX Live user guide contains a section on the highlights that changed from one version to the next.
However it does not show which packages have been updated from the last version.
3
This depends on which backend you are using.
If the backend is bibtex then no spaces are allowed in the filename (and there are other restrictions such as the length of the name must not be more than 40 characters). LaTeX will happily write the file name to the .aux file, but bibtex will complain when it reads the resulting \bibdata command.
If you use ...
9
You can make the text a bit more heavy by using Heiko's great pdfrender package. Just play with the LineWidth parameter.
\documentclass[paper=a4]{scrartcl}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{pdfrender,xcolor}
\begin{document}
\pdfrender{StrokeColor=black,TextRenderingMode=2,LineWidth=0.2pt}
A wonderful serenity has taken ...
5
It appears that this issue is independent of the compiler, and it's not possible to "fine-tune" the .pdf output without changing the font package used.
I answered pretty much the same question a while ago. It is possible to produce what I'd call ›faux ink gain‹, using the method I described in that answer, but it's going to produce unpredictable results ...
5
This requires a bit of debugging... Do you have a /etc/fonts/fonts.conf that references these fonts? It might be quite important as the code of luaotfload relies on this file. If it doesn't work on your system, it might be because of an update in fontconfig files which makes luaotfload code needing an update... If you want, I would be ready to debug it if ...
9
While in MiKTeX an installation process is automatically triggered if you have, say, \usepackage{beamer} in a document preamble without the corresponding package installed, there is no such feature on TeX Live.
The last statement is not true actually, as pointed out by wasteofspace in the comments there is the texliveonfly package that implements the on ...
11
The environment variable OSFONTDIR will override fontconfig information. Specifying directories with a double trailing slash means "please recurse into subdirectories". For example:
OSFONTDIR=${HOME}/.fonts:/usr/share/fonts//:/usr/share/texmf/fonts//
EDIT: There seems to be an issue with Debian (and thus Ubuntu) texlive packaging, which provides a default ...
9
put it into /usr/local/share/fonts/ or alternatively into your home directory into .fonts/.
Run mkluatexfontdb -v | grep "local/share" to see what's going on.
Top 50 recent answers are included
