New answers tagged

0

I have found the same problem but none of the above answers solved it. In the end, I found the code \'{\i} in my .bib file. This was supposed to yield í but was producing a crazy unicode char that broke compilation. This .bib file was exported from CiteULike based on a reference that I entered mannually or copy-&-pasted from somewhere else. I suppose ...


2

I tried on a Ubuntu system, first by creating a file named Préambule.tex and making a test file containing \documentclass{article} \begin{document} \input{\detokenize{Préambule.tex}} \end{document} I compiled with pdflatex and this is the terminal output This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014) (preloaded format=pdflatex) ...


2

Package listingsutf8 re-encodes the listing file from UTF-8 to the specified 8-bit encoding before passing it to listings. Since the encoding actually changes, package \inputencoding loads the new definitions for the active characters of the encoding from the .def file (latin1.def). These re-definitions has to be repeated each time the encoding is changed. ...


1

Listings(utf8) uses the standard interface \inputencoding{XXX} from the inputenc package to change the various encoding related definitions. \inputencoding loads the definitions from the XXX.def-file. While it is certainly possible to store the definitions in a macro instead of reloading them from the .def I don't think that inputenc should do it by default. ...


1

The following packages need to be added in the preamble of the document: \usepackage[T1]{fontenc} \usepackage[utf8]{inputenc} It is very important that all the pages of the document has UTF-8 encoding if not errors will happen when compiling.


2

Just to give the flavor, I define \itemizelist so that it splits the given input at | (or another character chosen at runtime) and adds \item in front of the various pieces. If the piece contains §, it is printed red. \documentclass{article} \usepackage{xparse,ifxetex} \usepackage{xcolor} \ifxetex \usepackage{fontspec} % <- xelatex/lualatex works ...


2

You are probably misunderstanding how the devanagari package works. I saved your example in a file gyalten.tex and typeset it with pdflatex (but removed \input dnmacs, which is foreign to LaTeX) and got which is possibly what you mean by daeva a a na a a m parai. If I change the name of the file to gyalten.dn as \documentclass[a4paper,11pt]{report} ...


1

At first, The document is made using Plain TeX. Furthermore. It was made using extremely rare bird - Plain TeX with russification. Finally, such document can't be appeared under BaKoMa TeX. Important: This document has no any relation to BaKoMa TeX.



Top 50 recent answers are included