Jürgen Spitzmüller wrote:
However, I agree the encoding switch is a hack, and we should at least limit
the hack to the case where it is needed, i.e. only switch to latin1 if we
actually are in a multibyte encoding.
So fundamentally, I think, it's a question of whether protecting the
user from himself on the encoding issue is worth the price.
Suggestions are welcome. But they have to work in any encoding.
I saw the patch you proposed on the developer list, and I think it's a
reasonable compromise. The only limitation I can see is that users
writing in a language that needs multibyte encoding won't be able to
embed native language comments in a listing. If that's important, they
can always do the listing in ERT.
/Paul
