If there's any issues with this case, please send an email before the
deadline 

Thanks 

--Irene
On Wed, 2008-07-23 at 18:30 +0800, Irene Huang wrote:
> Hi, All 
> 
> I am sponsoring this case. The time out is  set to be 07/29/2008. 
> 
> Additional materials are posted at 
> Internally
> http://sac.eng/Archives/CaseLog/arc/LSARC/2008/471/materials/
> 
> Externally
> http://www.opensolaris.org/os/community/arc/caselog/2008/471
> 
> --Irene
> On Wed, 2008-07-23 at 03:22 -0700, 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:
> >      o3read for OpenSolaris
> >     1.2. Name of Document Author/Supplier:
> >      Author:  Jerry Tan
> >     1.3  Date of This Document:
> >     23 July, 2008
> > 4. Technical Description
> > 1. Introduction
> >   1.1. Project/Component Working Name:
> > 
> >        o3read 0.0.4
> > 
> >   1.2. Name of Document Author/Supplier:
> >        Author:         Jerry Tan
> >        Sponsor:        Irene Huang
> > 
> >   1.3. Date of This Document:
> > 
> >          07/08/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:
> > 
> >                Robert O'Dea
> > 
> >     1.4.4. The name of your business unit:
> > 
> >                Software - OPG
> > 
> >   1.5. Email Aliases:
> >            1.5.1. Responsible Manager:  harry.lu at sun.com
> >            1.5.2. Responsible Engineer: jerry.tan at sun.com
> >            1.5.3. Interest List:        halton.huo at sun.com
> >                                         ava.zhang at sun.com
> > 
> > 2. Project Summary
> >   2.1. Project Description:
> >         
> >    o3read  is a standalone converter for the OpenOffice.org 
> >    swriter (*.sxw) and scalc (*.sxc) format to  html/text 
> >    format.
> > 
> > 3. Business Summary
> > 
> >    It is a userful tool, lightweight, which will help user 
> >    to read SXW file if no OpenOffice or StarOffice installed.
> > 
> > 4. Technical Description:
> >    4.1. Details:
> > 
> >    Example: 
> >  unzip -p fileformat.sxw content.xml | o3read | utf8tolatin1
> >   
> >    There are three output modules:
> > 
> >     * o3read displays a dump of the parse tree
> >     * o3totxt creates plain text
> >     * o3tohtml creates html code 
> > 
> >   The utility utf8tolatin1 converts from utf8 to 8859-1.
> >      
> >           
> >    4.2. Interfaces:
> >         Exported Interfaces
> >         Interface               Classification        Comments
> >            ---------------          ---------------          
> > ---------------     
> >         /usr/bin/o3read    Volatile          a tool to dump SXW document
> >         /usr/bin/o3totxt   Volatile          used to create plain text
> >         /usr/bin/o3tohtml  Volatile          used to create html file
> >         /usr/bin/utf8tolatin1 
> >                            Volatile          converts from utf8 to 8859-1.
> >         SUNWo3read         Uncommitted       package name
> >  
> > 
> > 
> > 
> > 
> >    4.3. Doc Impact:
> >         Man page is needed.
> > 
> >    4.4. Packaging & Delivery:
> >         
> >         SUNWo3read                    - the package for o3read
> > 
> > 
> >    4.5. Dependencies:
> >         
> > 
> >    4.6. L10N Impact:
> >         The Desktop team and the G11N are working together 
> >         to evaluate and  provide I18N/L10N support 
> > 
> > 
> >    4.7 Security Impact:
> > 
> >        None.
> >        
> >    5. Reference Documents:
> >       http://siag.nu/o3read/
> > 
> > 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