all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Pogonyshev <pogonyshev@gmx.net>
Cc: handa@m17n.org
Subject: Re: `decode-coding-string' question
Date: Thu, 6 Jul 2006 23:34:21 +0300	[thread overview]
Message-ID: <200607062334.21288.pogonyshev@gmx.net> (raw)
In-Reply-To: <upsgiqyga.fsf@gnu.org>

Eli Zaretskii wrote:
> > From: Paul Pogonyshev <pogonyshev@gmx.net>
> > Date: Thu, 6 Jul 2006 18:52:28 +0300
> > Cc: Kenichi Handa <handa@m17n.org>
> > 
> > > > 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.
> 
> Paul, there's some misunderstanding here, so please bear with us.
> Handa-san cannot understand how come you have undecoded characters in
> the buffer, and neither can I.
> 
> The fact that it's a C file does not matter: Emacs _always_ decodes
> characters when it visits the file, no matter if it's a C file or
> something else.  In the text you get in your buffer the characters
> should be decoded.  The question is, how come it didn't decode these
> characters in your case?  Are there other non-ASCII characters in the
> same file, perhaps? if so, what characters are those?  For that
> matter, can you post a small sample file that, when visited in Emacs,
> leaves the UTF-8 encoded characters undecoded in the buffer?  Please
> post that file as a binary attachment, to avoid munging it by email
> software en- and de-coding.

There is indeed a misunderstanding.  The characters in the buffer _are_
decoded.  However the characters form C escape sequence, like "\xc2\xa9".
To know what character is encoded by this C sequence, I first translate
strings "\xc2" and "\xa9" to the appropriate (undecoded!) characters.
The resulting string of length 2 is encoded in UTF-8 and I decode it
to receive the copyright character or whatever.

Phew.  Hope it is clearer now.  Anyway, it is not so important for me
anymore, since gettext doesn't support non-ASCII characters in
untranslated strings with fairly recent GNU libc.  (And yes, I tried
inserting non-ASCII characters in the untranslated strings.)

Paul

  reply	other threads:[~2006-07-06 20:34 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200607062334.21288.pogonyshev@gmx.net \
    --to=pogonyshev@gmx.net \
    --cc=handa@m17n.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.