Re: [Edbrowse-dev] html unicode translations in edbrowse

[Adam Thompson <arthompson1990@gmail.com>]

On Wed, Dec 18, 2013 at 10:59:31AM -0500, Karl Dahlke wrote:
> 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.

That sounds like a good idea.

> How did I use to do it?
> The html browser would turn the html code
> α 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.

Again agreed.

> 
> 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.

This makes sense as long as the user's adapter does handle utf8.
I use speakup with espeak which seems to handle most things,
but probably not everything, and I've got no idea what those characters would
do to my braille display.

I'm not against the idea, but it may be worth remembering that edbrowse has a
wider user community than those using jupiter,
particularly as there's a debian package for edbrowse and not for jupiter (at
least not in the main repos).

Also, are you planning to ship an example list of these characters or do users
have to go through the utf8 charset to work out what's what?

Cheers,
Adam.