Hi Ken, I believe you don't need computer braille indicators in UEB (Leona, can you clarify this?). As for the "odd" hex symbols: the 0x03B range are Greek characters. What might be happening is that the user types URL's in computer braille, but then when LibLouis back-translates this, it'll find that .a and .o are Greek symbols from UeB grade 1, hence will give you that result. I might have to look at exact rules on URL's - when I find it, I'll try my best (with help and feedback from others) to come up with a solution (at least from table design perspective). Cheers, Joseph On 8/1/13, Ken Perry <kperry@xxxxxxx> wrote: > > This is a separate problem from the en-us- problems I am writing about in > the other mail. I also tested backtranslation of URLs in UEB. First it > seems to me you should not have to mark urls in UEB to not be back > translated right? Even if you have to there is a weird bug that I can't > find with UEB g1 and g2. Here is what I get when I translate one URL: > > Starting URL: > http://www.aph.org > translation > _+http://.aph.org_: > Back translation > http://www\x03b1ph\x03bfrg<http://www/x03b1ph/x03bfrg> > > First do we need the _+ and _: in UEB and second what the heck is going on > with the\x03b I can't find that Unicode anywhere in all the includes for > en-uebg1 or en-uebg2. > > Ken > > For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com