all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer")
Cc: 23701@debbugs.gnu.org
Subject: bug#23701: Decoding broken by sequence ESC comma
Date: Mon, 06 Jun 2016 09:27:46 +0200	[thread overview]
Message-ID: <mvmtwh6u68d.fsf@hawking.suse.de> (raw)
In-Reply-To: <874m979scx.fsf@T420.taylan> ("Taylan Ulrich \=\?utf-8\?Q\?\=5C\=22Bay\=C4\=B1rl\=C4\=B1\=2FKammer\=5C\=22\=22's\?\= message of "Mon, 06 Jun 2016 01:35:26 +0300")

taylanbayirli@gmail.com (Taylan Ulrich "Bayırlı/Kammer") writes:

> I just grepped all the files and the archives seem to contain a few more
> files in which the ESC , sequence appears, such as:
>
>     G^[,Avdel vs Godel vs Goedel
>
>     ^[,Hylem vs ^[,Hylen vs the same with proper vowel symbols
>
>     ... I know that there is a single bit sequence that specifies
>     strings, and it's not ^[,A+;^[(Bs; I know that there's another
>     single sequence that specifies ellipsis, and it's not ^[$,1s&^[(B
>     ...
>
> These aren't ISO-8859-1 either.  I don't know what encoding they're
> supposed to be in.  Could also be a mail server breaking things.

That looks like iso-2022-7bit, except for missing shift-out sequences.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."





      parent reply	other threads:[~2016-06-06  7:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-05 19:13 bug#23701: Decoding broken by sequence ESC comma Taylan Ulrich Bayırlı/Kammer
2016-06-05 19:59 ` Andreas Schwab
2016-06-05 22:35   ` Taylan Ulrich Bayırlı/Kammer
2016-06-06  2:33     ` Eli Zaretskii
2016-06-06 13:17       ` Taylan Ulrich Bayırlı/Kammer
2016-06-06 15:07         ` Eli Zaretskii
2016-06-06  7:27     ` Andreas Schwab [this message]

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=mvmtwh6u68d.fsf@hawking.suse.de \
    --to=schwab@linux-m68k.org \
    --cc=23701@debbugs.gnu.org \
    --cc=taylanbayirli@gmail.com \
    /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.