Tag Info

New answers tagged

1

It may be unrelated, but I had problems with babel when I initially loaded the acro package. I solved them (perhaps fortuitously) by loading acro before babel. \documentclass[a4paper,12pt]{scrreprt} % KOMA report class \usepackage{acro} % Define and list acronyms (load before {babel}) \usepackage[greek, UKenglish]{babel} % Provides language support ...


1

It's a bug in cnltx-base.sty. The problem is on line 179 of cnltx-base.sty 179 \edef\cnltx@tmpa{\catcode`\%=\the\catcode`\% \catcode`\&=\the\catcode`\&} where the code is not sufficiently defensive; it should be 179 \edef\cnltx@tmpa{\catcode`\noexpand\%=\the\catcode`\% \catcode`\noexpand\&=\the\catcode`\& } so a possible change of ...


1

You should not import the inputenc package multiple times (and that goes for all packages), even with different options. In your case, you should use the inputenc package with the utf8x option. Why, in your case, chosing utf8x over utf8, is explained in this document (footnote of the page 32).


1

Using the scaled rule example the error is avoided if I switch to english (ie left to right) just locally. If wrapping your \includegraphics in {\selectlanguage{english}..} works then there is at least a workaround for the bug. If not, I'll delete this answer. I get no error from: \documentclass[10pt]{article} \usepackage{graphics} ...


1

I don't know if this is the best solution, but I simply use \selectlanguage{spanish} and \selectlanguage{english} to switch between English and Spanish as needed.


2

The problem is quite subtle and lipsum is not really involved. Analysis of the problem The mparhack package makes some annotations in the .aux files, using \newcommand*\mph@outputpage@hook{% \bgroup \advance\c@page\m@ne \immediate\write\@auxout{% \string\mph@setcol{ii:\thepage}{\string\mph@nr}% }% \egroup } and the problem ...


1

Ok, I got something, but I'm not sure it's correct - so more erudite responses will be appreciated. By using package {trace}, I compared the trace outputs for the correct [english] and the problematic [greek,english] options for babel. Both variants end up in this stack trace: \mph@outputpage@hook ->\bgroup \advance \c@page \m@ne \immediate \write ...


4

Giving the option globally can be a handy thing. The class file passes the options further to packages. You mentioned the language, let's have a look at it. Internally, siunitx loads package translator (part of the beamer bundle). translator can see the global option for the language and react by using the right dictionary. Another famous instance where ...


3

The error is in loading babel after fontspec, which sets the document encoding to EU1 (with XeLaTeX) or EU2 (with LuaLaTeX). When this fact is known, babel is able to load the Greek language adapting it for those engines, without doing the tricks it has to do with the LGR encoding for pdflatex. This might be improved in babel, but the remedy is very simple: ...


1

I was just trying these examples with a fresh TexLive 2014; I had been using the \let\l@ENGLISH\l@english fix for a while in TexLive 2011 with success, but now with 2014 the same document gave me the dreaded warning: Package babel Warning: You haven't loaded the language ENGLISH yet (babel) I'll proceed, but expect unexpected results. ...


10

There is some mistake in the tests for input encodings in magyar.ldf. You get the same error message if you choose latin2 is the encoding. The relevant part of magyar.ldf is \def\magyar@sugg@ie@lowb#1{\@latex@warning@no@line{Please use \string\usepackage[latin2]{inputenc} with\MessageBreak \string\usepackage[#1]{babel}}}% %** @param #1 ...


2

It does: > \filedate=macro: ->2012/08/20. l.10 \show\filedate ? > \fileversion=macro: ->v3.3p. l.11 \show\fileversion ? > \fileinfo=macro: ->English support from the babel system. l.12 \show\fileinfo ? generated from \documentclass[a4paper]{book} \usepackage[T1]{fontenc} \usepackage[english]{babel} \usepackage{doc} ...


0

Ok, I think I got it. The thing is - what I usually do if I install a new TexLive version, I install the minimal packages, and then try to tex my docs and add packages until they compile - so obviously there was some missing stuff here. Here is a log of what I did to get it properly working (without hacks). As pointed out in comments: the first key thing is ...


1

From my comment to a proper answer. :) This looks like a missing dependency in the TeX installation. Running $ sudo apt-get install texlive-lang-portuguese in the terminal (or installing the very same package via Software Center) will install the Portuguese support for babel and hopefully the code will work. :) Also, the format of the document should ...


1

I would consider that a bug. Please report this to the maintainers of tikz-cd and the babel library. In the meanwhile, this hack works for you: % arara: pdflatex \documentclass{article} \usepackage{tikz-cd} \usepackage[spanish]{babel} \usetikzlibrary{babel} \begin{document} \[ \shorthandoff{"} \begin{tikzcd} X\arrow[mapsto, ...


2

The behavior is readily explained by looking at Cuadro 2 in the documentation of babel-spanish: "a "A "o "O Ordinals: 1.a 1.A 1.o 1.O This means that an input such as 1"a will be rendered as 1.a but any appearance of "a will become .a (and similarly for "A, "o and "O). You can globally disable this by using the es-noshorthands option ...


3

In babel use also option es-noshorthand. Your minimal example will look like: \documentclass{article} \usepackage[spanish,es-noshorthands]{babel} \begin{document} \texttt{"avg"} \texttt{"a} \verb|"a| \end{document} And the output is: More of this is here.


3

The file dt-welsh.def seems to be at fault, for it does \DeclareRobustCommand*\datewelsh{% \renewcommand{\formatdate}[3]{% \@day=##1\relax\@month=##2\relax\@year=##3\relax \ifnum\@day=1\relax 1\/$^{\mathrm{a\tilde{n}}}$\else \number\@day\fi \space a\space viz\space \monthnamewelsh[\@month]\space\number\@year}}% If I redefine \datewelsh in the document ...



Top 50 recent answers are included