From: Karl Dahlke <firstname.lastname@example.org> To: email@example.com Subject: emojis Date: Sun, 28 Nov 2021 09:20:03 -0500 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) [-- Attachment #1: Type: text/plain, Size: 1721 bytes --] So for the next version, think of a streamlined way to enter emojis. Right now I go over to the config file, not the edbrowse config file but the one that runs my adapter, the one that pronounces each emoji that I care about. I search for the emoji by words, read the hex code, and type that into edbrowse. I'm getting so old though I almost can't remember 5 hex digits any more. And it's awkward no matter how you slice it. You might wonder if edbrowse and my adapter, or your adapter, could share a common file of emojis. Perhaps not. Sometimes I purposely misspell emojis, so they will be pronounced correctly by my synthesizer. Or I use a very abbreviated phrase. Would I remember to search for the words as I misspelled them? Or do I maintain separate lists of emojis in the two config files? And then, what is the user interface? I'm entering text, enter enter enter, and I want an emoji here, do I do something like ~egreen-heart similar to the way I use ~ to enter hex or unicode, and hope it finds the green heart? Or ~eheart and when it tries to resolve that, have it put up a menu of the various hearts, and I select green heart. If I've tried to enter 3 emojis on the line does it step through them one at a time and resolve each one, perhaps showing me a menu each time? And what if I'm not entirely sure even what word to search for? Maybe emojis having to do with a farm, which could be a barn or a cow or a farmer etc. Graphics systems let you scan through emojis by category. It all seems like a lot of work, and at the end of it all, I'm not sure the resulting system is any easier or faster than what I'm doing now. Well give it some thought. 😊 Karl Dahlke
reply other threads:[~2021-11-28 14:20 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: emojis' \ /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
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).