MiKTeX and proTeXt ⇒ fontspec package problem with XeLaTeX in MiKTeX 2.9

[eiterorm]

Hi!
I'm not certain if this is the correct place to post this, but please help me move this post if it belongs elsewhere.

The following code did compile with XeLaTeX earlier, but it won't compile (in TeXnicCenter) after I upgraded to MiKTeX 2.9.

Code: Select all

\documentclass[10pt, a4paper]{article}
\usepackage[T1]{fontenc}
\usepackage{lmodern}
\usepackage{fontspec}
\usepackage{xunicode}
\setmainfont{Cambria}
\pagestyle{empty}

\begin{document}
Hell\char"03A9 world!
\end{document}

I don't know what has changed, but I get the following messages after compiling:

("C:\Program Files\MiKTeX 2.9\tex\latex\euenc\eu11mr.fd")xelatex.exe: Windows API error 1113: No mapping for the Unicode character exists in the target multi-byte code page.

I couldn't open file name 'D:\Documents\test\test.aux'

Couldn't find input index file D:\Documents\test\test nor D:\Documents\test\test.idx.

Usage: C:\Program Files\MiKTeX 2.9\miktex\bin\makeindex.exe [-ilqrcgLT] [-s sty] [-o ind] [-t log] [-p num] [idx0 idx1 ...]

D:/Documents/test/test.dvi: No such file or directory

This is dvips(k) 5.99 Copyright 2010 Radical Eye Software (http://www.radicaleye.com)

C:\Program Files\MiKTeX 2.9\miktex\bin\dvips.exe: DVI file can't be opened:


LaTeX-Result: 0 Error(s), 0 Warning(s), 0 Bad Box(es), 0 Page(s)

Does anyone know what's wrong? Answers are much appreciated.


EDIT:

As written below, it appears the '\usepackage{fontspec}' commmand is what causes the compilation to fail, and the essential build log message is

xelatex.exe: Windows API error 1113: No mapping for the Unicode character exists in the target multi-byte code page.

Thanks
eiterorm

[frabjous]

Out of curiosity can you compile:

Code: Select all

\documentclass{article}
\begin{document}
Hello world
\end{document}

with XeLaTeX on MikTeX?

What about

Code: Select all

\documentclass{article}
\usepackage[T1]{fontenc}
\usepackage{lmodern}
\begin{document}
Hello world
\end{document}

on either pdflatex or xelatex?

[eiterorm]

Those examples do indeed compile with both xelatex and pdflatex.

After doing some further testing, it appears the '\usepackage{fontspec}' commmand is what causes the compilation to fail, and the essential build log message is

xelatex.exe: Windows API error 1113: No mapping for the Unicode character exists in the target multi-byte code page.

However, I did compile a document with this very same preamble before upgrading to MiKTeX 2.9. And the fontspec package is rather essential to my document.

Any ideas what might be wrong?

[eiterorm]

After spending quite some time searching the web for answers to this, it seemed the solution to many problems slightly similar to this one was to reinstall MiKTeX 2.9 and all packages. I thought I'd give this a try, but it did not help. I have also triple checked that all my packages are up to date.

So I the problem remains unsolved, and the build log is the same.

[meho_r]

I'm not sure what version of fontspec came with MikTeX 2.8, but if it came with a version prior to v.2, maybe that is the problematic bit. If I remember correctly, there were some changes introduced with v.2, but I'm not sure what those were. I suggest, for starters, that you try compiling your document (or a simple example with fontspec loaded) using another editor or from Command Line, just to make sure it is not TXC-related issue. Or, you might ask on {TeX} SE, since Will, the author of fontspec, is often there.

[eiterorm]

The problem is either related to fontspec, MiKTeX or Windows, or a combination of the three. I've tried to compile the document with TeXWorks, and I get the same Windows API error.

Thanks for the tip about the other forum. I'll try there as well.