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
The text was updated successfully, but these errors were encountered:
Comment 1 by nvdakor on 2014-02-01 09:23
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.
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.
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.
Comment 5 by nvdakor on 2014-03-13 23:35
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).
Comment 8 by nvdakor on 2014-05-30 10:10
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.