From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: decode-coding-region
Date: 04 Sep 1998 18:49:26 +0200 [thread overview]
Message-ID: <kig7lzjkell.fsf@jagor.srce.hr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "04 Sep 1998 17:41:54 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Hrvoje Niksic <hniksic@srce.hr> writes:
>
> > However, this will fail to work correctly when the decoding changes
> > the number of characters, because the extent indices will not be
> > preserved correctly.
>
> Decoding iso-2022-jp, for instance, will change the number of chars,
> so I don't know how useful this approach is...
Pretty useless I guess. I'll try to make the functions do the right
thing, then.
--
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
I luv the smell of nature in the morning. Smells like manure!
prev parent reply other threads:[~1998-09-04 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-03 14:56 decode-coding-region Hrvoje Niksic
1998-09-03 20:44 ` decode-coding-region Lars Magne Ingebrigtsen
1998-09-04 12:09 ` decode-coding-region Hrvoje Niksic
1998-09-04 15:41 ` decode-coding-region Lars Magne Ingebrigtsen
1998-09-04 16:49 ` Hrvoje Niksic [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=kig7lzjkell.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).