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.

Sign up for GitHub

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

Jump to bottom

Update allowed values for translate #83

Open
bertfrees opened this issue Oct 11, 2019 · 0 comments
Open

Update allowed values for translate #83

bertfrees opened this issue Oct 11, 2019 · 0 comments

Comments

@bertfrees
Copy link
Contributor

Currently the spec says that the allowed values for the translate attribute are:

  • pre-translated
  • grade0
  • grade1
  • grade2
  • grade3
  • empty string

However, Dotify allows you to use any string. It is up to the BrailleTranslatorFactoryMakerService implementations to find a matching translator for a given string (and a locale).

In Dotify itself, some other values than the ones listed above are used, for example:

  • uncontracted
  • contracted
  • bypass
  • 6-dot
  • 8-dot

For the Liblouis integration, Joel even invented a new syntax that allows you to specify any contraction grade, and encode a combination of multiple properties in a single string. Examples are:

  • grade:1.5
  • grade:2/8-dot
  • uncontracted/6-dot

Note that this is not documented anywhere yet (but you can check out the code in TranslatorMode).

If you define your own BrailleTranslatorFactoryMakerService you are free to do anything you want. You could even use random identifiers to select your translators. In Pipeline I'm using a special translator "query" format.

In order to make the produced OBFLs portable we need a proper standard. (On the other hand it's also important to retain the flexibility that exists today in Dotify to select any translator you want, because translators can have very specific requirements that can not always be captured in a number of predefined properties.)
@bertfrees bertfrees mentioned this issue Jul 10, 2020
Open
bertfrees added a commit to bertfrees/obfl that referenced this issue Jan 19, 2022
@bertfrees
Improve/correct documentation of translate, xml:lang, hyphenate and s…
95e2853 
…tyle

- Use the terms "braille code" and "braille transcription" instead of
  "translation policy" in the documentation of the "translate"
  attribute.
- Update the allowed values for the "translate" attribute according to
  Dotify's "TranslatorMode" class. Fixes
  braillespecs#83.
- Also update the validation of the "translate" attribute.
- Make some corrections to the documentation of the "pre-translated"
  value, notably regarding white space processing.
- Add a section dedicated to the "xml:lang" attribute.
- Add a note about non-standard hyphenation in the documentation of
  the "hyphenate" attribute.
- Add more documentation for the "style" element.
@bertfrees bertfrees mentioned this issue Jan 19, 2022
Merged
bertfrees added a commit to bertfrees/obfl that referenced this issue Jan 26, 2022
@bertfrees
Improve/correct documentation of translate, xml:lang, hyphenate and s…
1dd3970 
…tyle

- Use the terms "braille code" and "braille transcription" instead of
  "translation policy" in the documentation of the "translate"
  attribute.
- Update the allowed values for the "translate" attribute according to
  Dotify's "TranslatorMode" class. Fixes
  braillespecs#83.
- Also update the validation of the "translate" attribute.
- Make some corrections to the documentation of the "pre-translated"
  value, notably regarding white space processing.
- Add a section dedicated to the "xml:lang" attribute.
- Add a note about non-standard hyphenation in the documentation of
  the "hyphenate" attribute.
- Add more documentation for the "style" element.
bertfrees added a commit to bertfrees/obfl that referenced this issue Jan 26, 2022
@bertfrees
Improve/correct documentation of translate, xml:lang, hyphenate and s…
e451cab 
…tyle

- Use the terms "braille code" and "braille transcription" instead of
  "translation policy" in the documentation of the "translate"
  attribute.
- Update the allowed values for the "translate" attribute according to
  Dotify's "TranslatorMode" class. Fixes
  braillespecs#83.
- Also update the validation of the "translate" attribute.
- Make some corrections to the documentation of the "pre-translated"
  value, notably regarding white space processing.
- Add a section dedicated to the "xml:lang" attribute.
- Add a note about non-standard hyphenation in the documentation of
  the "hyphenate" attribute.
- Add more documentation for the "style" element.
kalaspuffar pushed a commit to mtmse/obfl that referenced this issue Feb 11, 2022
@bertfrees @kalaspuffar
Improve/correct documentation of translate, xml:lang, hyphenate and s…
5b703fb 
…tyle

- Use the terms "braille code" and "braille transcription" instead of
  "translation policy" in the documentation of the "translate"
  attribute.
- Update the allowed values for the "translate" attribute according to
  Dotify's "TranslatorMode" class. Fixes
  braillespecs#83.
- Also update the validation of the "translate" attribute.
- Make some corrections to the documentation of the "pre-translated"
  value, notably regarding white space processing.
- Add a section dedicated to the "xml:lang" attribute.
- Add a note about non-standard hyphenation in the documentation of
  the "hyphenate" attribute.
- Add more documentation for the "style" element.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bertfrees