gpoore / minted

minted is a LaTeX package that provides syntax highlighting using the Pygments library. Highlighted source code can be customized using fancyvrb.
1.75k stars 126 forks source link

whitespace in minted environment produces "^^I" #9

Closed Cylox closed 11 years ago

Cylox commented 11 years ago

Using minted 1.7 with pygmentize 1.6: This code: \begin{minted}[fontsize=\footnotesize]{xml} <Window x:Class="_2200DatabaseExport.MainWindow" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:vm="clr-namespace:_2200DatabaseExport.ViewModel" xmlns:v="clr-namespace:_2200DatabaseExport.View" Title="2200 Database Export" Width="800" Height="Auto">

</Window>
\end{minted}

will produce the following output: whitespacebug

I'm using windows 7 with miktex 2.9. I also have another machine which has minted 1.6 and pygmentize 1.5 installed. The output there is absolutely fine.

Cylox commented 11 years ago

Unfortunately the auto-formatting feature here removed the leading white space in my latex code, but every tab in the minted environment gets converted into "^^I" as seen in the picture.

UPDATE: Downgraded to minted 1.6 and it works like a charm: orig

gpoore commented 11 years ago

Are you using XeLaTeX? It looks like you are using XeLaTeX without the -8bit command-line option. If that option isn't used, tabs written to an external file become ^^I; more here. Let me know if it that's the case; otherwise please let me know exactly how you are compiling the documents.

Cylox commented 11 years ago

Yes, I'm using XeLateX. I tried your suggestion and added the -enable-8bit-chars option. This solved the problem and the minted output is correct now. I used to command line: xelatex.exe -shell-escape -enable-8bit-chars -synctex=1 -interaction=nonstopmode "filename".tex I used the same line without the -enable-8bit-chars option and it works with minted 1.6, so I'm a bit confused why. Nevertheless it's great to have it running now. Maybe you want to update the minted documentation for this case? (If I simply didn't overlook it). Thanks for your fast reply!

gpoore commented 11 years ago

I have updated the documentation for the next release. I'm also puzzled about why it would work with minted 1.6. I've looked at the changes between 1.6 and 1.7, and don't see anything obvious that would cause different behavior.

Ahmedshukr commented 1 year ago

@gpoore Thanks, this helped me.