Features/Text To Speech In The Toolkit - Revision history

Godiard at 19:42, 20 April 2015

2015-04-20T19:42:31Z

← Older revision		Revision as of 15:42, 20 April 2015
Line 1:		Line 1:
	<noinclude>		<noinclude>
	[[Category:~~Feature Page Incomplete]]~~		[[Category:FeatureLanded\|TextToSpeechInTheToolkit]]
	~~[[Category:Feature~~\|TextToSpeechInTheToolkit]]
	</noinclude>		</noinclude>

FGrose: FGrose moved page Features/TextToSpeechInTheToolkit to Features/Text To Speech In The Toolkit: deCamelCase

2014-09-07T02:30:33Z

FGrose moved page Features/TextToSpeechInTheToolkit to Features/Text To Speech In The Toolkit: deCamelCase

← Older revision	Revision as of 22:30, 6 September 2014
(No difference)

Godiard: /* Detailed Description */

2014-07-31T13:20:32Z

Detailed Description

← Older revision		Revision as of 09:20, 31 July 2014
Line 29:		Line 29:
	:voice, pitch and rate are optionals, if not set use the default values configured.		:voice, pitch and rate are optionals, if not set use the default values configured.
	:Return a id to enable pause and stop		:Return a id to enable pause and stop
			:We will need some type of notification when the TTS finished playing. In this way we can change the state of buttons, and start a new text,
			by example when have long texts, we can send it by parts.

	pause(id)		pause(id)

Godiard: /* Benefit to Sugar */

2014-07-31T13:08:20Z

Benefit to Sugar

← Older revision		Revision as of 09:08, 31 July 2014
Line 69:		Line 69:
	== Benefit to Sugar ==		== Benefit to Sugar ==

	Easier implementation of TTS in activities. Faster startup of activities.		Easier implementation of TTS in activities. Right now, there are a lot of code,
			usually implementing TTS with more than one backend, and with code copied from other activities.

			Faster startup of activities. Initialize gstreamer takes a substantial time.

	== Scope ==		== Scope ==

Godiard: /* Detailed Description */

2014-07-30T19:55:45Z

Detailed Description

← Older revision		Revision as of 15:55, 30 July 2014
Line 24:		Line 24:
	== Detailed Description ==		== Detailed Description ==

	These are the ~~funcitionalities~~ needed by the activities		These are the functionalities needed by the activities

	say(text,[voice])		say(text,[voice], [pitch], [rate])
			:voice, pitch and rate are optionals, if not set use the default values configured.
	:Return a id to enable pause and stop		:Return a id to enable pause and stop

Godiard: /* Activities using TTS */

2014-07-30T19:53:15Z

Activities using TTS

← Older revision		Revision as of 15:53, 30 July 2014
Line 53:		Line 53:
	:The user can select a languages from a list and make the activity do TTS on the text using that voice		:The user can select a languages from a list and make the activity do TTS on the text using that voice
	:The user can pause and stop		:The user can pause and stop

			* Speak
			:The user can select a languages from a list, pitch and rate, and make the activity do TTS on the text using that voice
			:The user can pause and stop

			* Story

			* TurtleBlocks

	* Write		* Write

Godiard at 19:15, 30 July 2014

2014-07-30T19:15:29Z

← Older revision		Revision as of 15:15, 30 July 2014
Line 41:		Line 41:
	:Return the best voice name available for the language.		:Return the best voice name available for the language.

	=== Activities using TTS ==		=== Activities using TTS ===

	* Clock		* Clock

Godiard: /* Detailed Description */

2014-07-30T19:14:23Z

Detailed Description

← Older revision		Revision as of 15:14, 30 July 2014
Line 24:		Line 24:
	== Detailed Description ==		== Detailed Description ==

			These are the funcitionalities needed by the activities

			say(text,[voice])
			:Return a id to enable pause and stop

			pause(id)

			stop(id)

			get_languages()
			:Return array of translated language names (to show in the UI),
			:and the voice name related in the backend.

			get_voice(lang)
			:lang is a language code
			:Return the best voice name available for the language.

			=== Activities using TTS ==

			* Clock
			:say the time in the default voice

			* Memorize
			:user can select the language and the game say text in the selected voice.
			:games based on Art4apps do TTS if a sound file is not available.

			* Read
			:The user can select a languages from a list and make the activity do TTS on the text using that voice
			:The user can pause and stop

			* Write
			:The user can select a languages from a list and make the activity do TTS on the text using that voice
			:The user can pause and stop

	== Benefit to Sugar ==		== Benefit to Sugar ==

Godiard: Created page with " Category:Feature Page Incomplete TextToSpeechInTheToolkit == Summary == Sugar have a global text to speech feature, you can..."

2014-07-18T13:15:52Z

Created page with "<noinclude> Category:Feature Page Incomplete TextToSpeechInTheToolkit </noinclude> == Summary == Sugar have a global text to speech feature, you can..."

New page

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|TextToSpeechInTheToolkit]]
</noinclude>

== Summary ==

Sugar have a global text to speech feature, you can select any text and do TTS with the device in the frame or with a keystroke.

But activities also do TTS for specific cases. Some activities doing it are Clock, Read, Memorize or Write.

There are a lot of code copied in every activity to implement it.

== Owner ==
* Name: [[Godiard| Gonzalo Odiard]]

* Email: godiard at sugarlabs.org

== Current status ==
* Targeted release: 0.104
* Last updated: 2014-07-18
* Percentage of completion: 0%

== Detailed Description ==

== Benefit to Sugar ==

Easier implementation of TTS in activities. Faster startup of activities.

== Scope ==
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

==UI Design==
''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.''

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== User Experience ==
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''

== Dependencies ==
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''

== Contingency Plan ==
''If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''

== Documentation ==
''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''

== Release Notes ==
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''

== Comments and Discussion ==

* ''Link to the discussion of this feature on lists.sugarlabs.org''
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]