From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: `decode-coding-string' question Date: Wed, 05 Jul 2006 09:55:43 +0900 Message-ID: References: <200607040035.01379.pogonyshev@gmx.net> <200607041831.18435.pogonyshev@gmx.net> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: sea.gmane.org 1152061005 6322 80.91.229.2 (5 Jul 2006 00:56:45 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 5 Jul 2006 00:56:45 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 05 02:56:41 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Fxvgy-0001CD-HF for ged-emacs-devel@m.gmane.org; Wed, 05 Jul 2006 02:56:36 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fxvgy-0003sj-3t for ged-emacs-devel@m.gmane.org; Tue, 04 Jul 2006 20:56:36 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fxvgl-0003se-IL for emacs-devel@gnu.org; Tue, 04 Jul 2006 20:56:23 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fxvgi-0003qs-Tm for emacs-devel@gnu.org; Tue, 04 Jul 2006 20:56:22 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fxvgi-0003qm-QD for emacs-devel@gnu.org; Tue, 04 Jul 2006 20:56:20 -0400 Original-Received: from [150.29.246.133] (helo=mx1.aist.go.jp) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FxvuV-0002Ie-3V for emacs-devel@gnu.org; Tue, 04 Jul 2006 21:10:35 -0400 Original-Received: from smtp1.aist.go.jp ([150.29.246.12]) by mx1.aist.go.jp with ESMTP id k650uBO3025294; Wed, 5 Jul 2006 09:56:11 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp1.aist.go.jp with ESMTP id k650uB3f028193; Wed, 5 Jul 2006 09:56:11 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1Fxvg7-00024Z-00; Wed, 05 Jul 2006 09:55:43 +0900 Original-To: Paul Pogonyshev In-reply-to: <200607041831.18435.pogonyshev@gmx.net> (message from Paul Pogonyshev on Tue, 4 Jul 2006 18:31:18 +0300) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.50 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:56538 Archived-At: In article <200607041831.18435.pogonyshev@gmx.net>, Paul Pogonyshev writes: > Bad. OK, here is my task: I have a C string in the sources, possibly > containing encoded characters, like > "foo bla \xc2\xa9", > the last thing being the UTF-8 copyright characters. I want to > decode the string (can do that) _and_ know where particular > characters begin. Currently I set text property `point' on character > beginnings, but `decode-coding-string' eats them :( Can anyone see a > different solution, maybe ugly if nothing else? (Except that custom > implementation of `decode-coding-string' doesn't count as a solution > ;) Why don't you find paticular characters in the decoded string? --- Kenichi Handa handa@m17n.org