-
Notifications
You must be signed in to change notification settings - Fork 18
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
Comments
Hi Andre!
I discourage this feature, because it will break existing character definitions.
It will be god, if a new opcode from Daniel will be merged to Ll.
See the discussion from 640, if I recall it correctly from my heart…
From: André-Abush Clause <notifications@github.com>
Sent: Wednesday, November 27, 2019 12:24 AM
To: Andre9642/BrailleExtender <BrailleExtender@noreply.github.com>
Cc: zstanecic <zvonimirek222@yandex.com>; Mention <mention@noreply.github.com>
Subject: [Andre9642/BrailleExtender] Add HUC Braille support (#36)
HUC Braille is another representation for undefined chars designed by @DrSooom <https://github.com/DrSooom> . See the official documentation <https://danielmayr.at/huc/en.html> for more info.
Using this HUC-Braille converter <https://github.com/Andre9642/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 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 <https://github.com/DrSooom> , @zstanecic <https://github.com/zstanecic> ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#36> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVCDE2BL62F4FD5NCBRNGLQVWVYNANCNFSM4JR7DYHQ> . <https://github.com/notifications/beacon/ACVCDE6EDJPRBXWDE5HYDQ3QVWVYNA5CNFSM4JR7DYH2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H4IJMNQ.gif>
|
@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 |
@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.: Then, for each string to translate (i.e. each string sent to liblouis):
|
For historical reasons see also: Wayback Machine link for the English documentation and nvaccess/nvda#8702 |
@DrSooom Thank you for the clarification.
|
Hi @DrSooom, and happy new year! To test this:
By default, to enable/disable the — HUC Braille input — mode, press NVDA+Windows+h or dots(1+2+5+8)+space on braille displays supported. Otherwise define another gesture for this feature. Any suggestion? |
Hi adriano,
For easy of testing and monitoring, can you merge this to master?
From: André-Abush Clause <notifications@github.com>
Sent: Friday, January 10, 2020 5:16 PM
To: Andre9642/BrailleExtender <BrailleExtender@noreply.github.com>
Cc: zstanecic <zvonimirek222@yandex.com>; Mention <mention@noreply.github.com>
Subject: Re: [Andre9642/BrailleExtender] Add HUC Braille support (#36)
Hi @DrSooom <https://github.com/DrSooom> , and happy new year!
I've just added a first implementation of HUC Braille in input.
Currently, only HUC8 works (HUC6 is more complicated to implement). Also, this feature works only with NVDA 2019.3 (due to Python 3).
To test this:
1. Enable HUC Braille input mode.
2. Type your HUC Braille patterns on the braille display. E.g.: ⣭⠤⠕ for 🍑, ⣭⢤⡙ for 👍, ⣭⡤⣺ for 😀.
By default, to enable/disable the — HUC Braille input — mode, press NVDA+Windows+h or dots(1+2+5+8)+space on braille displays supported. Otherwise define another gesture for this feature.
Any suggestion?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#36> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVCDE3CWRLJTKMAOI6M6R3Q5CNLVANCNFSM4JR7DYHQ> . <https://github.com/notifications/beacon/ACVCDE2T2WGS3VEWFC6FOUTQ5CNLVA5CNFSM4JR7DYH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIUNG5Q.gif>
|
Hi @zstanecic, |
@Andre9642: I don't own a braille display with a braille keyboard. Is there another way to test this? @zstanecic: This link will always open the latest dev version of the BrailleExtender. Currently it's 20.01.10-dev. |
@DrSooom you can test this with pcKeyboardBrailleInput add-on -> https://addons.nvda-project.org/addons/pcKeyboardBrailleInput.en.html |
Small typo in the GUI (dropdown list): "Other dot patterns" » "Other dot pattern" And the Liblouis style output is incorrect. Code points from U+10000 to U+FFFFF starts with The rest works correctly – as far as I see (with NVDA 2019.3 Beta 1). Very, very good job. 👍 The Braille input test follows later. And should I also test the braille output with NVDA 2019.2.1 as well? Or does this version of the BrailleExtender no longer work with NVDA 2019.2.1? |
— commit 9dc8cfc @DrSooom thanks for your comments. I'll fix those. |
Hi @DrSooom, |
@Andre9642: I'm really sorry, but currently I must manually migrate the main content of my website (more than 1100 posts) into a complete new self-developed backend due to an upcoming php upgrade in February 2020. And I really have to hurry up here. Therefore I sadly cannot help you until the main part of the migration process was finished. If I don't do that, my website will get broken in February 2020. The HUC Braille Tables website isn't affected by the way – as it doesn't contain any php content. In the meantime you can use parts of the content of the Readme file of HUCv2, as this file is licensed under LGPL 2.1. To give you a suitable text, I will have to rewrite some parts of the documentation and also translate these parts into German. And for this process I sadly haven't the time yet. Thanks for your understanding. |
No problem, don't worry. Thanks and good luck! |
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:
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?
The text was updated successfully, but these errors were encountered: