Skip to content

LibLouis 3, UEB table name/file names, and provisions for other enhancements.#6110

Merged
jcsteh merged 17 commits into
nvaccess:masterfrom
josephsl:i6109
Oct 11, 2016
Merged

LibLouis 3, UEB table name/file names, and provisions for other enhancements.#6110
jcsteh merged 17 commits into
nvaccess:masterfrom
josephsl:i6109

Conversation

@josephsl

@josephsl josephsl commented Jun 23, 2016

Copy link
Copy Markdown
Contributor

What's New entry: in Changes:

- Updated liblouis braille translator to 3.0.0. This includes significant enhancements to Unified English Braille. (#6109, #4194, #6220, #6140)

Fixes #6109. Fixes #4194. Fixes #6220. Fixes #6140.

josephsl added 2 commits June 23, 2016 13:53
One of the enhancements in LibLouis 3 is centralized pattern matching and translation routines. Among other things, it allows emphasais to be handled better.
Thus add pattern.c to list of files to be compiled as part of compiling NVDA from source, as without this, MS Linker (link.exe) presents unresolved symbol error.
…ccess#4194.

As the old uebc-g* tables are no longer maintained, it was decided to use the new en-ueb-g* set. Not only this makes the file names more consistent, it allows exciting changes to be included as part of LibLouis 3.0.0.
For string compatibility with old NVDA releases, table name presented to users will still be named Unified English Braille Code grade 1/2, with braille table name entries now mapped under en-ueb-g*.
@josephsl

Copy link
Copy Markdown
Contributor Author

@jcsteh @dkager

@dkager

dkager commented Jun 24, 2016

Copy link
Copy Markdown
Contributor

The Dutch table name also changed, and possibly the Norwegian one.
Note that this is an alpha release.

@josephsl

Copy link
Copy Markdown
Contributor Author

@dkager: Do you know the file names of these tables? I found Norwegian (no-no-comp8) but would like to get a list of file name changes so I can commit them in a single commit. Thanks.

…name for Telugu. re nvaccess#6109.

Davy Kager reports that Norwegian table file name has changed (confirmed), thus added the new file name.
Telugu: it is actually called 'Telugu', not 'Telegu' accoridng to Wikipedia, table header itself and other sources. No impact for translators as it is just English name that's different.
@josephsl

Copy link
Copy Markdown
Contributor Author

In case of te-in: it is actualy called Telugu, not Telegu. No impact for translators (just English label has been corrected). Thanks.

@derekriemer

Copy link
Copy Markdown
Collaborator

Hey Joseph,

I wouldn't be worried about commit cleanlyness too much, because @jcsteh
squashes them once he commits to master, and you can squash them if you
like before pr.

On 6/24/2016 3:03 PM, Joseph Lee wrote:

In case of te-in: it is actualy called Telugu, not Telegu. No impact
for translators (just English label has been corrected). Thanks.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#6110 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AFGivbSFq8HwoM1clWD93Ak-ZaAL6tUDks5qPEY4gaJpZM4I9R6q.


Derek Riemer
  • Department of computer science, third year undergraduate student.
  • Proud user of the NVDA screen reader.
  • Open source enthusiast.
  • Member of Bridge Cu
  • Avid skiier.

Websites:
Honors portfolio http://derekriemer.com
Awesome little hand built weather app!
http://django.derekriemer.com/weather/

email me at derek.riemer@colorado.edu mailto:derek.riemer@colorado.edu
Phone: (303) 906-2194

@dkager

dkager commented Jun 25, 2016

Copy link
Copy Markdown
Contributor

The Dutch tables are nl-BE-g0.utb (Belgium) and nl-NL-g0.utb (Netherlands).

@josephsl

Copy link
Copy Markdown
Contributor Author

Hi, how about g1 files? Thanks.

From: Davy Kager [mailto:notifications@github.com]
Sent: Saturday, June 25, 2016 2:30 AM
To: nvaccess/nvda nvda@noreply.github.com
Cc: Joseph Lee joseph.lee22590@gmail.com; Author author@noreply.github.com
Subject: Re: [nvaccess/nvda] LibLouis 3, UEB table name/file names, and provisions for other enhancements. (#6110)

The Dutch tables are nl-BE-g0.utb (Belgium) and nl-NL-g0.utb (Netherlands).


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub #6110 (comment) , or mute the thread https://github.com/notifications/unsubscribe/AHgLkL-UC10QSSuj6MFTiY8vE61sTgKNks5qPPUwgaJpZM4I9R6q .

@dkager

dkager commented Jun 25, 2016

Copy link
Copy Markdown
Contributor

The table has been renamed.

From: Joseph Lee [mailto:notifications@github.com]
Sent: Saturday, June 25, 2016 11:46
To: nvaccess/nvda nvda@noreply.github.com
Cc: Davy Kager mail@davykager.nl; Mention mention@noreply.github.com
Subject: Re: [nvaccess/nvda] LibLouis 3, UEB table name/file names, and provisions for other enhancements. (#6110)

Hi, how about g1 files? Thanks.

From: Davy Kager [ mailto:notifications@github.com mailto:notifications@github.com]
Sent: Saturday, June 25, 2016 2:30 AM
To: nvaccess/nvda < mailto:nvda@noreply.github.com nvda@noreply.github.com>
Cc: Joseph Lee < mailto:joseph.lee22590@gmail.com joseph.lee22590@gmail.com>; Author < mailto:author@noreply.github.com author@noreply.github.com>
Subject: Re: [nvaccess/nvda] LibLouis 3, UEB table name/file names, and provisions for other enhancements. (#6110)

The Dutch tables are nl-BE-g0.utb (Belgium) and nl-NL-g0.utb (Netherlands).


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub < #6110 (comment) https://github.com/nvaccess/nvda/pull/6110#issuecomment-228526266> , or mute the thread < https://github.com/notifications/unsubscribe/AHgLkL-UC10QSSuj6MFTiY8vE61sTgKNks5qPPUwgaJpZM4I9R6q https://github.com/notifications/unsubscribe/AHgLkL-UC10QSSuj6MFTiY8vE61sTgKNks5qPPUwgaJpZM4I9R6q> .


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #6110 (comment) , or mute the thread https://github.com/notifications/unsubscribe/AC9y8dlF9wWosjCvNWfN0qwDmivOaigDks5qPPjVgaJpZM4I9R6q . https://github.com/notifications/beacon/AC9y8c3uNa6jz7EIykKzmZvY0bbkJ7HGks5qPPjVgaJpZM4I9R6q.gif

@jcsteh

jcsteh commented Jul 4, 2016

Copy link
Copy Markdown
Contributor

The Dutch tables are nl-BE-g0.utb (Belgium) and nl-NL-g0.utb (Netherlands).

Ug. As is far too often the case in liblouis land, this is ridiculously confusing. The old tables still exist... but now we have these new ones.

  1. How is anyone supposed to know which tables to use?
  2. Why the rename? If these supersede the old ones, why not just replace the old ones?
  3. What do we call these? Currently, NVDA calls nl-NL-g1.ctb "Dutch (Netherlands) grade 1". Should this now be grade 0? Or does Dutch only have one grade and we should just drop the "grade 1" bit?
  4. Is this computer braille, uncontracted braille or contracted braille? I assume the last.

@dkager

dkager commented Jul 4, 2016

Copy link
Copy Markdown
Contributor
  1. Why the rename? If these supersede the old ones, why not just replace the old ones?

I thought they had been replaced. Something to look at.

  1. What do we call these?

Dutch only has one grade, so dropping the "grade 1" in the name sounds fine. This is uncontracted literary braille.

@josephsl

josephsl commented Jul 4, 2016

Copy link
Copy Markdown
Contributor Author

Hi,

@dkager: Thanks for the answer. Will apply it.

For other table maintainers: I think now is the time to tell us which tables are which, especially those that were modified (not due to opcode changes). Thanks.

According to Davy Kager, there is really one braille code for Dutch (no separate grade 0 nor grade 1). Thus:
* Dutch (Netherlands) Grade 1 -> Dutch (Netherlands)
* Duethc (Belgium) grade 1 -> Duethc (Belgium)
Also, the old g0 tables are incompatible iwth new optocdes introduced as part of LibLouis 3 (grade 1 tables use the new ones).
@LeonarddeR

Copy link
Copy Markdown
Collaborator
What do we call these?





  Dutch only has one grade, so dropping the "grade 1" in the name
    sounds fine. This is uncontracted literary braille.


Don't we also have a Dutch computer braille code, even though it
isn't in liblouis? Honestly, I think removing the grade from the
name can cause confusion at some point.

@josephsl

josephsl commented Jul 4, 2016

Copy link
Copy Markdown
Contributor Author

For @dkager: @jcsteh is thinking we should use LibLouis's own liblouis.def instead of nVDA's own. Doi you think it's safe to do now, and do you see some benefits and outstanding issues? Thanks.

@josephsl

josephsl commented Jul 4, 2016

Copy link
Copy Markdown
Contributor Author

Hi,

In the end, due to file inclusion issues and build issues on Windows (vanilla Liblouis def), it was decided that NVDA will use its own liblouis.def. Thanks.

@jcsteh

jcsteh commented Jul 4, 2016

Copy link
Copy Markdown
Contributor

Merge note: This should not be merged to master until liblouis 3.0.0 final is released. Once that happens, do the following:

  • Update the submodule.
  • Update the liblouis version in readme.md.

What's New entry: in Changes:

- Updated liblouis braille translator to 3.0.0. (#6109, #4194)
 - If you are using either Dutch or Unified English Braille Code tables, you will need to manually select these again from NVDA's Braille Settings dialog.

@dkager

dkager commented Jul 4, 2016

Copy link
Copy Markdown
Contributor

Instead of the NMake file using liblouis.def we should probably have MSVC generate one. This requires some code changes I'll have to discuss with Christian.
Currently you can't compile findTable.c with MSVC, which is why the .def file causes trouble. Not a big fan of gnulib... :)

@dkager

dkager commented Jul 4, 2016

Copy link
Copy Markdown
Contributor

Don't we also have a Dutch computer braille code, even though it isn't in liblouis? Honestly, I think removing the grade from the name can cause confusion at some point.

No, the 2005 braille standard only includes an uncontracted 6-dot code. In the past we had multiple levels of contractions (3 I believe), but now we don't. So this is grade 0, but since there are no other grades we can leave that out IMO.

On a final note, the Netherlands and Belgium tables differ only in some character definitions. The rules are the same for the whole Dutch language region. At some point we wanted to consolidate the two tables, but it hasn't happened yet.

@jcsteh

jcsteh commented Jul 6, 2016

Copy link
Copy Markdown
Contributor

Merge note: On further reflection and discussion, this should not be merged to master until #6140 (backwards compat for renamed tables) is done.

@josephsl

josephsl commented Jul 6, 2016

Copy link
Copy Markdown
Contributor Author

Hi, first commit on #6140 (for UEB series and Norwegian) will be done tonight, the rest will be done once beta comes out. Thanks.

From: James Teh [mailto:notifications@github.com]
Sent: Tuesday, July 5, 2016 8:49 PM
To: nvaccess/nvda nvda@noreply.github.com
Cc: Joseph Lee joseph.lee22590@gmail.com; Author author@noreply.github.com
Subject: Re: [nvaccess/nvda] LibLouis 3, UEB table name/file names, and provisions for other enhancements. (#6110)

Merge note: On further reflection and discussion, this should not be merged to master until #6140 #6140 (backwards compat for renamed tables) is done.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub #6110 (comment) , or mute the thread https://github.com/notifications/unsubscribe/AHgLkGhakDDDT0icElbl2X8Sf7SPuZJ2ks5qSyWagaJpZM4I9R6q .

josephsl added 5 commits July 5, 2016 21:20
…w filenames. re nvaccess#6140.

Given that people would be surprised if some tables would revert back to defaults, it would be handy to provide a short migration routine to map old table filenames to new ones. Thus, a tempoary routine and a map is introduced to handle it (to be removed at a future date).
More table renames for Danish (6-dot series) and Dutch, along with entries for them in migration map.
@jcsteh

jcsteh commented Aug 8, 2016

Copy link
Copy Markdown
Contributor

I want to get this into 2016.3, so in the interest of speed, I've made a few tiny changes myself (rather than going back and forth with a tiny review).

@jcsteh

jcsteh commented Sep 26, 2016

Copy link
Copy Markdown
Contributor

@michaelDCurran, can you please review these commits? I reviewed most of this, but then made some minor tweaks myself in the interest of speed when I was trying to get this into 2016.3 (a decision we obviously reversed). So, my small tweaks should probably be reviewed.

@michaelDCurran

Copy link
Copy Markdown
Member

I am happy with these 4 commits.

jcsteh added a commit that referenced this pull request Sep 27, 2016
@jcsteh jcsteh merged commit de7bf21 into nvaccess:master Oct 11, 2016
@nvaccessAuto nvaccessAuto added this to the 2016.4 milestone Oct 11, 2016
@josephsl josephsl deleted the i6109 branch January 27, 2017 01:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants