edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com, acsint@lists.the-brannons.com
Subject: [Edbrowse-dev] html unicode translations in edbrowse
Date: Wed, 18 Dec 2013 10:59:31 -0500	[thread overview]
Message-ID: <20131118105931.eklhad@comcast.net> (raw)

This is a heads up of where we are headed, quite soon I hope.

My jupiter adapter will pronounce unicodes in utf8 in the tty buffer
according to pronunciations that you can set in the config file.
Here is an example, the start of Greek.

u945	alpha
u946	beta
u947	gamma

So when this code appears as 2 bytes in utf8 it is read alpha,
no matter how it got there.

How did I use to do it?
The html browser would turn the html code
&#945; into the word alpha when rendering html.
See format.c line 1330
That works fine as long as I am browsing files from the web,
or html files that I wrote myself,
but if alpha beta gamma are in a document or from pdf or some other
source well I am just out of luck.
You can see at a glance that such things are better handled in the adapter.
It's a more general and flexible approach.

Once the latest version of Jupiter is pushed,
I may request of Chris that most or all
of those hard-coded translations in format.c go away,
and instead you just crank out the unicode that is implied by the html tag.
It's up to the adapter then to read it properly.
It's mostly deleting code that I'm happy to get rid of,
so should be no trouble.
The real test will be reading my math pages,
which are full of greek letters etc.

Thanks.

Karl Dahlke

             reply	other threads:[~2013-12-18 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18 15:59 Karl Dahlke [this message]
2013-12-18 17:06 ` Adam Thompson
2013-12-18 18:45 Karl Dahlke
2013-12-19 12:20 ` Adam Thompson

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=20131118105931.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).