From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: meta@public-inbox.org
Subject: Feature R/BUG: Auto uri_unescape() & utf8 handling
Date: Tue, 23 May 2017 12:17:09 +0200 [thread overview]
Message-ID: <CACBZZX5Gnow08r=0A1J_kt3a=zpGyMfvsqu8nAN7kacNnDm+dg@mail.gmail.com> (raw)
Feature request:
It would be neat to be able to right click on highlighted msgids in
the "what's cooking e-mails" in GMail and paste them into public
inbox, unfortunately Chrome copies this URL escaped, so you get e.g.:
https://public-inbox.org/git/?q=%3CCACBZZX4UUwzRQmyH8joYaqHnuVTjVtGBHp%252BiZKcnAnwoM_ZJhg%40mail.gmail.com%3E
Whereas that doesn't work because it's seacrhing for a URI escaped
msgid that contains + converted to %2B
Whereas unescaping it works:
https://public-inbox.org/git/?q=CACBZZX4UUwzRQmyH8joYaqHnuVTjVtGBHp%2BiZKcnAnwoM_ZJhg%40mail.gmail.com
I don't know if it breaks anything else but calling uri_unescape()
would work for these sort of msgids, but then of course searching for
%2b wouldn't work, hrm...
BUG:
The code is missing a utf8::decode() or equivalent somewhere, try
searching for: https://public-inbox.org/git/?q=%C3%86var
The search works, but the text in the search box is garbled, the
second search is https://public-inbox.org/git/?q=%C3%83%E2%80%A0var
third https://public-inbox.org/git/?q=%C3%83%C6%92%C3%A2%E2%82%AC%C2%A0var
etc.
next reply other threads:[~2017-05-23 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 10:17 Ævar Arnfjörð Bjarmason [this message]
2017-05-23 18:39 ` Feature R/BUG: Auto uri_unescape() & utf8 handling Eric Wong
2017-05-23 22:02 ` [PATCH] www: do not mangle characters from search queries Eric Wong
2017-05-23 18:43 ` Feature R/BUG: Auto uri_unescape() & utf8 handling Eric Wong
2017-05-23 23:17 ` [PATCH] searchview: retry queries if uri_unescape-able Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACBZZX5Gnow08r=0A1J_kt3a=zpGyMfvsqu8nAN7kacNnDm+dg@mail.gmail.com' \
--to=avarab@gmail.com \
--cc=meta@public-inbox.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://80x24.org/public-inbox.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).