|
144.
|
|
|
DVD chapter extractor
|
|
|
Summary
|
|
|
|
(no translation yet)
|
|
|
|
Located in
Package: chaplin
|
|
145.
|
|
|
The tool parses a DVD disc or image and extracts the exact duration for each chapter of a given title. Then the total list of chapters is split into a user-selectable number of subsets. Each subset should have approximately the same duration.
|
|
|
Description
|
|
|
|
(no translation yet)
|
|
|
|
Located in
Package: chaplin
|
|
146.
|
|
|
http://www.lallafa.de/bp/chaplin.html
|
|
|
Description
|
|
|
|
(no translation yet)
|
|
|
|
Located in
Package: chaplin
|
|
147.
|
|
|
Doom engine closely-compatible with vanilla doom
|
|
|
Summary
|
|
|
|
(no translation yet)
|
|
|
|
Located in
Package: chocolate-doom
|
|
148.
|
|
|
Chocolate doom is a modern, cross-platform doom engine with the major design goal of emulating the behaviour of vanilla Doom as close as is possible. For example, chocolate doom can read and write vanilla doom save games.
|
|
|
Description
|
|
|
|
(no translation yet)
|
|
|
|
Located in
Package: chocolate-doom
|
|
149.
|
|
|
Unlike most modern doom engines, chocolate doom is not derived from the Boom source-port and does not inherit its features (or bugs).
|
|
|
Description
|
|
|
|
(no translation yet)
|
|
|
|
Located in
Package: chocolate-doom
|
|
150.
|
|
|
Chocolate doom requires a doom-wad to play. If you have a copy of the commercial games Doom or Doom 2, you can generate a doom-wad package using "game-data-packager".
|
|
|
Description
|
|
|
|
(no translation yet)
|
|
|
|
Located in
Package: chocolate-doom
|
|
151.
|
|
|
French and English Text-To-Speech for MBROLA
|
|
|
Summary
|
|
|
|
(no translation yet)
|
|
|
|
Located in
Package: cicero
|
|
152.
|
|
|
This Text-To-Speech (TTS) engine speaks French; a preliminary English support is also offered. The engine uses context-sensitive rules to produce phonemes from the text. It relies on MBROLA to generate actual audio output from the phonemes. The TTS engine is implemented using the Python programming language.
|
|
|
Description
|
|
|
|
(no translation yet)
|
|
|
|
Located in
Package: cicero
|
|
153.
|
|
|
The upstream authors have come up with this TTS to try and meet their own needs as blind users. It's designed to be plugged as output to some screen-review software, firstly with BRLTTY. They favor speed and intelligibility over perfect pronunciation. Cicero is aimed to have a quick response time, the ability to quickly shut-up and skip to another utterance, intelligibility where it counts (not perfect pronunciation), the ability to track speech progression, relative simplicity (hackability) and relative small code size.
|
|
|
Description
|
|
|
|
(no translation yet)
|
|
|
|
Located in
Package: cicero
|