From: tomas@tuxteam.de
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Is there a way to "asciify" a string?
Date: Mon, 28 May 2018 18:02:40 +0200 [thread overview]
Message-ID: <20180528160240.GA29819@tuxteam.de> (raw)
In-Reply-To: <CAP_d_8Xb+dQqm8wfe3n73r3xQwBHU7GrfSsqrOJiK4pPp3uQnw@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, May 28, 2018 at 10:30:38PM +0700, Yuri Khan wrote:
> On Mon, May 28, 2018 at 5:39 PM <tomas@tuxteam.de> wrote:
>
> > One often-used method is to just URL-encode [1] the thing [...]
[...]
> %3D ‘=’ and %2F ‘/’ are Trained Rat Level 1 material. Under your
> suggestion, my name is %D0%AE%D1%80%D0%B8%D0%B9+%D0%A5%D0%B0%D0%BD and it
> takes a certain effort to decode that in my head. I seriously doubt Tak
> Kunihiro’s urlencoded name could be read at all without decoding.
This is all Enlightened Beaver level. I'm far below that...
> (On the other hand, I regularly get offended at banks trying to
> automatically transliterate my name when issuing a card for me.)
FWIW, I've got one accented letter, and used to give out my name
with that, to see what comes back from the round trip. Hilarity :-)
Things have become much more boring the last fifteen to twenty
years, though.
Cheers
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlsMKCAACgkQBcgs9XrR2kY3IwCffQEZ5cn/K4rd8Vs9SigmROvx
r4kAnifbFp8deNRQ6p4nJgW4ZIxx3Zmy
=ntf1
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2018-05-28 16:02 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-27 6:22 Is there a way to "asciify" a string? Marcin Borkowski
2018-05-27 7:36 ` tomas
2018-05-27 12:36 ` Marcin Borkowski
2018-05-27 12:52 ` Teemu Likonen
2018-05-27 16:07 ` Eli Zaretskii
2018-05-27 16:59 ` Teemu Likonen
2018-05-28 5:24 ` Tak Kunihiro
2018-05-30 10:12 ` Marcin Borkowski
2018-05-30 17:05 ` Eli Zaretskii
2018-05-30 19:38 ` Marcin Borkowski
2018-05-27 20:00 ` tomas
2018-05-28 18:27 ` Eli Zaretskii
2018-05-29 6:37 ` tomas
2018-05-27 13:04 ` Yuri Khan
2018-05-30 10:14 ` Marcin Borkowski
2018-05-30 11:51 ` Yuri Khan
2018-05-30 15:04 ` Marcin Borkowski
2018-05-31 2:03 ` John Mastro
2018-06-02 18:07 ` Marcin Borkowski
2018-06-02 18:48 ` tomas
2018-06-07 17:16 ` Marcin Borkowski
2018-06-02 22:33 ` Drew Adams
2018-06-07 17:15 ` Marcin Borkowski
2018-06-02 18:12 ` Marcin Borkowski
2018-05-27 19:53 ` tomas
2018-05-28 8:15 ` Philipp Stephani
2018-05-28 10:28 ` Marcin Borkowski
2018-05-28 10:39 ` tomas
2018-05-28 15:30 ` Yuri Khan
2018-05-28 16:02 ` tomas [this message]
2018-05-30 10:12 ` Marcin Borkowski
2018-05-31 14:23 ` Stefan Monnier
2018-05-31 15:08 ` S. Champailler
2018-05-31 22:52 ` Richard Wordingham
2018-05-31 15:42 ` Marcin Borkowski
2018-05-31 15:53 ` Eli Zaretskii
2018-05-31 16:20 ` Yuri Khan
2018-05-31 19:03 ` Stefan Monnier
[not found] ` <mailman.871.1527781438.1292.help-gnu-emacs@gnu.org>
2018-05-31 23:23 ` James K. Lowden
2018-06-01 2:04 ` Stefan Monnier
2018-06-01 7:02 ` Eli Zaretskii
2018-05-27 14:55 ` Eric Abrahamsen
2018-05-27 16:00 ` Eli Zaretskii
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=20180528160240.GA29819@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@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 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.