mirror of the now-defunct rocklinux.org
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

141 lines
5.5 KiB

  1. ROCKCFG_OUTPUT_TTS_SYSTEM
  2. Please select which Text-to-Speech system to use
  3. ROCKCFG_OUTPUT_TTS_FLITE
  4. Please supply the full, absolute location of your flite executable,
  5. in most cases, this file is in /usr/bin/flite (rock package: flite)
  6. ROCKCFG_OUTPUT_TTS_MBROLA
  7. Please supply the full, absolute location of your mbrola executable,
  8. in most cases, if installed manually, this file is called mbrola-
  9. linux-i386.
  10. ROCKCFG_OUTPUT_TTS_VOICEFILE
  11. Please supply the full, absolute location of your desired voicefile.
  12. Yes, this is the huge file you waited so long to download for. It
  13. is suggested to use an english/american voice, as ROCK Linux build
  14. output will be mostly english (but you can adjust some parts for
  15. your language below)
  16. ROCKCFG_OUTPUT_TTS_TXT2PHO
  17. Please supply the full, absolute location of your text-to-pho converter
  18. program. This program should be able to read text input from STDIN and
  19. write .pho output on STDOUT, so texts can be 'piped through'. The most
  20. common program for german voices for this, as far as i know, is txt2pho.
  21. ROCKCFG_OUTPUT_TTS_PLAY
  22. Please supply the full, absolute location of your console wave file
  23. player of choice. It should be able to read it's input from STDIN,
  24. any output on STDOUT of the program will be discarded. I suggest using
  25. the 'play' utility that comes with the sox package, if you are using
  26. OSS, or 'aplay' from the alsa-utils package, if you prefer ALSA.
  27. ROCKCFG_OUTPUT_TTS_ENABLE_HEADER
  28. This class of messages looks like, for example:
  29. "Building cross binutils and cc for ${arch_target} ..."
  30. and would be read out exactly like this. So, if you plan to use a non-
  31. english voice, you wouldn't want this to be read.
  32. ROCKCFG_OUTPUT_TTS_ENABLE_STATUS
  33. This class of messages looks like, for exmaple:
  34. "writing build log to src.cross.$id/binutils.log."
  35. and would be read out exactly like this. So, if you plan to use a non-
  36. english voice, you wouldn't want this to be read.
  37. ROCKCFG_OUTPUT_TTS_ENABLE_ERROR
  38. This class of messages looks like, for example:
  39. "Detected a problem with the flist wrapper lib on your system"
  40. and would be read out exactly like this. So, again, if you plan to use
  41. a non-english voice, you pobably wouldn't be too happy with the result.
  42. ROCKCFG_OUTPUT_TTS_ENABLE_PKG_DENY
  43. This class of message is issued when a package build is categorically
  44. denied before even the tarball is touched. Common examples are trying
  45. to build e17 without imlib2 having compiled. The hook for this class
  46. of messages provides 3 arguments:
  47. $1 the current stagelevel
  48. $2 the current package-name
  49. $3 the reason why this package got refused
  50. You can use these in the free configurable text, as shown in the
  51. example text. Note, however, that for a text in a non-english language
  52. you might want to leave $3 out, as the reason is in english usually.
  53. ROCKCFG_OUTPUT_TTS_TXT_PKG_DENY
  54. Please have a look at the help of ROCKCFG_OUTPUT_TTS_ENABLE_PKG_DENY.
  55. ROCKCFG_OUTPUT_TTS_ENABLE_PKG_START
  56. This class of message is issued when a package build is started.
  57. The hook for this class of messages provides 5 arguments:
  58. $1 the current stagelevel
  59. $2 the current package's repository
  60. $3 the current package-name
  61. $4 the ROCK Linux version, for example 2.0.0
  62. $5 the ROCK Linux extraversion, e.g. -rc1
  63. You can use these in the free configurable text, as shown in the
  64. example text.
  65. ROCKCFG_OUTPUT_TTS_TXT_PKG_START
  66. Please have a look at the help of ROCKCFG_OUTPUT_TTS_ENABLE_PKG_START.
  67. ROCKCFG_OUTPUT_TTS_ENABLE_PKG_FINISH
  68. This class of message is issued when a package build is finished.
  69. The hook for this class of messages provides 3 arguments:
  70. $1 the current stagelevel
  71. $2 the current package's repository
  72. $3 the current package-name
  73. You can use these in the free configurable text, as shown in the
  74. example text.
  75. ROCKCFG_OUTPUT_TTS_TXT_PKG_FINISH
  76. Please have a look at the help of ROCKCFG_OUTPUT_TTS_ENABLE_PKG_FINISH.
  77. ROCKCFG_OUTPUT_TTS_ENABLE_PKG_ABORT
  78. This class of message is issued when a package build is aborted.
  79. The hook for this class of messages provides 3 arguments:
  80. $1 the current stagelevel
  81. $2 the current package's repository
  82. $3 the current package-name
  83. You can use these in the free configurable text, as shown in the
  84. example text.
  85. ROCKCFG_OUTPUT_TTS_TXT_PKG_ABORT
  86. Please have a look at the help of ROCKCFG_OUTPUT_TTS_ENABLE_PKG_ABORT.
  87. ROCKCFG_OUTPUT_TTS_ENABLE_ERRORQUOTE
  88. This class of message is usually used to quote the last few lines of a
  89. logfile to let you probably guess the reason of a failed build without
  90. the need to open the logfile. This is not ment to be read out (not even
  91. by humans), but you can replace the text with a generic, severe error
  92. message in your preferred message (as the example shows). The log
  93. excerpt will be readable on console as usual. However, if you intend to
  94. produce some weird noise, any argument given is to be interpreted as
  95. logfile content (so, use $*, if you want it all).
  96. ROCKCFG_OUTPUT_TTS_TXT_ERRORQUOTE
  97. Please have a look at the help of ROCKCFG_OUTPUT_TTS_ENABLE_ERRORQUOTE.
  98. ROCKCFG_OUTPUT_TTS_SAYPROG
  99. Please have a look at the help of ROCKCFG_OUTPUT_TTS_OWNSCRIPT.
  100. ROCKCFG_OUTPUT_TTS_USEFESTIVAL
  101. Select this, if you have installed the festival tts system. The festival
  102. system is major to mbrola with regards to it's licence, mbrola is binary-
  103. only, whereas festival is licensed under an OSI-approved licences.
  104. ROCKCFG_OUTPUT_TTS_FESTIVAL
  105. Please supply the full, absolute location of your 'festival' binary.