From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] entering high unicodes
Date: Thu, 28 Jan 2016 03:00:28 -0500 [thread overview]
Message-ID: <20160028030028.eklhad@comcast.net> (raw)
As per my last email about emojis,
I did something very simple that will probably meet my needs,
for as rarely as I do such things.
~u....; becomes the utf8 sequence for the hex unicode on input.
Semi is optional.
So my messsage to my wife is now written concisely as:
Love you ~u1f499 ~u1f49a ~u1f49b ~u1f49c
Strings become utf8, which are read by my adapter as
love you blue heart green heart yellow heart purple heart
so I know all is well.
This does not prevent a feature like ~[green heart] in the future,
with green heart in the config file, if I want to go to all that bother,
but I probably don't cause I just wouldn't be doing this
on a regular basis,
and for the rare times I do I don't mind looking up the unicodes.
I just needed an easy portable way to get them in,
and u hex digits is pretty standard, though sometimes written u+hex.
Karl Dahlke
next reply other threads:[~2016-01-28 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 8:00 Karl Dahlke [this message]
2016-01-28 8:01 ` Kevin Carhart
2016-01-28 11:20 ` Karl Dahlke
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=20160028030028.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.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.
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 NNTP newsgroup(s).