[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: decode-coding-string gone awry?
From: |
Richard Stallman |
Subject: |
Re: decode-coding-string gone awry? |
Date: |
Tue, 15 Feb 2005 12:28:07 -0500 |
Yuk. The problem is that this buffer is not only processed by
preview-latex, but also by AUCTeX, and the versions that get combined
may be different. AUCTeX uses the source code buffer's file encoding
by default, which is fine for basically unibyte based coding systems.
It sounds like the safest thing is to convert the string to what you
want, just before you use it.
If decode-coding-string is supposed to have a chance of reassembling
this junk, it must only be run at the end of reconstructing the byte
stream. Yes, this is completely insane. No, I can't avoid having to
deal with it somehow.
If you reconstruct the correct byte stream, it should work to apply
decode-coding-string to it.
- Re: decode-coding-string gone awry?, (continued)
- Re: decode-coding-string gone awry?, David Kastrup, 2005/02/14
- Re: decode-coding-string gone awry?, Stefan Monnier, 2005/02/14
- Re: decode-coding-string gone awry?, David Kastrup, 2005/02/14
- Re: decode-coding-string gone awry?, Stefan Monnier, 2005/02/14
- Re: decode-coding-string gone awry?, David Kastrup, 2005/02/14
- Re: decode-coding-string gone awry?, Stefan Monnier, 2005/02/14
- Re: decode-coding-string gone awry?, David Kastrup, 2005/02/14
- Re: decode-coding-string gone awry?, Stefan Monnier, 2005/02/14
- Re: decode-coding-string gone awry?, David Kastrup, 2005/02/14
- Re: decode-coding-string gone awry?, David Kastrup, 2005/02/14
- Re: decode-coding-string gone awry?,
Richard Stallman <=
- Re: decode-coding-string gone awry?, David Kastrup, 2005/02/15