-
Notifications
You must be signed in to change notification settings - Fork 0
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
Ordering of the open and closing "tags" in braille #10
Comments
Thanks guys for the thorough testing. Typeform is currently broken in liblouis so it doesn't surprise me that some things are not going as expected. It's the reason we're working on getting the changes from APH into the next release (liblouis#50). Could somebody please try and rebase the Norwegian table changes onto branch liblouis/ueb_update_code and check if that makes things better or worse? We might have to modify the table a bit because the behavior of some opcodes have changed. Documentation at https://github.com/liblouis/liblouis/wiki/New-opcodes-for-UEB (work in progress). |
There seems to be an additional problem with nested typeform where the inner typeform starts at a different letter, such as |
The test results are the same as before after rebasing to ueb_update_code. Here's a test where bold is nested inside italics, but does not start at the same place:
The results here are also the same after rebasing: output braille: Branch rebased to ueb_update_code: issue-10-norwegian-typeform |
I'm getting different results and they look better at first sight. @josteinaj @usama49 Could you please add the expected output to tests/harness/no_typeform_harness.txt and then run
|
Nesting is supposed to work in the ueb_update_code branch. That is, closing tags should be the reversed order of their opening tags. |
@usama49 @josteinaj Is this fixed in the latest version of pipeline-mod-nlb? (which does not use liblouis anymore to handle emphasis) |
I don't quite remember. We haven't worked on this lately I think. @usama49 @KariRudjord do you have time to test this? |
I've rebased the branch |
I have checked “The quick brown fox jumps” tests that Jostein gave me. They say the devil is in the details, but I found no devils. Everything correct. God work, Bert! |
@usama49 and I discovered a quirk in liblouis the other day in the ordering of open and closing "tags" (begin-/end-letters).
Italic/bold/underline in liblouis table no-no-g0.utb:
Test harness:
Running input "a b c" with different typeforms for the "b":
00000
⠁ ⠃ ⠉
1 12 14
⠁ ⠃ ⠉
00100
⠁ ⠆⠃⠰ ⠉⠰
1 23-12-56 14-56
⠁ <i>⠃</i> ⠉</i>
00200
⠁ ⠸⠃⠸ ⠉⠸
1 456-12-456 14-456
⠁ <u>⠃</u> ⠉</u>
00300
⠁ ⠸⠆⠃⠸⠰ ⠉⠸⠰
1 456-23-12-456-56 14-456-56
⠁ <u><i>⠃</u></i> ⠉</u></i>
00400
⠁ ⠠⠄⠃⠠⠄ ⠉⠠⠄
1 6-3-12-6-3 14-6-3
⠁ <b>⠃</b> ⠉</b>
00500
⠁ ⠠⠄⠆⠃⠠⠄⠰ ⠉⠠⠄⠰
1 6-3-23-12-6-3-56 14-6-3-56
⠁ <b><i>⠃</b></i> ⠉</b></i>
00600
⠁ ⠸⠃⠠⠄⠸ ⠉⠠⠄⠸
1 456-12-6-3-456 14-6-3-456
⠁ <u>⠃<b></u> ⠉</b></u>
00700
⠁ ⠃ ⠉
1 12 14
⠁ ⠃ ⠉
typeform 3 closes its underline "tag" before its italic "tag". I'm not sure if this is a
problem for braille readers, or if any braille specification says anything about it.
Maybe there could be a opcode for defining the default nesting order of bold/italic/underline?
Will it be possible to transform
<em><strong>TEXT</strong></em>
differentlythan
<strong><em>TEXT</em></strong>
?The text was updated successfully, but these errors were encountered: