# Tag Info

15

File extensions are mainly a naming convention. Source code in almost all programming languages is plain text, and there is no technical difference between a file named .txt or .tex or .asdasdasd or whatever.

9

As mentioned in the comments, .tex files are just plain-text files, so they do not have "hidden metadata". If you inspect it with any text editor as Notepad, TeXnicCenter etc... you will see the contents byte per byte (encoding issues apart, which are off-topic it would seem). If your concern is how safe it is to run latex (or variants) on the file, the ...

6

A TeX distribution consists of much more than just LaTeX. E.g., there are many additional TeX formats out there, e.g., PlainTeX, XeLaTeX, LuaLaTeX, and there are auxiliary programs such as bibtex, biber, makeindex and xindy. A well-configured front-end, in addition to serving as a text editor, makes it easy to access these formats and auxiliary programs. ...

5

To expand a bit on the other answers, a .texfile is the same file format as .txt from the operating system's perspective. Both are plain text files. A plain text file contains nothing but series of character-codes, which a text editor tells the computer to display as letters according to the codes. There are different encodings, with UTF-8 being now used ...

5

Explaining what text editor and TeX engine are might help here. Text editor is a program to write an input file. TeX engine is a program to typeset your input file to produce either PDF (usually), DVI, etc. There are many text editor freely available for LaTeX: TeXnicCenter etc Each editor give various features such as code folding, ...

5

There's two problems here: 1st: the reason compilation fails is due to wrong sequence of brackets in ({LDA)} in the abstract field of hastie_discriminant_1996. 2nd: the warnings with Biber reported the following issues are due to biber not recognising your page fields as ranges as they should be, according to the biblatex documentation: Range fields ...

4

To use LaTeX, you need an editor to write, texlive or miktex to compile and a PDF Viewer to display the result. If you produce a dvi instead of a PDF, you need a dvi viewer, of course. In comparison, Word offers "all in one". "All in one" has a huge disadvantage: If the software has to display the result of what you type ("what you see is what you get") ...

3

As you can see on your screeshot you are using the LaTeX engine. Instead of a pdf, this engine provides a dvi-file. You should use PDFLaTeX instead of LaTeX (choose from the dropdown list), which should output a proper pdf. See screenshot below:

3

As I mentioned in my comment, steinmetz loads pict2e, and this package needs to load the correct driver. The loading of the driver is done in pict2e.cfg which on miktex is from 2005 (completly outdated) and so doesn't load the suitable driver for xetex but the dvips driver instead. In Tex Live there is no problem. Make a bug report on the miktex site. A ...

3

For a simple text, really you do not need two programs, only one compiler as pdflatex. You can make a file test.pdf with the word "Test" only with this command, at least in TeX Live 2014 with Linux: pdflatex -jobname test \\documentclass{article} \\begin{document}Test \\end{document} Well, the problem is when you want to write a PDF with some more ...

3

I had the same problem with a project consisting of lots of separate .tex source files. I found that BibTeX is not called when I use \include{other_file} in my main file where other_file has new/updated citations. However, if I change this to \input{other_file} bibtex is called correctly. I also noticed in the latex-suite documentation (line 1469 in my ...

3

No, you can't. The printout of file names is too deep inside TeX to be changed by higher level macros. The only way that would suppress the printout of file names is to create a pre-compiled "precompiled-preamble". This process is the same as used for generating the latex command from tex. Command latex is nothing but bare bones tex unto which the LaTeX ...

2

It is possible to include a bbl created with bibtex instead to biber. Thus use the backend=bibtex option, run bibtex on your system, and then upload the bbl file to arXiv. The second option is to upload all style files required by a recent version of biblatex (but you have to include too many files) as well as the bbl file.

2

It seems that your installation is a little bit faulty. In your listfile part is the following missing: scrpage2.sty 2013/12/19 v3.12 KOMA-Script package (page head and foot) Without package scrpage2 the command \lohead can't work. That's why you get your error message. Please check your installation. You can try to use the package manager to ...

2

I suspect your compiler is latex rather than pdflatex. If that's the case, you will find a .dvi file in the folder with your document. To change the default compiler, if this is TeXstudio, try Options -> Configure -> Build and set the Default Compiler to PdfLaTeX . If it's another environment, find out how to set the default compiler there to pdflatex. ...

1

If you are using TexStudio, there is a simple way to do it. In Preferences/Commands, you can add to the BibTeX line build/%.aux if your output folder for PdfLaTeX is named build. This is working for me with my_bibliography.bib in the same folder as my LaTeX files and using the following at the end of my LaTeX file. \bibliographystyle{plain} ...

1

Just because LaTeX produces a reasonable-looking PDF doesn't mean it has compiled correctly. For example, the following document contains an error: \documentclass{article} \begin{document} Subscripts like x_i need to be in math mode. \end{document} But if you run the command pdflatex -interaction nonstopmode test_document.tex, which I assume LaTeXian ...

1

Once in a while I negotiate a contract with somebody: Emacs on the screen of my laptop, Okular displaying the PDF on the LDC projector. To get a change of the *tex file displayed quickly, I make Emacs save the *.tex file 1.5 s after I stop typing. Usually I create a format and run latexmk in the background. This makes the compilation start quickly. To ...

1

There are instructions on how to do this here. For master file called my_master.tex, create a file in either the same directory as your \input{}ed file or a directory anywhere above that one called: my_master.tex.latexmain Now typing <leader>ll will compile the master document of whichever .tex file you currently have on screen.

Only top voted, non community-wiki answers of a minimum length are eligible