Eli Zaretskii <e...@gnu.org> writes: > More to the point: there seems to be a fundamental misunderstanding > here regarding the effect of selecting an encoding at save time. It > sounds like the OP thought that selecting a "literal" encoding, such > as raw-text, which is supposed to leave the binary stream unaltered > (apart of the EOL format), will ensure that a buffer will be saved > exactly as it was originally found on disk. But this is false. What > raw-text and no-conversion do is to write out the _internal_ > representation of each character without any conversions. The > original encoded form of the characters as found on disk at visit time > _cannot_ be recovered by saving with raw-text, because that encoded > form is lost without a trace when the file is _visited_ and decoded > into the internal representation. The only information that's left is > the coding-system used to decode the characters. But since the file's > encoding in this case is inconsistent, that coding-system cannot be > used to save it back (Emacs will not let you do so, as demonstrated in > the report), and therefore the original form cannot be recovered this > way.
Ahh, right; that make sense to me. -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
