Tests for element-level control over translation

[bertfrees]

Addresses requirements:

• 4.3:45
• 4.3:35C

Related issues:

• Transforming text braillespecs/braille-css#12
• Control translation pipeline-mod-braille#22

[mixa72]

Hi Bert
What exactly is meant by "where markup of the input is inadequate or undesirable"? Does this requirement refer to what we use in the dtbook, i.e. the brl:select element for verbatim translations? Or does it deal with different grades of contraction in the same book: a poem in a foreign language that needs to be rendered in uncontracted braille, for instance?
Thank you for clarifying the issue.

Regards,
Mischa

[bertfrees]

@mixa72 says

Or does it deal with different grades of contraction in the same book: a poem in a foreign language that needs to be rendered in uncontracted braille, for instance?

Exactly, that is an example of what I had in mind. The brl:select element for verbatim translations is also related. Another example is leaving out capital signs in certain sections as is sometimes done by Dedicon (see also 4.3:35C).

[dkager]

Interesting. Could this also be used to use different braille tables for certain text, e.g. marked up with a DTBook class? I’m thinking about the math code here.

[bertfrees]

Sure

[mixa72]

Hi Bert,

Please find attached some examples of downgrading and switching between two different languages / braille systems. In all the examples the surrounding braille system is German contracted braille (grade 2). Insertions in other languages such as blockquotes, poems, etc., can be handled by using different strategies:

• Downgrade: switch to grade 1 or 0, but continue using the surrounding braille system (German). In addition, an appropriate announcement/deannouncement (indicator) can be used.
  • Announcement single word: '. dot-6, dot-3
  • Announcement multiple words: -. dot-3-6, dot-3
  • Deannouncement multiple words: '. dot-6, dot-3
• Use the corresponding braille system: all braille symbols, punctuation, accents and hyphenation conform to the braille system of the language used in the insertion. In addition, an appropriate announcement/deannouncement (indicator) can be used.
  • Announcement single word: < dot-5-6
  • Announcement multiple words: << dot-5-6, dot-5-6
  • Deannouncement multiple words: '. dot-6, dot-3

Depending on the languages (also dialects) inserted in a text the use of announcements/deannouncements may vary. Therefore it would be nice if the transcriber could define/override them via CSS.

[mixa72]

Hi Bert,

You pointed out that Dedicon sometimes leave out capital signs (4.3:35C). We would like to have exactly the opposite, i.e., produce braille with the capitals in the text for some parts of the book (where capitalization is relevant) or in books for children.

Does this feature belong to the requirement 4.3:35C or is there a different one? A complete example (grade 0, 1, 2) is attached.

[dkager]

We would like to have exactly the opposite, i.e., produce braille with the capitals in the text for some parts of the book (where capitalization is relevant) or in books for children.

Do you mean to add capitals where the source material doesn't have them? The suppression of capital signs can be toggled on a paragraph-level (I think), so if you want to preserve capitals for parts of a book you simply don't suppress them for those parts. Obviously this doesn't allow for adding capitals that aren't in the source material.

[bertfrees]

@mixa72 Thanks, this is a good example of 4.3:45. Also thanks for the downgrading examples. Defining/overriding with CSS is a possibility.

@dkager: In German there are capitals everywhere but normally they are left out in braille except in proper nouns.

[mixa72]

Let me just put that right: capitals are generally left out in German braille except in pronouns for POLITE FORMS (Sie, Ihr, Ihnen, etc.) to avoid ambiguities with other pronouns written in small letters such as sie (= she), ihr (= to her), ihnen (= to them), etc.

[mixa72]

Hi Bert,

Do you remember your implementation for combining EMs in adjacent paragraphs (with the brl-continuation attribute)?

<p><em brl:continuation="em1 em2 em3 em4 em5">Mach's mit ihr.</em></p>
<p><em id="em1">Dann müssten wir zurückkommen und dich wirklich in die Mangel nehmen</em</p>
<p><em id="em2">Mach's mit dieser Nutte.</em></p>
<p><em id="em3">Du musst lernen, den Mund zu halten, außer wenn du auf den Knien liegst.</em></p>
<p><em id="em4">Mach's mit ihr, mach's mit dieser Nutte.</em></p>
<p><em id="em5">Weil dir ohnehin niemand glauben würde.</em></p>

Does that also go under requirement 4.3:45? If so, do you need test data for it?

[bertfrees]

Hi Mischa. Requirement 4.3:45 is about element-level control over the translation by means of configuration. And in practice "element-level configuration" means "CSS".

So the brl:continuation feature doesn't really belong here, but that doesn't mean it can't be implemented of course. In fact when Christian has finished porting the translation part of dtbook2sbsform, this feature should already be there. Everything (translation-related) that you have written tests for in dtbook2sbsform (UTFX) should be supported in the new system. That should save you a lot of work in providing tests.