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 English grade 2 symbols in Korean grade 2 table #3835

Closed
nvaccessAuto opened this issue Jan 31, 2014 · 12 comments
Closed

Add English grade 2 symbols in Korean grade 2 table #3835

nvaccessAuto opened this issue Jan 31, 2014 · 12 comments

Comments

@nvaccessAuto
Copy link

Reported by hyongsop.kim on 2014-01-31 21:12
Hello, I have a question about Nvda's supporting braille code Korean and English.
Now Nvda supports Korean braille grade2 code and I'm using it.
But even if I chose Korean grade2, English characters are appeared as grade1.
In fact this is very hard to read English.
How about make that if user chose Korean braille option as grade1, English also grade 1, but if user chose Korean braille as grade2, English also grade2?
Thank you.
Blocked by #4434

@nvaccessAuto
Copy link
Author

Comment 1 by nvdakor on 2014-02-01 09:23
Hello,
I tried to follow the standard braille rules used in Korea. If the Korean braille standard says that Korean grade 2 must include English grade 2, I'll include it. However, as far as I remember, in Korean, Latin letters (including English) are not contracted, nor contracted braille code for English is used.
Thanks.

@nvaccessAuto
Copy link
Author

Comment 2 by nvdakor on 2014-02-01 09:26
Changes:
Changed title from "Nvda's supporting braille code Korean and English." to "Add English grade 2 symbols in Korean grade 2 table"

@nvaccessAuto
Copy link
Author

Comment 3 by hyongsop.kim on 2014-02-06 20:13
Thank you for replies.
If Korean grade2 braille doesn't include English grade2, please add settings option that change English grade option.
In fact it is very hard to read English grade1 within Korean grade2.
Thank you.

@nvaccessAuto
Copy link
Author

Comment 4 by jteh on 2014-02-07 01:56
If the Korean braille code doesn't specify English grade 2, you'd need a non-standard table. This is a decision that would need to be made in the liblouis project.

@nvaccessAuto
Copy link
Author

Comment 5 by nvdakor on 2014-03-13 23:35
Hi,
after asking some Korean users, it appears that with ko-g2.ctb, we need to add en-us-g2.ctb's contraction list contents to allow English grade 2 to be displayed. Users there say transcribers and screen readers in Korea write contracted English braille when writing Korean grade 2.
As noted by Jamie, I'll do some work on this support, plus improvements to Korean tables (and 2010 standard revision support ) soon for inclusion in next LibLouis version (current version is 2.5.4, so hopefully in 2.5.5, which would be later this year).

@nvaccessAuto
Copy link
Author

Comment 6 by nvdakor on 2014-04-21 23:48
Hi,
A Korean user who lives in United States (not me) has provided a simple fix for this which will be submitted to LibLouis this week.
Thanks.

@nvaccessAuto
Copy link
Author

Comment 7 by hyongsop.kim on 2014-04-23 14:39
Thank you so much.
As soon as this braille code is applied, I will test and us it with appreciation.

@nvaccessAuto
Copy link
Author

Comment 8 by nvdakor on 2014-05-30 10:10
Hi,
I sent the modified table to LibLouis mailing list. Due to repository changes, the table was unable to be included for 2.5.4, but if the table is added, it'll be included in upcoming 2.6. Thanks.

@nvaccessAuto
Copy link
Author

Comment 9 by nvdakor on 2014-09-02 06:35
Hi,
Now merged and released as part of LibLouis 2.6.0, which will be included in NVDA 2014.4. Thanks.

@nvaccessAuto
Copy link
Author

Comment 10 by jteh on 2014-09-02 07:13
Changes:
Milestone changed from None to next

@nvaccessAuto
Copy link
Author

Comment 11 by James Teh <jamie@... on 2014-10-08 00:35
In [541ef62]:

Upgrade liblouis to 2.6.0.

Fixes #4434, #3835.

Changes:
State: closed

@nvaccessAuto
Copy link
Author

Comment 12 by jteh on 2014-10-08 01:24
Changes:
Milestone changed from next to 2014.4

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

No branches or pull requests

2 participants