edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: acsint@lists.the-brannons.com, Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] High Unicodes
Date: Sat, 31 Jan 2015 11:43:12 -0500	[thread overview]
Message-ID: <20150031114312.eklhad@comcast.net> (raw)

This is where speech adapters and edbrowse intersect,
thus posted to both groups.
Twitter, and I'm sure other social media,
make it easy for people to embed emoticons in their messages.
These are rendered by edbrowse, then spoken by speech software.
An example is &#x1f600; for a grinning face.
So, what should we do about this?
Right now both my worlds have a partial solution.
Edbrowse translates a few common high unicodes into words,
but of course this only happens when browsing html, and the resulting words are
hard coded English.
My jupiter speech has the right solution:
set pronunciations in your config file.
Other speech adapters do this as well.
The line in my config file looks like this.

x1f600 grin

That's all you need.

I think edbrowse shouldn't be doing this at all.
Just turn the &#codes into unicode, then utf8, then
to the screen, and let speech software say the symbols as you wish,
in your language.
And this would work for all files everywhere, not just html that edbrowse browses.
But, some have said that some speech adapters aren't this flexible,
and wouldn't it be nice if edbrowse would continue to perform
some of these translations, so at least surfing the web would work properly.
Well maybe, I'm not sure, but if we retain this functionality
it should probably be configurable, not hard coded.

Karl Dahlke

             reply	other threads:[~2015-01-31 16:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-31 16:43 Karl Dahlke [this message]
2015-01-31 18:21 ` Tyler Spivey
2015-01-31 19:09   ` Adam Thompson
2015-01-31 22:25     ` Chris Brannon
2015-02-01 16:30       ` Adam Thompson
2015-02-01 16:46 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=20150031114312.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=acsint@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).