Michael Gerz wrote:
> I agree that listings is a very important package (BTW: What does soul
> do?).
letterspacing, better underlining, strike-out letters, highlighting. It's a
standard package.
> However, what does "listings does not support unicode" mean? Does
> it mean that
>
> (a) latex breaks if we use non-ASCII characters_within_ a listing or
> (b) latex breaks if we _declare_ the document as UTF-8 and use UTF-8
> characters _outside_ of listings?
>
> Listings (at least mine) typically contain ASCII characters only (i.e.,
> programming code). If (a) holds, I am all for UTF-8 output only.
The fact that you don't use non-ASCII inside listings does not mean that you
want to restrict all other users to not use non-ASCII characters insider
listings, or does it? Search Google for "listings utf8" and see that this
causes real problems.
The two packages were just examples. In general, all packages that do fancy
things with active characters have to be rewritten in order to support
unicode, and in the case of listings and soul, this seems to be all but a
trivial task.
utf8ienc (which is used by \usepackage[utf8]{inputenc}) is still in beta stage
(read the commands in utf8ienc.def). I'm all for supporting it, and I'm sure
it will become standard eventually, but I think it's way too early to drop
support for the mature input encodings.
Jürgen
> > In summary and IMHO: let's keep the core C++ LyX simple and only
> > support utf8.
>
> That's a good point!
>
> Michael
