[liblouis-liblouisxml] Re: UEB url problems
- From: Ken Perry <kperry@xxxxxxx>
- To: "liblouis-liblouisxml@xxxxxxxxxxxxx" <liblouis-liblouisxml@xxxxxxxxxxxxx>
- Date: Tue, 6 Aug 2013 03:42:04 +0000
Well then tUEB tables need some fixing. If no one else has time I will look at
it after I finish some other things I am working on.
Ken
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Leona Holloway
Sent: Monday, August 05, 2013 7:11 PM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: UEB url problems
Hi,
Joseph is correct: URLs are treated as normal text in UEB. Computer braille
indicators are not required and grade 2 braille can be used, although
contractions should not bridge two words.
Leona
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Joseph Lee
Sent: Friday, 2 August 2013 4:55 PM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: UEB url problems
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
As Vision Australia gets ‘fit for the future’, we don’t want anyone to miss out
on having a say about the organisation. Find out more about what we’re doing
and have your say by visiting http://www.visionaustralia.org/strategicplan
ABN: 67 108 391 831 ACN: 108 391 831
Vision Australia is a partnership between people who are blind, sighted or have
low vision. We are united by our passion that people who are blind or have low
vision will have access to and fully participate in every part of life they
choose.
This email (including its attachments) is confidential and may contain legally
privileged material or personal information. If you are not a named addressee
you must not use, disclose, copy, disseminate or print the email or any
information in it. If you have received this email in error please notify us
immediately and delete the email and any copies.
Vision Australia is not responsible for any changes made to a document other
than those made by Vision Australia or for the effect of the changes to the
document's meaning. Vision Australia accepts no liability for any damage caused
by this email or its attachments due to viruses, interference, interception,
corruption or unauthorised access.
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
z + b z pj 0 Zv+Z b K- -
- m X , \
Other related posts:
