Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
Cylox opened this issue Sep 1, 2013 · 5 comments
Closed

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

Cylox opened this issue Sep 1, 2013 · 5 comments
Labels

Comments

@Cylox
Copy link

Cylox commented Sep 1, 2013

Using minted 1.7 with pygmentize 1.6:
This code:
\begin{minted}[fontsize=\footnotesize]{xml}



\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
Copy link
Author

Cylox commented Sep 1, 2013

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
Copy link
Owner

gpoore commented Sep 1, 2013

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
Copy link
Author

Cylox commented Sep 3, 2013

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
Copy link
Owner

gpoore commented Sep 4, 2013

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.

@gpoore gpoore closed this as completed Sep 4, 2013
@Ahmedshukr
Copy link

@gpoore Thanks, this helped me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants