Thanks all!  That was certainly easy.  I remember it being much more 
time consuming to get Orca in (Fear and Loathing in ARC Vegas :-)).  You 
guys have certainly streamlined the process.

Thanks much!

Will

Irene Huang wrote:
> Closed approved.
> 
> --Irene
> Irene Huang wrote:
>> This case is due tomorrow.If there's any issues please send an email 
>> before that.
>>
>> Thanks
>>
>> --Irene
>> Irene Huang wrote:
>>> Hi, all
>>>
>>> attahced are the manpages and pkgmaps
>>>
>>> They are also available at (internal link)
>>> http://sac.eng/Archives/CaseLog/arc/LSARC/2008/536/materials/
>>>
>>> --Irene
>>> Shi-Ying Irene Huang wrote:
>>>> Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI
>>>> This information is Copyright 2008 Sun Microsystems
>>>> 1. Introduction
>>>>     1.1. Project/Component Working Name:
>>>>      espeak for OpenSolaris
>>>>     1.2. Name of Document Author/Supplier:
>>>>      Author:  Willie Walker
>>>>     1.3  Date of This Document:
>>>>     19 August, 2008
>>>> 4. Technical Description
>>>> 1. Introduction
>>>>    1.1. Project/Component Working Name:
>>>>
>>>>     eSpeak 1.37
>>>>
>>>>    1.2. Name of Document Author/Supplier:
>>>>
>>>>     Willie Walker
>>>>
>>>>    1.3. Date of This Document:
>>>>
>>>>     18-Aug-2008
>>>>            1.3.1. Date this project was conceived:
>>>>
>>>>     24-Apr-2008
>>>>
>>>>    1.4. Name of Major Document Customer(s)/Consumer(s):
>>>>
>>>>     1.4.1. The PAC or CPT you expect to review your project:
>>>>
>>>>         Solaris PAC
>>>>
>>>>     1.4.2. The ARC(s) you expect to review your project:
>>>>
>>>>         LSARC
>>>>
>>>>     1.4.3. The Director/VP who is "Sponsoring" this project:
>>>>
>>>>         Anant.Mithal at Sun.COM
>>>>
>>>>     1.4.4. The name of your business unit:
>>>>
>>>>         Accessibility Program Office
>>>>
>>>>    1.5. Email Aliases:
>>>>     1.5.1. Responsible Manager:
>>>>
>>>>         harry.burks at sun.com
>>>>
>>>>     1.5.2. Responsible Engineer:
>>>>
>>>>         william.walker at sun.com
>>>>
>>>>     1.5.3. Marketing Manager:
>>>>
>>>>         glynn.foster at sun.com
>>>>
>>>>     1.5.4. Interest List:
>>>>
>>>>         desktop-discuss at opensolaris.org
>>>>
>>>> 4. Technical Description:
>>>>     4.1. Details:
>>>>
>>>>     eSpeak is a text-to-speech system that converts written text into
>>>>     audio.  It can be used standalone via the 'espeak' application,
>>>>     which can generate *.wav files and send audio samples directly to
>>>>     the audio device.  The intended and typical use, however, is as a
>>>>     library with C/C++ bindings to be used by other applications.  
>>>> The     main consumer of eSpeak in Solaris is expected to be 
>>>> gnome-speech,
>>>>     which will use eSpeak to speak to the user.
>>>>
>>>>     In addition to an executable and a shared library, eSpeak includes
>>>>     private data files under /usr/share/espeak-data
>>>>         This proposal will add espeak 1.37, the latest stable 
>>>> version, to
>>>>     OpenSolaris 2008.11 and beyond.
>>>>
>>>>     4.2. Bug/RFE Number(s):
>>>>
>>>>     None.
>>>>
>>>>     4.3. In Scope:
>>>>
>>>>     See above.
>>>>
>>>>     4.4. Out of Scope:
>>>>
>>>>     See above.
>>>>
>>>>     4.5. Interfaces:
>>>>
>>>>     
>>>> --------------------------------------------------------------------
>>>>     Exported                Stability    Comments
>>>>     
>>>> --------------------------------------------------------------------
>>>>     SUNWespeak                Volatile
>>>>     SUNWespeak-devel            Volatile
>>>>
>>>>     libespeak.so.1                    Volatile    SONAME
>>>>     /usr/bin/espeak                Volatile    Command
>>>>     /usr/include/espeak/speak_lib.h         Volatile    Header file
>>>>     /usr/share/espeak-data                  Project Private Data files
>>>>
>>>>     
>>>> --------------------------------------------------------------------
>>>>     Imported                Comments
>>>>     
>>>> --------------------------------------------------------------------
>>>>     libCrun.so.1                  SunStudio C++ library
>>>>     libCstd.so.1                SunStudio C++ library
>>>>
>>>>     4.6. Doc Impact:
>>>>
>>>>     Man pages need to be written for the espeak application and the
>>>>     espeak library.
>>>>
>>>>     4.7. Admin/Config Impact:
>>>>
>>>>     The application using eSpeak to play audio needs permissions to the
>>>>     audio device, which is accessed via SADA.
>>>>
>>>>     4.8. HA Impact:
>>>>
>>>>     None.
>>>>
>>>>     4.9. I18N/L10N Impact:
>>>>
>>>>     The JDS and G11N teams are working together to evaluate and
>>>>     provide I18N/L10N support.
>>>>
>>>>     4.10. Packaging & Delivery:
>>>>         Adds two new packages, SUNWespeak (uncompressed package 
>>>> comprises
>>>>     approx 1.3 Mb) and SUNWespeak-devel (uncompressed package comprises
>>>>     approx 30k).
>>>>
>>>>     4.11. Security Impact:
>>>>
>>>>     None.
>>>>
>>>>     4.12. Dependencies:
>>>>
>>>>     eSpeak depends of the software listed in the Imported
>>>>     Interfaces section.  The Solaris version of eSpeak also
>>>>     uses SADA for audio, where SADA is covered by
>>>>     http://sac.sfbay/Archives/CaseLog/arc/PSARC/2004/563/.
>>>>
>>>> 5. Reference Documents:
>>>>
>>>>     http://espeak.sourceforge.net/ - eSpeak homepage
>>>>
>>>>         RFE #6738084
>>>>         CrPrint: http://bt2ws.central.sun.com/CrPrint?id=6738084
>>>>         Monaco: http://monaco.sfbay.sun.com/detail.jsf?cr=6738084
>>>>
>>>>
>>>> 6. Resources and Schedule
>>>>     6.4. Steering Committee requested information
>>>>        6.4.1. Consolidation C-team Name:
>>>>         Desktop
>>>>     6.5. ARC review type: FastTrack
>>>>     6.6. ARC Exposure: open
>>>>
>>>>   
>>>
>>
> 


Reply via email to