Tag Info

New answers tagged

8

The example if fixed by braces around the problematic UTF-8 character inside the text for decorate: text={|\myshift| T{ự} do} Otherwise the text would be scanned byte by byte and disrupting the multi-byte UTF-8 character.


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 ...


0

I am on TeXStudio 2.8 and I see "System" as a default encoding. It's available in the "Editor" menu.


2

As David Carlisle said, it must work with pdflatex as well. Probably you editor uses utf8 by default, and the declared input encoding and the real one must coincide. So declareutf8 encoding and use the Latin Modern fonts (don't load fontenc in that case, since the lmodern package does it for you): \documentclass[12pt,twoside]{report} ...


1

A typical italian preamble may instead be \documentclass[a4paper]{article} \usepackage[T1]{fontenc} \usepackage[utf8]{inputenc} \usepackage[italian]{babel} than followed by any \begin{document} Hello \end{document} (first comment by Ian Thompson is definitely right). ...but I am sure that, by today, you've learnt better than me the difference between ...


4

Regarding the inputenc question Your example works without problem if I copy it in an utf8-document and declare the inputenc encoding accordingly as utf8. Ditto with ansinew. I can't really imagine how you could get the output in your image -- it can be created but imho not with the standard files. None of them would replace non-ascii chars with question ...


2

this is the kind of job I use to do sometimes. Well, there are few tools you can use for solve this. Maybe the best and automatic way is with pandoc, but sincerely the truth is that I have not tested enough and have not had a satisfactory experience with it yet. Another choice is to do what @Bernard suggests. Formerly I used AbiWord for open doc files and ...


1

Pandoc is a command-line tool that can covert docx files to LaTeX files. As for dealing with ellipses and quote marks, I think that the best way to handle those is using the search and replace function in your LaTeX editor.


6

Don't use utf8x; with an up-to-date TeX distribution it could show necessary only for its most obscure features (faking characters with images from the Web, for instance). The problem with Greek, which was probably the main reason for adopting utf8x instead of utf8, have since be solved and \documentclass{article} \usepackage[T1]{fontenc} ...


0

I modified my preamble, following many suggestions you made. Therefore, this is my new preamble and... it works nice : \documentclass[12pt,a4paper,footinclude=true,twoside,headinclude=true]{scrbook} \XeTeXinputencoding iso-8859-1 \usepackage{setspace} \usepackage{hyperref} \usepackage{epigraph} \usepackage{scrpage2} \usepackage{graphicx} %% For ...


1

Macs have used unicode fonts for years. I'd try to isolate your problem by setting up a simple document like the one below. Check that it compiles and displays the font(s) correctly, then incorporate the settings into your file(s). \documentclass{article} \usepackage{fontspec} \setmainfont[Ligatures=TeX]{Minion Pro} \begin{document} The quick brown fox ...


21

UTF8 and ASCII are byte for byte identical for characters in the ascii range so if you have a plain text file that is ascii encoded it is also UTF-8 encoded, and similarly if it is UTF-8 encoded but only has characters in the range x00 - x7F then they are encoded directly as themselves with bytes in the same range so are valid ASCII files.



Top 50 recent answers are included