Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add HUC Braille support #36

Open
Andre9642 opened this issue Nov 26, 2019 · 5 comments · May be fixed by #39
Open

Add HUC Braille support #36

Andre9642 opened this issue Nov 26, 2019 · 5 comments · May be fixed by #39

Comments

@Andre9642
Copy link
Owner

@Andre9642 Andre9642 commented Nov 26, 2019

HUC Braille is another representation for undefined chars designed by @DrSooom. See the official documentation for more info.

Using this HUC-Braille converter, I'd like to implement this alternative in BrailleExtender.

In this scope, we need review the option — Show undefined characters as... —. I suggest:

  • A new label: Representation of undefined characters
  • A list box with the following choices:
    • Use braille table behavior (default)
    • Dots 1-8 (⣿)
    • Dots 1-6 (⠿)
    • Empty cell (⠀)
    • Question mark (depending output table)
    • Other dot patterns (to be filled in an edit box)
    • Hexadecimal, Liblouis style
    • Hexadecimal, HUC8
    • Hexadecimal, HUC6

Also I'd like to try to implement the possibility to — Use HUC8/HUC6 for braille input —. Maybe a special temporary mode for that (?).

Limitation: due to the end of Python 2 in January and other technical issues with Python 2 and Unicode, This feature will require Python 3.

Any though @DrSooom, @zstanecic?

@zstanecic

This comment has been minimized.

Copy link
Collaborator

@zstanecic zstanecic commented Nov 27, 2019

@DrSooom

This comment has been minimized.

Copy link

@DrSooom DrSooom commented Nov 27, 2019

@zstanecic: The implementation of the HUC Braille Tables into the BrailleExtender will and MUST be a different one than the way I describe here (= just including the complete tbl/tbi files). Due to @Andre9642's script it's (theoretically) already possible to limited the HUC8 and HUC6 definitions only to a limited code point range. Furthermore it could be also possible that @Andre9642 is able to merge existing braille tables with parts of the HUC Braille Tables by using a script. So the definitions in the original braille tables always win, as this process will no longer produce multiple definitions – which is currently the case with my HUC Braille Tables if you are completely including them into other braille tables.

See also: liblouis/liblouis#868 and liblouis/liblouis#869

@Andre9642

This comment has been minimized.

Copy link
Owner Author

@Andre9642 Andre9642 commented Nov 27, 2019

@zstanecic In addition to Daniel's answer, I think I'll do as follows on the first attempt:

First, add an 'undefined' rule to the current table. E.g.:
undefined 78-12345678-78

Then, for each string to translate (i.e. each string sent to liblouis):

  1. Retrieve the liblouis translation.
  2. If the braille string contains at least one "⣀⣿⣀" occurrence, replace all these occurrences by their corresponding HUC representation (using the original string and — HUC-braille converter —).
  3. Show the string on the braille display.
@DrSooom

This comment has been minimized.

Copy link

@DrSooom DrSooom commented Dec 5, 2019

@Andre9642

This comment has been minimized.

Copy link
Owner Author

@Andre9642 Andre9642 commented Dec 13, 2019

@DrSooom Thank you for the clarification.
I also planned to implement the possibility to:

  • Limit the HUC8 and HUC6 definitions only to a limited code point ranges.
  • Customize prefix braille characters.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.