>>>> "Hrvoje" == Hrvoje Niksic
<hniksic(a)srce.hr> writes:
Hrvoje> "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
> We should ask Ken'ichi what he thinks the correct behavior
of
> `decode-coding-region' should be; I don't think it should move
> point, myself, but I don't know what the "correct" behavior
> should be if point starts strictly between START and END.
Hrvoje> This may not be related to your problem, but I'll chime in
Hrvoje> anyway. decode-coding-region is broken in both FSFmacs
Hrvoje> and XEmacs, primarily because it destroys all
Hrvoje> metainformation on buffer regions (markers and
Hrvoje> extents/text-props). If you look at the implementation of
Hrvoje> encode/decode-coding-region, you'll easily guess why that
Hrvoje> is so.
It's not clear to me what it means to "preserve metainformation" in
this case if the extent is completely contained in the region. It's
even worse if the extend crosses the boundary.
If it's easy, can you explain what you had in mind?
Martin and I have been kicking around the idea of always preserving
the file contents verbatim, and using extent-like objects to present
various views of the buffer (eg, the way hexl mode does). Then it
sortof makes sense, except that even in Unicode there are characters
that aren't text, and treatment of those characters might not be
obvious.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
__________________________________________________________________________
__________________________________________________________________________
What are those two straight lines for? "Free software rules."