[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#413045: texlive-latex-recommended: UTF8 listings error



Le vendredi 02 mars 2007 à 17:42 +0100, Frank Küster a écrit :
> Frank Küster <frank@debian.org> wrote:
> 
> > Benoît Dejean <benoit@placenet.org> wrote:
> >
> >> Package: texlive-latex-recommended
> >> Version: 2005.dfsg.3-1
> >> Severity: minor
> >>
> >> Hello,
> >>
> >> i have switched to texlive and i cannot compile an old report anymore
> > [...]
> >> It looks like listings doesn't like UTF-8 chars inside brackets.
> >> Is my source wrong ?
> >
> > Hm, this is strange, since the versions of listings in texlive 2005 and
> > teTeX 3.0 (the one in etch and sid) are the same.  However, I can
> > reproduce the problem here.  If I change utf8 to latin1 and save the
> > file in iso-8859-1 encoding, then it works.
> 
> I found that it also works with utf8 when you add
> 
> \lstset{extendedchars=false}
> 
> I've not found the string "utf" in the documentation of listings-1.3,
> but in the PDF for 1.4 on CTAN.  Even that one doesn't talk about
> general utf encoding, only about CJK and similar things.

(cpp was a mistake)

<> fail too :

! Package inputenc Error: Unicode char \u8:�\expandafter not set up for
use wit
h LaTeX.

See the inputenc package documentation for explanation.
Type  H <return>  for immediate help.
 ...

l.13 ...E_ANNONCES_ENTRANTES seq 5  deny <réseau>
                                                   le 32
?
! Emergency stop.

or with ucs/utf8x

See the utf8x package documentation for explanation.
Type  H <return>  for immediate help.
 ...

l.214 ..._ANNONCES_ENTRANTES seq 5  deny <réseau>
                                                   le 32
?

> I'll ask the upstream author.

Thanks.

Using \lstset{extendedchars=false makes it compile, but the output dvi
is wrong. Instead of "// réseau" it renders "// érseau".

-- 
Benoît Dejean
GNOME http://www.gnomefr.org/
LibGTop http://directory.fsf.org/libgtop.html

Attachment: signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=


Reply to: