ZedAI to EPUB 3

Inputs

• ZedAI document
  Input ZedAI.
  Media-type:

  • application/z3998-auth+xml
  Sequence: no
• Text-to-speech configuration file
  Configuration file for text-to-speech.

  Configuration file for text-to-speech.

  More details on the configuration file format.

  Media-type:

  • application/vnd.pipeline.tts-config+xml
  Sequence: no

Outputs

• TTS log
  Log file with information about text-to-speech process.
• EPUB
  The resulting EPUB 3 publication.
  Media-type:

  • text

Options

• Style sheets
  A list of CSS style sheets to take into account.

  A list of CSS style sheets to take into account.

  Must be a space separated list of URIs, absolute or relative to the input.

  Style sheets specified through this option are called “user style sheets”. Style sheets can also be attached to the source document. These are referred to as “author style sheets”. They can be linked (using an ‘xml-stylesheet’ processing instruction or a ‘link’ element), embedded (using a ‘style’ element) and/or inlined (using ‘style’ attributes). Only author styles that apply to “speech” media are taken into account.

  All style sheets are applied at once, but the order in which they are specified has an influence on the cascading order. Author styles take precedence over user styles.

  Possible values: <anyURI>
  Default value:
• Lexicons
  A list of PLS lexicons to take into account.

  A list of PLS lexicons to take into account.

  Must be a space separated list of URIs, absolute or relative to the input.

  Lexicons can also be attached to the source document, using a ‘link’ element.

  PLS lexicons allow you to define custom pronunciations of words. It is meant to help TTS processors deal with ambiguous abbreviations and pronunciation of proper names. When a word is defined in a lexicon, the processor will use the provided pronunciation instead of the default rendering.

  The syntax of a PLS lexicon is defined in Pronunciation Lexicon Specification (PLS) Version 1.0, extended with regular expression matching. To enable regular expression matching, add the “regex” attribute, as follows:

  <lexicon xmlns="http://www.w3.org/2005/01/pronunciation-lexicon" version="1.0"
           alphabet="ipa" xml:lang="en">
    <lexeme regex="true">
      <grapheme>([0-9]+)-([0-9]+)</grapheme>
      <alias>between $1 and $2</alias>
    </lexeme>
  </lexicon>
  

  The regex feature works only with alias-based substitutions. The regex syntax used is that from XQuery 1.0 and XPath 2.0.

  Whether or not the regex attribute is set to “true”, the grapheme matching can be made more accurate by specifying the “positive-lookahead” and “negative-lookahead” attributes:

  <lexicon version="1.0" xmlns="http://www.w3.org/2005/01/pronunciation-lexicon"
           alphabet="ipa" xml:lang="en">
    <lexeme>
      <grapheme positive-lookahead="[ ]+is">SB</grapheme>
      <alias>somebody</alias>
    </lexeme>
    <lexeme>
      <grapheme>SB</grapheme>
      <alias>should be</alias>
    </lexeme>
    <lexeme xml:lang="fr">
      <grapheme positive-lookahead="[ ]+[cC]ity">boston</grapheme>
      <phoneme>bɔstøn</phoneme>
    </lexeme>
  </lexicon>
  

  Graphemes with “positive-lookahead” will match if the beginning of what follows matches the “position-lookahead” pattern. Graphemes with “negative-lookahead” will match if the beginning of what follows does not match the “negative-lookahead” pattern. The lookaheads are case-sensitive while the grapheme contents are not.

  The lexemes are matched in this order:

  1. Graphemes with regex=”false” come first, no matter if there is a lookahead or not;
  2. then come graphemes with regex=”true” and no lookahead;
  3. then graphemes with regex=”true” and one or two lookaheads.

  Within these categories, lexemes are matched in the same order as they appear in the lexicons.

  Possible values: <anyURI>
  Default value: p:system-property('d:org.daisy.pipeline.tts.default-lexicon')
• Chunk size
  The maximum size of HTML files in kB. Specify "-1" for no maximum.

  The maximum size of HTML files in kB. Specify "-1" for no maximum.

  Top-level sections in the ZedAI become separate HTML files in the resulting EPUB, and are further split up if they exceed the given maximum size.

  Possible values: Any <integer>
  Default value: -1
• Enable TTS log
  Whether or not to make the TTS log available.

  Whether or not to make the TTS log available.

  The TTS log contains a great deal of additional information that is not present in the main job log and that is helpful for troubleshooting. Most of the log entries concern particular chunks of text of the input document.

  The default can be changed using the org.daisy.pipeline.tts.log property.

  Possible values: true or false
  Default value: p:system-property('d:org.daisy.pipeline.tts.log')
• Enable text-to-speech
  Whether to use a speech synthesizer to produce audio files.
  Possible values: true or false
  Default value: false