Skip to content

No longer use liblouis pass1only by default#7822

Closed
LeonarddeR wants to merge 1 commit into
nvaccess:masterfrom
BabbageCom:noPass1Only
Closed

No longer use liblouis pass1only by default#7822
LeonarddeR wants to merge 1 commit into
nvaccess:masterfrom
BabbageCom:noPass1Only

Conversation

@LeonarddeR

Copy link
Copy Markdown
Collaborator

Link to issue number:

Follow-up of #7702
Closes #7301
Fixes #7693, and possibly other issues
fixes #7526

Description of this pull request:

In #7702, we introduced a hidden config parameter to toggle the use of Liblouis multipass vs. pass1only. In that pr, pass1only was still enabled, although you could disable it by changing a hidden config parameter. E.g.:
import config; config.conf["braille"]["outputPass1Only"]=False

This pr changes the default for outputPass1Only to false, effectively disabling pass1only for everyone except for the users who explicitly decide to enable pass1only by hand again.

Though this is a one liner change, this should not go straight to master as it could have major effect on how people experience braille output for certain tables.

Rationale

According to commit liblouis/liblouis@ac59139 , output position issues have been fixed in liblouis master, this commit will be in Liblouis 3.4. Note that other screen readers do not use pass1only either, so we don't have to wait for Liblouis 3.4 in order to have this merged.

Also note that liblouis/liblouis#445 states that pass1only will be deprecated in liblouis 3.4 and removed in liblouis 3.5. Thus, as soon as liblouis 3.5 is there and we use that in NVDA, the config parameter should be removed altogether. Cc @josephsl

Change log entry:

@feerrenrut

Copy link
Copy Markdown
Contributor

Is there a release schedule, giving an estimate for when liblouis 3.5 will be available?

@feerrenrut feerrenrut changed the title Noi longer use liblouis pass1only by default No longer use liblouis pass1only by default Dec 5, 2017
@feerrenrut

Copy link
Copy Markdown
Contributor

Apologies if I've missed something obvious, could you please clarify what the following means?

According to commit liblouis/liblouis@ac59139 , output position issues have been fixed in liblouis master, this commit will be in Liblouis 3.4. Note that other screen readers do not use pass1only either, so we don't have to wait for Liblouis 3.4 in order to have this merged.

We are currently using Liblouis 3.3 I believe, do these bugs not affect us? Why don't we have to wait for Liblouis 3.4?

@josephsl

josephsl commented Dec 5, 2017 via email

Copy link
Copy Markdown
Contributor

@LeonarddeR

Copy link
Copy Markdown
Collaborator Author

@feerrenrut commented on 5 dec. 2017 01:47 CET:

We are currently using Liblouis 3.3 I believe, do these bugs not affect us? Why don't we have to wait for Liblouis 3.4?

I think there are various reasons why this particular pr can be incorporated before Liblouis 3.4 is out:

  1. Other screen readers, including JAWS, already use Liblouis in production without pass1only
  2. Using pass1only causes major problems for users of several tables as mentioned above.
  3. The particular liblouis commit I mentioned suggests that currently, pass1only is also broken somehow.

@josephsl: I assume liblouis 3.4 is scheduled for release before NVDA 2018.1 will be in feature freeze? If so, I can change this pr to be a Liblouis 3.4 incorporation pr as soon as liblouis 3.4 is there.

@josephsl

josephsl commented Dec 5, 2017 via email

Copy link
Copy Markdown
Contributor

@LeonarddeR

Copy link
Copy Markdown
Collaborator Author

That's fine with me, I will close this pr.
@jospehsl: Do you think we should remove the hidden config parameter altogether, or keep it until 3.5 is out?

@LeonarddeR LeonarddeR closed this Dec 5, 2017
@josephsl

josephsl commented Dec 5, 2017 via email

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

3 participants