unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Re: Fixing Gnus, and string encoding question
Date: Sun, 07 Apr 2019 10:17:46 -0700	[thread overview]
Message-ID: <87pnpxbupx.fsf@ericabrahamsen.net> (raw)
In-Reply-To: m2ftqujnx8.fsf@linux-m68k.org

Andreas Schwab <schwab@linux-m68k.org> writes:

> Symbol names can be unibyte and multibyte.  Make sure to get that right.
> If you see ã instead of \343 then the symbol has a unibyte name.

I will meditate on this for a bit.

Andreas Schwab <schwab@linux-m68k.org> writes:

> On Apr 06 2019, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>
>> (with-temp-buffer
>>   (set-buffer-multibyte t)
>>   (let ((coding-system-for-read 'raw-text))
>>     (insert-file-contents "active")
>>     (goto-char (point-min))
>>     (symbol-name (read (current-buffer)))))
>>     
>> I'm trying to turn that into something that looks like
>> "nnml:ã\203\206ã\202¹ã\203\210"
>
> (decode-coding-string (symbol-name (read "nnml:\343\203\206\343\202\271\343\203\210")) 'latin-1)

That did it! What a relief. I'm not sure why 'latin-1 in particular, but
that aligns all the strings correctly. I'll try to figure that out.

Huge thanks to you and Noam!

Eric




  reply	other threads:[~2019-04-07 17:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-05 20:47 Fixing Gnus, and string encoding question Eric Abrahamsen
2019-04-06  1:40 ` Noam Postavsky
2019-04-06  2:22   ` Eric Abrahamsen
2019-04-06  3:56     ` Noam Postavsky
2019-04-07  2:32       ` Eric Abrahamsen
2019-04-07  4:10       ` Eric Abrahamsen
2019-04-07  7:05         ` Andreas Schwab
2019-04-07 17:17           ` Eric Abrahamsen [this message]
2019-04-07 11:59         ` Noam Postavsky
2019-04-07 12:18           ` Andreas Schwab
2019-04-07 12:41         ` Andreas Schwab
2019-04-06  6:20     ` Eli Zaretskii
2019-04-07  2:30       ` Eric Abrahamsen
2019-04-06  8:26 ` Andreas Schwab

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=87pnpxbupx.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=emacs-devel@gnu.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 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).