Re: decode-coding-region and encode-coding-region
"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
I think that if you somehow manage to create an extent that ends up
with endpoints inside a *-coding-region, you've screwed up somehow
anyway so an approximation should be fine.
Maybe. Generally, I want to fix the case where Gnus properties get
screwed merely because it encodes/decodes the region.
The real problem (and what I was really asking, now that I've
slept
on it) is "what do you do when the text properties you have applied
don't make sense?" For example, Japanese has no italic or bold
(...)
That's not my care, really. I merely make sure that the extents are
preserved -- how the stuff stored in the extents will be handled is up
to the redisplay code.
It seems to me that you probably want to split such extents,
preserve the meaning outside of the *-coding-region, and do
something (probably at user option) inside the *-coding-region.
I will definitely not code something like that. What I want is
conceptually very simple. I don't think I will kludge around Mule
limitations more than absolutely necessary.
I hope that by now it is at least clear *what* exactly I'd like
decode/encode-coding-region to do. If it's not, then I'm seriously
incapable of communiating my ideas.