From: Paul Pogonyshev <pogonyshev@gmx.net>
Subject: Re: `decode-coding-string' question
Date: Wed, 5 Jul 2006 19:50:21 +0300 [thread overview]
Message-ID: <200607051950.21849.pogonyshev@gmx.net> (raw)
In-Reply-To: <43882.128.165.123.18.1152117274.squirrel@webmail.lanl.gov>
Stuart D. Herring wrote:
> > I do. But I need to know where they begin in the buffer (containing
> > the encoded C string.) I don't see a way to keep this information at
> > present... :(
> >
> > For instance, if the buffer only contains "\xc2\xa9foo", I'd like
> > to receive a string with the following text properties:
> >
> > #("©foo" 0 1 (point 0) 1 2 (point 8) 2 3 (point 9) 3 4 (point 10))
> >
> > The first characters actually takes 8 characters in the buffer!
>
> This is a horrible hack, but could you take the "©foo" that you get
> (without properties), turn it into "©-f-o-o-", then reencode it and look
> for the '-'s you added? It might run into trouble if there were -s in the
> string already, but you could always compare the original and -ed strings
> to resolve that.
Probably I don't have any other option, I have to try something like
this... Or maybe reencode character by one...
Thanks!
Paul
next prev parent reply other threads:[~2006-07-05 16:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 21:35 `decode-coding-string' question Paul Pogonyshev
2006-07-04 0:50 ` Kenichi Handa
2006-07-04 3:27 ` Eli Zaretskii
2006-07-04 17:29 ` Richard Stallman
2006-07-04 15:31 ` Paul Pogonyshev
2006-07-05 0:55 ` Kenichi Handa
2006-07-05 16:11 ` Paul Pogonyshev
2006-07-05 16:34 ` Stuart D. Herring
2006-07-05 16:50 ` Paul Pogonyshev [this message]
2006-07-06 1:08 ` Kenichi Handa
2006-07-06 15:52 ` Paul Pogonyshev
2006-07-06 20:18 ` Eli Zaretskii
2006-07-06 20:34 ` Paul Pogonyshev
2006-07-07 9:17 ` Eli Zaretskii
2006-07-07 16:05 ` Paul Pogonyshev
2006-07-07 19:56 ` David Kastrup
2006-07-07 22:54 ` Paul Pogonyshev
2006-07-08 8:18 ` David Kastrup
2006-07-04 12:55 ` Richard Stallman
2006-07-04 13:03 ` David Kastrup
2006-07-04 13:23 ` Johan Bockgård
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200607051950.21849.pogonyshev@gmx.net \
--to=pogonyshev@gmx.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).