Add English (U.S.) 8 dot extended computer braille table to the list #6836
Comments
|
Hi, are there real-life use cases for this table, including possible endorsements and testimonials from users and organizations? Thanks.
From: Davy Kager [mailto:notifications@github.com]
Sent: Friday, February 3, 2017 11:25 AM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [nvaccess/nvda] Add English (U.S.) 8 dot extended computer braille table to the list (#6836)
This was recently added to liblouis, pending the relase of 3.1: liblouis/liblouis@ <liblouis/liblouis@b4e8793> b4e8793
The table name is en-us-comp8-ext.utb.
This requires:
* Upgrade to liblouis 3.1 when it is released.
* Add the table to the lists of output and input tables.
Also appreciated:
* Scrutinize the table for errors and omissions.
Open questions:
* What to call this table? There is no official standard. Will the suggested name "extended computer braille" confuse users?
* Can this table supersede the current en-us-comp8.ctb table? It is a superset of the existing 8-dot table and thus backwards compatible. However, I hesitate because that would make it the default table and thus impacts a lot of users.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#6836> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkPsVjBupUnKuDGUW0POwFfiDYIuTks5rY38PgaJpZM4L2tYz> .
|
|
Yes: you can read anything that can be displayed with the Windows-1252 codepage. Examples include bullets, the euro sign and accented letters. |
|
See also liblouis/liblouis#261 |
|
As a trainer at @BabbageCom, I've already met several people who would like an extended US 8 dot braille table due to the several missing characters in the current one. Even letters like é, ë and á do not have a braille character assigned in the standard table. In the Netherlands, we do not have an 8 dot Dutch table, so either people use the English or German 8 dots table. But as mentioned, the current English one has its drawbacks |
|
Hi, suppose we do have evidence of support from users and organizations from one part of the world. How about other parts, such as United States where BANA rules are in effect? I personally don’t mind this being added and perhaps create a survey/experiment, but I’d like to hear comments from others around the world. Thanks.
From: Davy Kager [mailto:notifications@github.com]
Sent: Friday, February 3, 2017 11:36 AM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Joseph Lee <joseph.lee22590@gmail.com>; Comment <comment@noreply.github.com>
Subject: Re: [nvaccess/nvda] Add English (U.S.) 8 dot extended computer braille table to the list (#6836)
Yes: you can read anything that can be displayed with the Windows-1252 codepage. Examples include bullets, the euro sign and accented letters.
@LeonarddeR <https://github.com/leonardder> Can you say something about organization support?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#6836 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkGP1Vf1mz7uyT0YWi8RpThwgnmCTks5rY4GDgaJpZM4L2tYz> .
|
|
IMO this is a subject for discussion within liblouis. This issue is intended to track progress while that discussion is going on. As for the screen reader side, this table implements a compromise of what the major screen readers for Windows are currently calling U.S. English 8-dot braille. As the table mentions I was unable to find any official standards for one-to-one mappings of characters beyond ASCII, nor did inquiries at screen reader vendors reveal any specification documents. |
|
See also here for discussion on the liblouis mailing list. |
|
Is this a computer braille table in the strictest sense; i.e. is it a pure
1 to 1 mapping or are there duplicates/double cells? If it isn't strict, it
can't be considered computer braille for input purposes, since the
behaviour of duplicated/multi-cell patterns will be undesirable.
|
|
There are duplicates, and even some multi-cell patterns (ligatures). But backtranslation should be unambiguous through the use of the |
|
To clarify, do you mean noback has already been used where necessary? Also,
has it been used for all multi-cell patterns or only for duplicates? Again,
any multi-cell patterns aren't computer braille in a strict sense and thus
can't be handled; we'd need to treat the table as uncontracted (which
requires #2439).
|
|
There should be no multi-cell patterns that allow to be backtranslated. For single-cell patterns, there should always be zero or one matches for backtranslation. Obviously, forward translation is neither unambiguous nor only single-cell. |
|
Re #6935 |
… braille table, use that table to replace the existing English (U.S.) 8 dot computer braille table. Re #6836.
|
Does this inclusion explain the error I'm getting in recent Next snaps when
running the installer from the next archive? I posted this to the dev list
recently.
Should this not be trapped so when it does not seem to be found its not
going to generate an error sound?
Brian
bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Davy Kager" <notifications@github.com>
To: "nvaccess/nvda" <nvda@noreply.github.com>
Cc: "Subscribed" <subscribed@noreply.github.com>
Sent: Monday, March 06, 2017 4:44 PM
Subject: Re: [nvaccess/nvda] Add English (U.S.) 8 dot extended computer
braille table to the list (#6836)
… Re #6935
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#6836 (comment)
|
It would be really helpful if you could post the error, along with steps to reproduce if you have them. |
|
If you have once installed Next and than run a master installer, this error is expected. From what you said on NVDA devel, I assumed this was the case. Are you sure you get these errors in most recent next? |
- New braille translation tables: Danish 8 dot computer braille, Lithuanian, Persian 8 dot computer braille, Persian grade 1, Slovenian 8 dot computer braille. (#6188, #6550, #6773, #7367) - Improved English (U.S.) 8 dot computer braille table, including support for bullets, the euro sign and accented letters. (#6836) - Changed the description for "Slovene grade 1" to "Slovenian grade 1" for consistency.
This was recently added to liblouis, pending the relase of 3.1: liblouis/liblouis@b4e8793
The table name is
en-us-comp8-ext.utb.This requires:
Also appreciated:
Open questions:
en-us-comp8.ctbtable? It is a superset of the existing 8-dot table and thus backwards compatible. However, I hesitate because that would make it the default table and thus impacts a lot of users.The text was updated successfully, but these errors were encountered: