edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@edbrowse.org
Subject: Re: Carl Linnaeus
Date: Wed, 1 Dec 2021 07:44:43 +0000	[thread overview]
Message-ID: <Yacn69VGEacw9phv@pinebook-pro> (raw)
In-Reply-To: <20211030182716.eklhad@comcast.net>

On Tue, Nov 30, 2021 at 06:27:16PM -0500, Karl Dahlke wrote:
> Still thinking about emojis, I am inspired by Carl Linnaeus, father of taxonomy and classification, and inventor of the binomial nomenclature.
> He attempted to categorize all animals and plants, good Lord, can you imagine?
> You've heard some of these latin names before, in identifying species, the first is the genus, the second is the species.
> 
> canus lupus: wolf
> canus familiaris: dog
> canus aureus: jackle
> ...
> 
> So I might imagine, as I enter text, typing ~jheart.green
> for the group of emojis under heart, and then the green heart.
> If matches are not unique, edbrowse would give you a menu to choose from.
> If you just type the category, you see all the emojis in the category.
> Once selected, the unicode is entered in position.
> 
> Love you ~jheart.green ~jheart.blue ~jheart.purple
> 
> Why not use e for emoji? Because e is already a hex digit, so ~ followed by e looks like we are entering hex bytes.
> And u is for unicode, so j for emoji, I guess.

How would the menu selection work during text entry? Other than that, the
notation sounds ok. I guess if the ebrc doesn't contain the unicode it'd
just be displayed as usual?

> 
> All this assumes you have these in .ebrc,
> and I would provide, in the edbrowse wiki, a typical library.
> I have written one, based on the file I use to pronounce these things, I just sort of reversed it.
> Here is one group, which is the heart group which is what we were talking about.
> 
> emoji heart {
> 2764 = original
> 1f499 = blue
> 1f49a = green
> 1f49b = yellow
> 1f49c = purple
> 1f9e1 = orange
> 1f5a4 = black
> 1f493 = beating
> 1f494 = broken
> 1f495 = two hearts
> 1f496 = sparkling
> 1f497 = growing
> 1f498 = arrow
> 1f49d = ribbon
> 1f49e = revolving
> 1f49f = decoration
> 1f491 = couple with heart
> }
> 
> Of course people could maintain their own library, for whatever they need.

Makes sense.

Cheers,
Adam.


  reply	other threads:[~2021-12-01  7:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30 23:27 Karl Dahlke
2021-12-01  7:44 ` Adam Thompson [this message]
2021-12-02  4:05 ` proposed CSSStyleDeclaration properties and defaults Kevin Carhart
2021-12-02  4:17   ` Karl Dahlke
2021-12-02  4:14 ` corrected: proposed CSSStyleDeclaration properties and default values Kevin Carhart

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=Yacn69VGEacw9phv@pinebook-pro \
    --to=arthompson1990@gmail.com \
    --cc=edbrowse-dev@edbrowse.org \
    --cc=eklhad@comcast.net \
    --subject='Re: Carl Linnaeus' \
    /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).