Re: `decode-coding-string' question

[Paul Pogonyshev]

Kenichi Handa wrote:
> In article <address@hidden>, Paul Pogonyshev <address@hidden> writes:
> 
> >> Why don't you find paticular characters in the decoded
> >> string?
> 
> > 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... :(
> 
> How did you make that buffer?  Why don't you have an
> already-decoded text in that buffer?

Because it's a C source file.  Strings have to be encoded there.

> > 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!
> 
> They are just displayed by 8 characters, as well as, a
> control character, say Formfeed (C-l), is displayed by 2
> characters "^L".

They are 8 different characters in the buffer.

Paul