LaTeX.org

Great! Now I'm on a complex, critical mission and cannot change installation midway, but definitely will try XeLaTeX in the future. Thanks a lot.

shadgrind wrote:Have you tried adding inputencoding=utf8 in your \lstset command? Another thing to try is \usepackage[utf8x]{inputenc}, instead of \usepackage[utf8]{inputenc}, in the preamble.

Thanks. Yes I've tried. No luck:-(

Thanks. I checked listingsutf8 but from its documentation it seems it requires the source code to be able to be transformed into a one byte encoding. That sounds useless and silly. If the source code could be represented in one byte I would not be using UTF8 in the first place. Maybe they are ...

Not sure I understand the issue, but if it is the negative numbers taking two lines then changing the column specs thus seems to work:

\begin{tabularx}{1.25\textwidth}{C C C C C C C c c c c}%l*9{C}C}

Thanks. LaTeX input and contents of the source code file follows.


\documentclass[12pt,a4paper]{report}
\usepackage{ucs}
\usepackage[utf8]{inputenc}
\usepackage{listings}
\lstloadlanguages{Ada,C}
\usepackage{textgreek}

\begin{document}

\lstset{
language=Ada,
basicstyle={\rmfamily\scriptsize ...

Is there a bug reporting/discussing channel for this? Is this it?

Nice Ada source code, with Greek letter variables, UTF-8 encoded:
nice_ada_code.png
And here is how LaTeX typesets it, via package listings:
ada_code_latex.png
Note how line 49 is perfectly typeset, but the variables at the ...