Tag Info

New answers tagged

0

The original TeXcount is a Perl script, which would typically be called texcount.pl (or with version codes attached). To run this, you need Perl installed: ActivePerl and StrawberryPerl are two popular options on Windows. Apart from this, TeXcount requires no installation: the texcount.pl Perl script is entirely self-contained. As Ulrike Fisher has pointed ...


4

I guess I will answer my question, although it isn't solved as such - but at least I can use TeXcount on windows via what seems to me a very linuxy method! I installed ActivePerl I have MikTex installed which has texcount.exe as listed in the question I hunted around for texcount.pl but still haven't found it - which makes me wonder whether the executable ...


1

Upgrading Biber have implied that I must encode my report on UTF8. Thanks to @Bernard, @cfr, @Speravir, @moewe and @gns_ank.


0

In my case, the option -synctex=1 was in the command line. Yet it didn't work. What fixed it is deleting a file with the extension *.synctex. After that, syncing worked perfectly. Apparently, the file was a remnant of a previous latex compilation on a different machine.


1

As the problem actually seems linked to the fact that MiKTeX 64-bit doesn't include biber, which is a 32-bit application, you should take a look at the answers to this question. Don't forget to create a Local TeXMF root if you don't already have one.


1

Yes, I could connect outside TeX. After several more attempts to get it to run it turns out I forgot to declare the server. Using \texdbconnectionnet{MySql.Data.MySqlClient}{Server=localhost;Database=sakila; User=Manuel;Password=XXXXXX;} I could connect to the locally installed MySQL and run nlatexdb.


3

Your image shows the pdflatex command is set up to use pdftex.exe (plain tex) not pdflatex.exe (latex) so latex commands are not defined.


1

I was struggling with the same problem and the linked article helped me to solve the problem. Apparently the problem is that we use portable version. http://robertmarkbramprogrammer.blogspot.ch/2008/01/xxx-is-not-recognized-as-internal-or.html


2

The problem is simply that you try to compile with Plain TeX and you wrote a LaTeXdocument, that can be compiled with LaTeX (Shift+Ctrl+L) or pdfLaTeX (no shortcut, but you have an icon in the toolbar that lets you choose the compiler: You also can use LaTeXify or pdfLaTeXify to automatically compile the right number of times if your document has ...


2

The original command is mthelp, as noted by Torbjørn, to be used on command prompt. Later texdoc was introduced as alias for mthelp, so Harish’s hint is valid, as well. Execute mthelp -? (or with texdoc) for command line options (Note, that MiKTeX’s texdoc does not understand all command line options from TeX Live’s texdoc and vice versa.) To quote Ulrike ...


3

A minimal example producing the wrong behavior is \documentclass[twocolumn,10pt]{asme2e} \usepackage[english]{babel} \begin{document} \cite{xyz,xxx} \end{document} with which the .aux file show \citation{0.0pt} The erroneous behavior is due to the fact that asme2e.cls defines \@citex in a way that pleases it, while babel redefines the macro in an ...


7

Update: The following is now historical. The bug was fixed with MiKTeX update from 2014-04-10, cf. regarding entry in MiKTeX Bug Tracker: Map file missing for "esvect". There is a very simple reason: MiKTeX installs all of esvect, except esvect.map, that is required to use the type 1 versions of the fonts. It actually exists in esvect-src.tar.bz2, but the ...


-1

In my case, it is because I installed the 32 bit version, while my Windows is a 64 bit system. After reinstalling the correct version of MiKTeX, everything works fine.


2

According to the documentation, the inputenc package allows the user to specify an input encoding (for example, ASCII, ISO Latin-1 or Macintosh) by saying: \usepackage[encoding name]{inputenc} The choices of encoding name are listed on pages 1-2 of the manual.


1

I've had the same problem. I've found two ways to make it work: Solution 1. Add miktex portable to the environment variable PATH. Even if you don't have administrative privileges on the machine, you can usually set the variable just for your account. I wouldn't use it while keeping miktex on a USB drive but if you copied it onto the disk it should be ...


1

For ease of distribution, TeX can be downloaded in its entirety as an archived bundle. This archive is stored in a temporary location before being extracted to a location of your choice on your local drive. Once installation is complete, you can safely remove this temporary download.


2

Everything works fine here. I just made an update and installed new packages. Some more information: 178.77.68.21 - Reverse IP Lookup on DomainTools shows you, that this IP is used amongst others for http://miktex.org/. The reason is that in these cases, when you have package installation from a random or from the “nearest” repository selected, the page ...


2

I was faced with the same challenge a while ago. In my case, I only needed to compile documents of a fixed format and I thus only needed a small subset of the TeX distribution. To extract this subset i wrote a script, which Sets up a "watch" on the TeX distribution (I used FileSystemAuditRules). Compiles all relevant file templates using the monitored TeX ...


2

As Speravir mentioned in a comment to this answer, manually adding files to the MiKTeX directory is not a proper solution to the problem. According to this answer of his, it should be avoided for security reasons. A more secure solution is the one offered here by Bernard, reprinted here: Download miktex-biber-bin.tar.lzma from a CTAN repository (direct ...


2

Try adding the .tex extension back on to the file. I'm not sure why arXiv would remove it, but many editors will assume that it's there when running compile sequences. To see what I mean, compare the compilation for pdfLaTeX and BibTeX: $ pdflatex myfile.tex $ bibtex myfile Note that bibtex doesn't need the file extension since it also looks at the ...


2

This is more of a comment, but it turned out to be too long. If I'm imagining this correctly in my head, this is the sequence of events: You create a LaTeX-formatted file in texstudio and save it as foo.tex. You compile this file from within TeXstudio. This in turn calls pdflatex foo.tex. The pdftex engine provided by MiKTeX begins compiling the ...


3

Try \usepackage{ifpdf} \ifpdf \usepackage{tikz} \fi Remark: Why the new pgf version breaks in auto-pst-pdf hasn't been analysed yet. So this is more a work-around then a solution.


2

Find fi-logo.mf (https://github.com/liskin/fithesis), copy it to fonts/source and update the FNDB.



Top 50 recent answers are included