when i try to write accentuated characters (éà...) in a lstlisting environment,

hence :






$ ln -s arg1 arg2
arg1 : chemin (relatif ou absolu) du répertoire ou du fichier pointé
arg2 : chemin (relatif ou absolu) du lien à créer


here's what i get :

enter image description here

note : it seems like the accentuated letters are placed before the non-accentuated ones.

My document uses UTF-8 encoding (from texworks settings)

I've tried to setup lstset setting extendedchars to \true and inputencoding to utf8. But this doesn't seem to apply any effects to the current code..

  • The accented à seems correct. Does the problem appear with any other character than é?
    – T. Verron
    Feb 21, 2013 at 9:42
  • @T.Verron eèéàe is rendered as èéàee (it seems like the accentuated letters are placed before non-accentuated ones)
    – vdegenne
    Feb 21, 2013 at 9:48
  • 5
    Duplicate of Having problems with listings and UTF-8. Can it be fixed? (anyway I try adding the literate option for each character and it works)
    – user202729
    Aug 1, 2022 at 14:40

1 Answer 1


The listings package doesn't handle UTF-8, only one-byte characters. You have to use the listingsutf8 package, which works only with the \lstinputlisting command, not with the lstlisting environment.

You'll have to change the inputencoding option in your \lstset command such as:


This is needed by the listingsutf8 package to convert multibyte UTF-8 characters to one-byte characters. As I suspect you're French, latin9 is a good choice. For other languages, other one-byte character sets might be more appropriate.

Check listingsutf8 documentation for details.

  • the same trouble occurs using this package.
    – vdegenne
    Feb 21, 2013 at 10:09
  • You also need in your preamble: \lstset{inputencoding=utf8/latin9} Feb 21, 2013 at 10:12
  • According to listings documentation, utf8 encoding should be usable with extendedchars=false, that is by letting inputenc handle these chars instead of listings. While it indeed doesn't work in this very case, I wouldn't say it is a design choice.
    – T. Verron
    Feb 21, 2013 at 10:16

Not the answer you're looking for? Browse other questions tagged .