From sh162551@sac.sfbay.sun.com Tue May 27 20:44:50 2008
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m4S3ioNL015572
	for <LSARC-ext@sac.sfbay.sun.com>; Tue, 27 May 2008 20:44:50 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m4S3iou3004169;
	Tue, 27 May 2008 21:44:50 -0600 (MDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K1K00F017QQ9Y00@brm-avmta-1.central.sun.com>; Tue,
 27 May 2008 21:44:50 -0600 (MDT)
Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K1K00ARC7QP1T60@brm-avmta-1.central.sun.com>; Tue,
 27 May 2008 21:44:49 -0600 (MDT)
Received: from sac.sfbay.sun.com (new-sac.SFBay.Sun.COM [129.146.175.65])
	by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id m4S3inMT043270; Tue, 27 May 2008 20:44:49 -0700 (PDT)
Received: from sac.sfbay.sun.com (localhost [127.0.0.1])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m4S3ilpY015565; Tue,
 27 May 2008 20:44:47 -0700 (PDT)
Received: (from sh162551@localhost)
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id m4S3ilnh015561; Tue,
 27 May 2008 20:44:47 -0700 (PDT)
Date: Tue, 27 May 2008 20:44:47 -0700 (PDT)
From: Shi-Ying Irene Huang <sh162551@sac.sfbay.sun.com>
Subject: W3M [LSARC/2008/346 FastTrack timeout 06/03/2008]
To: lsarc-ext@sun.com
Message-id: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
Status: RO
Content-Length: 6312


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:
	 W3M
    1.2. Name of Document Author/Supplier:
	 Author:  Rick Ju
    1.3  Date of This Document:
	27 May, 2008
4. Technical Description
1. Introduction
   1.1. Project/Component Working Name:

        w3m  a text-based WWW browser

   1.2. Name of Document Author/Supplier:
        
        Author:         Rick Ju
        Sponser:        Irene Huang

   1.3. Date of This Document:

        05/11/2008

2. Technical Description:
    2.1. Details:
     
     w3m is a text-based web browser as well as a pager like `more' or `less'.
     With w3m you can browse web pages through a terminal emulator window
     (xterm, rxvt or something like that).  Moreover, w3m can be used as a
     text formatting tool which typesets HTML into plain text.

     w3m has support for tables, frames, SSL connections, color and even inline
     images on suitable terminals. Generally, it renders pages in a form as true
     to their original layout as possible.  And W3m is small. Its stripped
     binary for Sparc is only 260kbyte.

     w3m locally run cgi scripts to test html output (requires *no* webserver).
     w3m keystroke compatible with lynx and support the keybindings customize.
     w3m support SSL through the openssl library. And w3m could support cookies.

     Table rendering algorithm in w3m

     HTML table rendering is difficult. Tabular environment of LaTeX is not very
     difficult, which makes the width of a column either a specified value or
     the maximum width to put items into it. On the other hand, HTML table
     renderer has to decide the width of a column so that the entire table can
     fit into the display appropriately, and fold the contents of the table
     according to the column width.  Inappropriate column width decision makes
     the table ugly.  Moreover, table can be nested, which makes the algorithm
     more complicated.

     1. First, calculate the maximum and minimum width of each column. The
        maximum width is the width required to display the column without
        folding the contents. Generally, it is the length of paragraph
        delimited by <BR> or <P>. The minimum width is the lower limit
        to display the contents.  If the column contains the word
        `internationalization', the minimum width will be 20. If the column
        contains <pre>..</pre>, the maximum width of the preformatted
        text will be the minimum width of the column.  2. If the width of
        the column is specified by WIDTH attribute, fix the column
        width using that value. If the specified width is smaller than the
        minimum width of the column, fix the column width to the minimum
        width.

     3. Calculate the sum of the maximum width (or fixed width) of each column
        and check if the sum exceeds the screen width. If it is smaller than
        screen width, these values are used for width of each column.

     4. If the sum is larger than the screen width, determine the widths of
        each column according to the following steps.
         1. Let W be the screen width subtracted by the sum of widths of
            fixed-width columns.
         2. Distribute W into the columns whose width are not decided, in
            proportion to the logarithm of the maximum width of each column.
         3. If the distributed width of a column is smaller than the minimum
            width, then fix the width of the column to the minimum width,
            and do the distribution again. 

    In this process, distributed width is proportion to logarithm of maximum width.

    The algorithm above assumes that the screen width is known. But it is not
    true for nested table. According the algorithm above, the column width of
    the outer table have to be known to render the inner table, while the total
    width of the inner table have to be known to determine the column width of
    the outer table. If WIDTH attribute exists there are no problems.
    Otherwise, w3m assumes that the inner table is 0.8 times as wide as the
    outer table. It works fine, but if there are two tables side by side in an
    outer table, the width of the outer table always exceeds the screen width.
    To render this kind of table correctly, one have to render the table once,
    check the width of outmost table, and then render the entire table again.
    Netscape might employ this kind of algorithm.

    2.2. Interfaces:
           Exported Interfaces
                Interface        Classification    Comments
                --------------- ---------------    -----------------------
                w3m CLI           Volatile         See w3m-help.txt

                $HOME/.w3m/config Project Private  w3m Configuration information
                SUNWw3m           Uncommited       w3m end-user packaging contains binary, libraries.
                SUNWw3m-l10n      Uncommited       Localization.

        Imported Interfaces
                Interface        Classification        Comments
                --------------- --------------- -----------------------
                HTML/XML/HTTP       Stable           These specs are defined
                                                     W 3C.org
                OpenSSL             Volatile         PSARC/2003/500
                Firefox             Volatile         LSARC/2008/158
                GTK+                Committed        LSARC/2006/202
                libpng              Volatile         LSARC/2006/202

    2.3. Doc Impact:
    
         Man page is needed.
     
    2.4. Packaging & Delivery:
         SUNWw3m (base package)             - application i.e binary, libraries
         SUNWw3m-l10n (localization)        - Localization.

   
    2.5. Dependencies:
         w3m depends on OpenSSL, Firefox, GTK+, and libpng.
        
    2.6. L10N Impact:
         There are string changes. Hence this should be taken care.

    2.7 Security Impact:

        None. 
        


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


From Irene.Huang@sun.com Wed May 28 02:26:50 2008
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m4S9QotE024485
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 28 May 2008 02:26:50 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m4S9QnIT000525
	for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Wed, 28 May 2008 02:26:50 -0700 (PDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K1K00J03NKPVK00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com
 (ORCPT lsarc-ext@sun.com); Wed, 28 May 2008 03:26:49 -0600 (MDT)
Received: from sineb-mail-1.sun.com ([192.18.19.6])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K1K00JI4NKNBU00@brm-avmta-1.central.sun.com> for
 lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed,
 28 May 2008 03:26:48 -0600 (MDT)
Received: from fe-apac-05.sun.com
 (fe-apac-05.sun.com [192.18.19.176] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m4S9R7nv027884	for
 <lsarc-ext@sun.com>; Wed, 28 May 2008 09:27:07 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0K1K00H01NK5D800@mail-apac.sun.com>
 (original mail from Irene.Huang@Sun.COM)
 for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed,
 28 May 2008 17:26:30 +0800 (SGT)
Received: from [129.158.217.138] by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0K1K00MFCNK59VGJ@mail-apac.sun.com>; Wed,
 28 May 2008 17:26:29 +0800 (SGT)
Date: Wed, 28 May 2008 17:27:08 +0800
From: Irene Huang <Irene.Huang@sun.com>
Subject: Re: W3M [LSARC/2008/346 FastTrack timeout 06/03/2008]
In-reply-to: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
Sender: Irene.Huang@sun.com
To: Shi-Ying Irene Huang <sh162551@sac.sfbay.sun.com>
Cc: lsarc-ext@sun.com
Message-id: <1211966828.1484.8.camel@goalie>
MIME-version: 1.0
X-Mailer: Evolution 2.12.2
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
Status: RO
Content-Length: 6955

hi, All 

I am sponsoring this case, setting the time out to be 06/03/2008. 
Additional materials can be found at 

Sun Internal 
http://sac.eng/Archives/CaseLog/arc/LSARC/2008/346/materials/

Will be posted to Opensoaris.org
http://www.opensolaris.org/os/community/arc/caselog/2008/346/

--Irene 
On Tue, 2008-05-27 at 20:44 -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:
> 	 W3M
>     1.2. Name of Document Author/Supplier:
> 	 Author:  Rick Ju
>     1.3  Date of This Document:
> 	27 May, 2008
> 4. Technical Description
> 1. Introduction
>    1.1. Project/Component Working Name:
> 
>         w3m  a text-based WWW browser
> 
>    1.2. Name of Document Author/Supplier:
>         
>         Author:         Rick Ju
>         Sponser:        Irene Huang
> 
>    1.3. Date of This Document:
> 
>         05/11/2008
> 
> 2. Technical Description:
>     2.1. Details:
>      
>      w3m is a text-based web browser as well as a pager like `more' or `less'.
>      With w3m you can browse web pages through a terminal emulator window
>      (xterm, rxvt or something like that).  Moreover, w3m can be used as a
>      text formatting tool which typesets HTML into plain text.
> 
>      w3m has support for tables, frames, SSL connections, color and even inline
>      images on suitable terminals. Generally, it renders pages in a form as true
>      to their original layout as possible.  And W3m is small. Its stripped
>      binary for Sparc is only 260kbyte.
> 
>      w3m locally run cgi scripts to test html output (requires *no* webserver).
>      w3m keystroke compatible with lynx and support the keybindings customize.
>      w3m support SSL through the openssl library. And w3m could support cookies.
> 
>      Table rendering algorithm in w3m
> 
>      HTML table rendering is difficult. Tabular environment of LaTeX is not very
>      difficult, which makes the width of a column either a specified value or
>      the maximum width to put items into it. On the other hand, HTML table
>      renderer has to decide the width of a column so that the entire table can
>      fit into the display appropriately, and fold the contents of the table
>      according to the column width.  Inappropriate column width decision makes
>      the table ugly.  Moreover, table can be nested, which makes the algorithm
>      more complicated.
> 
>      1. First, calculate the maximum and minimum width of each column. The
>         maximum width is the width required to display the column without
>         folding the contents. Generally, it is the length of paragraph
>         delimited by <BR> or <P>. The minimum width is the lower limit
>         to display the contents.  If the column contains the word
>         `internationalization', the minimum width will be 20. If the column
>         contains <pre>..</pre>, the maximum width of the preformatted
>         text will be the minimum width of the column.  2. If the width of
>         the column is specified by WIDTH attribute, fix the column
>         width using that value. If the specified width is smaller than the
>         minimum width of the column, fix the column width to the minimum
>         width.
> 
>      3. Calculate the sum of the maximum width (or fixed width) of each column
>         and check if the sum exceeds the screen width. If it is smaller than
>         screen width, these values are used for width of each column.
> 
>      4. If the sum is larger than the screen width, determine the widths of
>         each column according to the following steps.
>          1. Let W be the screen width subtracted by the sum of widths of
>             fixed-width columns.
>          2. Distribute W into the columns whose width are not decided, in
>             proportion to the logarithm of the maximum width of each column.
>          3. If the distributed width of a column is smaller than the minimum
>             width, then fix the width of the column to the minimum width,
>             and do the distribution again. 
> 
>     In this process, distributed width is proportion to logarithm of maximum width.
> 
>     The algorithm above assumes that the screen width is known. But it is not
>     true for nested table. According the algorithm above, the column width of
>     the outer table have to be known to render the inner table, while the total
>     width of the inner table have to be known to determine the column width of
>     the outer table. If WIDTH attribute exists there are no problems.
>     Otherwise, w3m assumes that the inner table is 0.8 times as wide as the
>     outer table. It works fine, but if there are two tables side by side in an
>     outer table, the width of the outer table always exceeds the screen width.
>     To render this kind of table correctly, one have to render the table once,
>     check the width of outmost table, and then render the entire table again.
>     Netscape might employ this kind of algorithm.
> 
>     2.2. Interfaces:
>            Exported Interfaces
>                 Interface        Classification    Comments
>                 --------------- ---------------    -----------------------
>                 w3m CLI           Volatile         See w3m-help.txt
> 
>                 $HOME/.w3m/config Project Private  w3m Configuration information
>                 SUNWw3m           Uncommited       w3m end-user packaging contains binary, libraries.
>                 SUNWw3m-l10n      Uncommited       Localization.
> 
>         Imported Interfaces
>                 Interface        Classification        Comments
>                 --------------- --------------- -----------------------
>                 HTML/XML/HTTP       Stable           These specs are defined
>                                                      W 3C.org
>                 OpenSSL             Volatile         PSARC/2003/500
>                 Firefox             Volatile         LSARC/2008/158
>                 GTK+                Committed        LSARC/2006/202
>                 libpng              Volatile         LSARC/2006/202
> 
>     2.3. Doc Impact:
>     
>          Man page is needed.
>      
>     2.4. Packaging & Delivery:
>          SUNWw3m (base package)             - application i.e binary, libraries
>          SUNWw3m-l10n (localization)        - Localization.
> 
>    
>     2.5. Dependencies:
>          w3m depends on OpenSSL, Firefox, GTK+, and libpng.
>         
>     2.6. L10N Impact:
>          There are string changes. Hence this should be taken care.
> 
>     2.7 Security Impact:
> 
>         None. 
>         
> 
> 
> 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
> 


From Darren.Moffat@sun.com Wed May 28 02:44:14 2008
Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m4S9iDV4024620
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 28 May 2008 02:44:14 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m4S9iCi6010789
	for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Wed, 28 May 2008 17:44:13 +0800 (SGT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K1K00L01ODN7F00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com
 (ORCPT lsarc-ext@sun.com); Wed, 28 May 2008 03:44:11 -0600 (MDT)
Received: from gmp-eb-inf-1.sun.com ([192.18.6.21])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K1K00JRIODMC610@brm-avmta-1.central.sun.com> for
 lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed,
 28 May 2008 03:44:11 -0600 (MDT)
Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12])
	by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m4S9iA5f005495	for
 <lsarc-ext@sun.com>; Wed, 28 May 2008 09:44:10 +0000 (GMT)
Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0K1K00201N09NL00@fe-emea-10.sun.com>
 (original mail from Darren.Moffat@Sun.COM)
 for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed,
 28 May 2008 10:44:10 +0100 (BST)
Received: from [129.156.173.21] by fe-emea-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0K1K00B0RODCI030@fe-emea-10.sun.com>; Wed,
 28 May 2008 10:44:01 +0100 (BST)
Date: Wed, 28 May 2008 10:43:59 +0100
From: Darren J Moffat <Darren.Moffat@sun.com>
Subject: Re: W3M [LSARC/2008/346 FastTrack timeout 06/03/2008]
In-reply-to: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
Sender: Darren.Moffat@sun.com
To: Shi-Ying Irene Huang <sh162551@sac.sfbay.sun.com>
Cc: lsarc-ext@sun.com
Message-id: <483D295F.9000808@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080507)
Status: RO
Content-Length: 186

Why does this case import Firefox ?

Exactly what from Firefox does it import ?  Surely not the whole thing ?

Are there no use editable files in $HOME/.w3m/config ?

--
Darren J Moffat

From MAILER-DAEMON Wed May 28 10:04:29 2008
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m4SH4Tjg009675
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 28 May 2008 10:04:29 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m4SH4LTh020779
	for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Wed, 28 May 2008 10:04:29 -0700 (PDT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K1L0030R8RFPC00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com
 (ORCPT lsarc-ext@sun.com); Wed, 28 May 2008 10:04:27 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K1L00KXJ8REY070@nwk-avmta-1.sfbay.Sun.COM> for
 lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed,
 28 May 2008 10:04:26 -0700 (PDT)
Received: from xanadu (xanadu.SFBay.Sun.COM [129.146.228.194])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id m4SH4QrC722986; Wed, 28 May 2008 10:04:26 -0700 (PDT)
Date: Wed, 28 May 2008 10:04:30 -0700
From: Dan Price <dp@eng.sun.com>
Subject: Re: W3M [LSARC/2008/346 FastTrack timeout 06/03/2008]
In-reply-to: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
To: Shi-Ying Irene Huang <sh162551@sac.sfbay.sun.com>
Cc: lsarc-ext@sun.com
Message-id: <20080528170425.GA3570@eng.sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-PMX-Version: 5.4.1.325704
References: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
User-Agent: Mutt/1.4.2.1i
Status: RO
Content-Length: 1687

On Tue 27 May 2008 at 08:44PM, 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:
> 	 W3M
>     1.2. Name of Document Author/Supplier:
> 	 Author:  Rick Ju
>     1.3  Date of This Document:
> 	27 May, 2008
> 4. Technical Description
> 1. Introduction
>    1.1. Project/Component Working Name:
> 
>         w3m  a text-based WWW browser

[Insert obligatory plug for 'elinks', which is better.  Oh well.]

Can I assume we're talking about w3m-0.5.2 or higher?

One concern I have is that the last time I built w3m, at least, it
had a dependency on libgc (the Boehm Garbage Collector).  I take
it that this case has a dependency on LSARC/2008/068?
Since libgc was not listed in imported interfaces, I'm confused.
Presumably you will amend the case and remember to record
a package dependency on SUNWlibgc.

Given the use of libpng/gtk, am I to assume that you are enabling the
optional image rendering support?  (--with-imagelib ?)  I'm skeptical
that this is useful, and means that w3m might not be able to be
used on a system which has no X11/GTK packages.

I would also note (although it is not architectural) that libgc has worked
poorly for me on x86, and led me to drop my usage of w3m (after about 6
years) for elinks.


>      Table rendering algorithm in w3m

This text seems entirely out of scope for a case like this.  Also, you
copied it verbatim from the documentation of w3m (doc/STORY.html) without
attribution.  That seems bad.

        -dp

-- 
Daniel Price - Solaris Kernel Engineering - dp@eng.sun.com - blogs.sun.com/dp

From Irene.Huang@sun.com Wed May 28 20:05:53 2008
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m4T35qpu004688
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 28 May 2008 20:05:53 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m4T35hlq019917;
	Thu, 29 May 2008 04:05:51 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K1M000010LRG700@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 28 May 2008 20:05:51 -0700 (PDT)
Received: from sineb-mail-1.sun.com ([192.18.19.6])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K1M00GU10LPLN70@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 28 May 2008 20:05:50 -0700 (PDT)
Received: from fe-apac-06.sun.com
 (fe-apac-06.sun.com [192.18.19.177] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m4T369M6000456; Thu,
 29 May 2008 03:06:09 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0K1M00G010CA0000@mail-apac.sun.com>
 (original mail from Irene.Huang@Sun.COM); Thu, 29 May 2008 11:04:23 +0800 (SGT)
Received: from [129.158.146.126] by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0K1M009660J98FG6@mail-apac.sun.com>; Thu,
 29 May 2008 11:04:22 +0800 (SGT)
Date: Thu, 29 May 2008 11:05:48 +0800
From: Irene Huang <Irene.Huang@sun.com>
Subject: Re: W3M [LSARC/2008/346 FastTrack timeout 06/03/2008]
In-reply-to: <483D295F.9000808@Sun.COM>
Sender: Irene.Huang@sun.com
To: Darren J Moffat <Darren.Moffat@sun.com>
Cc: Shi-Ying Irene Huang <sh162551@sac.sfbay.sun.com>, lsarc-ext@sun.com,
        "tracker-dev@sun.com >> tracker-dev" <tracker-dev@sun.com>
Message-id: <483E1D8C.3000803@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
 <483D295F.9000808@Sun.COM>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
Status: RO
Content-Length: 276

Including the project team in this thread.

--Irene
Darren J Moffat wrote:
> Why does this case import Firefox ?
>
> Exactly what from Firefox does it import ?  Surely not the whole thing ?
>
> Are there no use editable files in $HOME/.w3m/config ?
>
> -- 
> Darren J Moffat


From Irene.Huang@sun.com Wed May 28 20:06:24 2008
Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m4T36NWr004704
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 28 May 2008 20:06:23 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m4T36HUP010894;
	Thu, 29 May 2008 11:06:22 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K1M000010MKIR00@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 28 May 2008 20:06:20 -0700 (PDT)
Received: from sineb-mail-1.sun.com ([192.18.19.6])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K1M00GMF0MJLO80@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 28 May 2008 20:06:20 -0700 (PDT)
Received: from fe-apac-06.sun.com
 (fe-apac-06.sun.com [192.18.19.177] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m4T36cfn000491; Thu,
 29 May 2008 03:06:38 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0K1M00G010CA0000@mail-apac.sun.com>
 (original mail from Irene.Huang@Sun.COM); Thu, 29 May 2008 11:04:52 +0800 (SGT)
Received: from [129.158.146.126] by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0K1M009ZB0K18AKZ@mail-apac.sun.com>; Thu,
 29 May 2008 11:04:50 +0800 (SGT)
Date: Thu, 29 May 2008 11:06:16 +0800
From: Irene Huang <Irene.Huang@sun.com>
Subject: Re: W3M [LSARC/2008/346 FastTrack timeout 06/03/2008]
In-reply-to: <20080528170425.GA3570@eng.sun.com>
Sender: Irene.Huang@sun.com
To: Dan Price <dp@eng.sun.com>
Cc: Shi-Ying Irene Huang <sh162551@sac.sfbay.sun.com>, lsarc-ext@sun.com,
        "tracker-dev@sun.com >> tracker-dev" <tracker-dev@sun.com>
Message-id: <483E1DA8.3070004@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
 <20080528170425.GA3570@eng.sun.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
Status: RO
Content-Length: 1767

Including the project team in this thread.

--Irene
Dan Price wrote:
> On Tue 27 May 2008 at 08:44PM, 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:
>> 	 W3M
>>     1.2. Name of Document Author/Supplier:
>> 	 Author:  Rick Ju
>>     1.3  Date of This Document:
>> 	27 May, 2008
>> 4. Technical Description
>> 1. Introduction
>>    1.1. Project/Component Working Name:
>>
>>         w3m  a text-based WWW browser
>>     
>
> [Insert obligatory plug for 'elinks', which is better.  Oh well.]
>
> Can I assume we're talking about w3m-0.5.2 or higher?
>
> One concern I have is that the last time I built w3m, at least, it
> had a dependency on libgc (the Boehm Garbage Collector).  I take
> it that this case has a dependency on LSARC/2008/068?
> Since libgc was not listed in imported interfaces, I'm confused.
> Presumably you will amend the case and remember to record
> a package dependency on SUNWlibgc.
>
> Given the use of libpng/gtk, am I to assume that you are enabling the
> optional image rendering support?  (--with-imagelib ?)  I'm skeptical
> that this is useful, and means that w3m might not be able to be
> used on a system which has no X11/GTK packages.
>
> I would also note (although it is not architectural) that libgc has worked
> poorly for me on x86, and led me to drop my usage of w3m (after about 6
> years) for elinks.
>
>
>   
>>      Table rendering algorithm in w3m
>>     
>
> This text seems entirely out of scope for a case like this.  Also, you
> copied it verbatim from the documentation of w3m (doc/STORY.html) without
> attribution.  That seems bad.
>
>         -dp
>
>   


From Brian.Cameron@sun.com Wed May 28 21:28:10 2008
Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m4T4SAOq006354
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 28 May 2008 21:28:10 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m4T4S9oj010474
	for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Wed, 28 May 2008 21:28:10 -0700 (PDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K1M00E0D4EXUV00@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com
 (ORCPT lsarc-ext@sun.com); Wed, 28 May 2008 22:28:09 -0600 (MDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K1M00MU74EVW840@brm-avmta-1.central.sun.com> for
 lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed,
 28 May 2008 22:28:07 -0600 (MDT)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m4T4S7pt024503	for
 <lsarc-ext@sun.com>; Thu, 29 May 2008 04:28:07 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0K1M0080148ZLW00@mail-amer.sun.com>
 (original mail from Brian.Cameron@Sun.COM)
 for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed,
 28 May 2008 22:28:07 -0600 (MDT)
Received: from [192.168.7.200] ([98.96.108.134])
 by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28
 2007)) with ESMTPSA id <0K1M00E6W4EUQ2F0@mail-amer.sun.com>; Wed,
 28 May 2008 22:28:07 -0600 (MDT)
Date: Wed, 28 May 2008 23:28:21 -0500
From: Brian Cameron <Brian.Cameron@sun.com>
Subject: Re: W3M [LSARC/2008/346 FastTrack timeout 06/03/2008]
In-reply-to: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
Sender: Brian.Cameron@sun.com
To: Shi-Ying Irene Huang <sh162551@sac.sfbay.sun.com>
Cc: lsarc-ext@sun.com
Message-id: <483E30E5.2030709@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080506)
Status: RO
Content-Length: 7009


Could you explain why W3M is needed on Solaris.  The FastTrack doesn't
seem to indicate what need it fills.  Dan has suggested elinks is a
better text-based web browser.  Did we consider elinks?  What made us
want to integrate w3m instead of other alternatives?

Brian


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:
> 	 W3M
>     1.2. Name of Document Author/Supplier:
> 	 Author:  Rick Ju
>     1.3  Date of This Document:
> 	27 May, 2008
> 4. Technical Description
> 1. Introduction
>    1.1. Project/Component Working Name:
> 
>         w3m  a text-based WWW browser
> 
>    1.2. Name of Document Author/Supplier:
>         
>         Author:         Rick Ju
>         Sponser:        Irene Huang
> 
>    1.3. Date of This Document:
> 
>         05/11/2008
> 
> 2. Technical Description:
>     2.1. Details:
>      
>      w3m is a text-based web browser as well as a pager like `more' or `less'.
>      With w3m you can browse web pages through a terminal emulator window
>      (xterm, rxvt or something like that).  Moreover, w3m can be used as a
>      text formatting tool which typesets HTML into plain text.
> 
>      w3m has support for tables, frames, SSL connections, color and even inline
>      images on suitable terminals. Generally, it renders pages in a form as true
>      to their original layout as possible.  And W3m is small. Its stripped
>      binary for Sparc is only 260kbyte.
> 
>      w3m locally run cgi scripts to test html output (requires *no* webserver).
>      w3m keystroke compatible with lynx and support the keybindings customize.
>      w3m support SSL through the openssl library. And w3m could support cookies.
> 
>      Table rendering algorithm in w3m
> 
>      HTML table rendering is difficult. Tabular environment of LaTeX is not very
>      difficult, which makes the width of a column either a specified value or
>      the maximum width to put items into it. On the other hand, HTML table
>      renderer has to decide the width of a column so that the entire table can
>      fit into the display appropriately, and fold the contents of the table
>      according to the column width.  Inappropriate column width decision makes
>      the table ugly.  Moreover, table can be nested, which makes the algorithm
>      more complicated.
> 
>      1. First, calculate the maximum and minimum width of each column. The
>         maximum width is the width required to display the column without
>         folding the contents. Generally, it is the length of paragraph
>         delimited by <BR> or <P>. The minimum width is the lower limit
>         to display the contents.  If the column contains the word
>         `internationalization', the minimum width will be 20. If the column
>         contains <pre>..</pre>, the maximum width of the preformatted
>         text will be the minimum width of the column.  2. If the width of
>         the column is specified by WIDTH attribute, fix the column
>         width using that value. If the specified width is smaller than the
>         minimum width of the column, fix the column width to the minimum
>         width.
> 
>      3. Calculate the sum of the maximum width (or fixed width) of each column
>         and check if the sum exceeds the screen width. If it is smaller than
>         screen width, these values are used for width of each column.
> 
>      4. If the sum is larger than the screen width, determine the widths of
>         each column according to the following steps.
>          1. Let W be the screen width subtracted by the sum of widths of
>             fixed-width columns.
>          2. Distribute W into the columns whose width are not decided, in
>             proportion to the logarithm of the maximum width of each column.
>          3. If the distributed width of a column is smaller than the minimum
>             width, then fix the width of the column to the minimum width,
>             and do the distribution again. 
> 
>     In this process, distributed width is proportion to logarithm of maximum width.
> 
>     The algorithm above assumes that the screen width is known. But it is not
>     true for nested table. According the algorithm above, the column width of
>     the outer table have to be known to render the inner table, while the total
>     width of the inner table have to be known to determine the column width of
>     the outer table. If WIDTH attribute exists there are no problems.
>     Otherwise, w3m assumes that the inner table is 0.8 times as wide as the
>     outer table. It works fine, but if there are two tables side by side in an
>     outer table, the width of the outer table always exceeds the screen width.
>     To render this kind of table correctly, one have to render the table once,
>     check the width of outmost table, and then render the entire table again.
>     Netscape might employ this kind of algorithm.
> 
>     2.2. Interfaces:
>            Exported Interfaces
>                 Interface        Classification    Comments
>                 --------------- ---------------    -----------------------
>                 w3m CLI           Volatile         See w3m-help.txt
> 
>                 $HOME/.w3m/config Project Private  w3m Configuration information
>                 SUNWw3m           Uncommited       w3m end-user packaging contains binary, libraries.
>                 SUNWw3m-l10n      Uncommited       Localization.
> 
>         Imported Interfaces
>                 Interface        Classification        Comments
>                 --------------- --------------- -----------------------
>                 HTML/XML/HTTP       Stable           These specs are defined
>                                                      W 3C.org
>                 OpenSSL             Volatile         PSARC/2003/500
>                 Firefox             Volatile         LSARC/2008/158
>                 GTK+                Committed        LSARC/2006/202
>                 libpng              Volatile         LSARC/2006/202
> 
>     2.3. Doc Impact:
>     
>          Man page is needed.
>      
>     2.4. Packaging & Delivery:
>          SUNWw3m (base package)             - application i.e binary, libraries
>          SUNWw3m-l10n (localization)        - Localization.
> 
>    
>     2.5. Dependencies:
>          w3m depends on OpenSSL, Firefox, GTK+, and libpng.
>         
>     2.6. L10N Impact:
>          There are string changes. Hence this should be taken care.
> 
>     2.7 Security Impact:
> 
>         None. 
>         
> 
> 
> 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
> 
> _______________________________________________
> opensolaris-arc mailing list
> opensolaris-arc@opensolaris.org


From Harry.Lu@Sun.COM Wed May 28 21:45:51 2008
Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m4T4jojv006492
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 28 May 2008 21:45:50 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m4T4jom7013895;
	Wed, 28 May 2008 21:45:50 -0700 (PDT)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K1M00G0358ED200@nwk-avmta-2.sfbay.sun.com>; Wed,
 28 May 2008 21:45:50 -0700 (PDT)
Received: from sineb-mail-1.sun.com ([192.18.19.6])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K1M00BMM58D3820@nwk-avmta-2.sfbay.sun.com>; Wed,
 28 May 2008 21:45:50 -0700 (PDT)
Received: from fe-apac-06.sun.com
 (fe-apac-06.sun.com [192.18.19.177] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m4T4k8vq007534; Thu,
 29 May 2008 04:46:08 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0K1M00M0153VZN00@mail-apac.sun.com> (original mail from Harry.Lu@Sun.COM)
 ; Thu, 29 May 2008 12:44:22 +0800 (SGT)
Received: from [129.158.217.161] by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0K1M009T355X8AYZ@mail-apac.sun.com>; Thu,
 29 May 2008 12:44:22 +0800 (SGT)
Date: Thu, 29 May 2008 12:47:40 +0800
From: Harry Lu <Harry.Lu@Sun.COM>
Subject: Re: W3M [LSARC/2008/346 FastTrack timeout 06/03/2008]
In-reply-to: <483E30E5.2030709@sun.com>
Sender: Harry.Lu@Sun.COM
To: Brian Cameron <Brian.Cameron@Sun.COM>
Cc: Shi-Ying Irene Huang <sh162551@sac.sfbay.sun.com>, lsarc-ext@Sun.COM,
        tracker-dev <tracker-dev@Sun.COM>
Message-id: <1212036460.4149.23.camel@fulltime>
MIME-version: 1.0
X-Mailer: Evolution 2.22.1.1
Content-type: text/plain
Content-transfer-encoding: 8BIT
X-PMX-Version: 5.4.1.325704
References: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
 <483E30E5.2030709@sun.com>
Status: RO
Content-Length: 7558

﻿Including the project team in this thread.

Harry
On Wed, 2008-05-28 at 23:28 -0500, Brian Cameron wrote:
> Could you explain why W3M is needed on Solaris.  The FastTrack doesn't
> seem to indicate what need it fills.  Dan has suggested elinks is a
> better text-based web browser.  Did we consider elinks?  What made us
> want to integrate w3m instead of other alternatives?
> 
> Brian
> 
> 
> 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:
> > 	 W3M
> >     1.2. Name of Document Author/Supplier:
> > 	 Author:  Rick Ju
> >     1.3  Date of This Document:
> > 	27 May, 2008
> > 4. Technical Description
> > 1. Introduction
> >    1.1. Project/Component Working Name:
> > 
> >         w3m  a text-based WWW browser
> > 
> >    1.2. Name of Document Author/Supplier:
> >         
> >         Author:         Rick Ju
> >         Sponser:        Irene Huang
> > 
> >    1.3. Date of This Document:
> > 
> >         05/11/2008
> > 
> > 2. Technical Description:
> >     2.1. Details:
> >      
> >      w3m is a text-based web browser as well as a pager like `more' or `less'.
> >      With w3m you can browse web pages through a terminal emulator window
> >      (xterm, rxvt or something like that).  Moreover, w3m can be used as a
> >      text formatting tool which typesets HTML into plain text.
> > 
> >      w3m has support for tables, frames, SSL connections, color and even inline
> >      images on suitable terminals. Generally, it renders pages in a form as true
> >      to their original layout as possible.  And W3m is small. Its stripped
> >      binary for Sparc is only 260kbyte.
> > 
> >      w3m locally run cgi scripts to test html output (requires *no* webserver).
> >      w3m keystroke compatible with lynx and support the keybindings customize.
> >      w3m support SSL through the openssl library. And w3m could support cookies.
> > 
> >      Table rendering algorithm in w3m
> > 
> >      HTML table rendering is difficult. Tabular environment of LaTeX is not very
> >      difficult, which makes the width of a column either a specified value or
> >      the maximum width to put items into it. On the other hand, HTML table
> >      renderer has to decide the width of a column so that the entire table can
> >      fit into the display appropriately, and fold the contents of the table
> >      according to the column width.  Inappropriate column width decision makes
> >      the table ugly.  Moreover, table can be nested, which makes the algorithm
> >      more complicated.
> > 
> >      1. First, calculate the maximum and minimum width of each column. The
> >         maximum width is the width required to display the column without
> >         folding the contents. Generally, it is the length of paragraph
> >         delimited by <BR> or <P>. The minimum width is the lower limit
> >         to display the contents.  If the column contains the word
> >         `internationalization', the minimum width will be 20. If the column
> >         contains <pre>..</pre>, the maximum width of the preformatted
> >         text will be the minimum width of the column.  2. If the width of
> >         the column is specified by WIDTH attribute, fix the column
> >         width using that value. If the specified width is smaller than the
> >         minimum width of the column, fix the column width to the minimum
> >         width.
> > 
> >      3. Calculate the sum of the maximum width (or fixed width) of each column
> >         and check if the sum exceeds the screen width. If it is smaller than
> >         screen width, these values are used for width of each column.
> > 
> >      4. If the sum is larger than the screen width, determine the widths of
> >         each column according to the following steps.
> >          1. Let W be the screen width subtracted by the sum of widths of
> >             fixed-width columns.
> >          2. Distribute W into the columns whose width are not decided, in
> >             proportion to the logarithm of the maximum width of each column.
> >          3. If the distributed width of a column is smaller than the minimum
> >             width, then fix the width of the column to the minimum width,
> >             and do the distribution again. 
> > 
> >     In this process, distributed width is proportion to logarithm of maximum width.
> > 
> >     The algorithm above assumes that the screen width is known. But it is not
> >     true for nested table. According the algorithm above, the column width of
> >     the outer table have to be known to render the inner table, while the total
> >     width of the inner table have to be known to determine the column width of
> >     the outer table. If WIDTH attribute exists there are no problems.
> >     Otherwise, w3m assumes that the inner table is 0.8 times as wide as the
> >     outer table. It works fine, but if there are two tables side by side in an
> >     outer table, the width of the outer table always exceeds the screen width.
> >     To render this kind of table correctly, one have to render the table once,
> >     check the width of outmost table, and then render the entire table again.
> >     Netscape might employ this kind of algorithm.
> > 
> >     2.2. Interfaces:
> >            Exported Interfaces
> >                 Interface        Classification    Comments
> >                 --------------- ---------------    -----------------------
> >                 w3m CLI           Volatile         See w3m-help.txt
> > 
> >                 $HOME/.w3m/config Project Private  w3m Configuration information
> >                 SUNWw3m           Uncommited       w3m end-user packaging contains binary, libraries.
> >                 SUNWw3m-l10n      Uncommited       Localization.
> > 
> >         Imported Interfaces
> >                 Interface        Classification        Comments
> >                 --------------- --------------- -----------------------
> >                 HTML/XML/HTTP       Stable           These specs are defined
> >                                                      W 3C.org
> >                 OpenSSL             Volatile         PSARC/2003/500
> >                 Firefox             Volatile         LSARC/2008/158
> >                 GTK+                Committed        LSARC/2006/202
> >                 libpng              Volatile         LSARC/2006/202
> > 
> >     2.3. Doc Impact:
> >     
> >          Man page is needed.
> >      
> >     2.4. Packaging & Delivery:
> >          SUNWw3m (base package)             - application i.e binary, libraries
> >          SUNWw3m-l10n (localization)        - Localization.
> > 
> >    
> >     2.5. Dependencies:
> >          w3m depends on OpenSSL, Firefox, GTK+, and libpng.
> >         
> >     2.6. L10N Impact:
> >          There are string changes. Hence this should be taken care.
> > 
> >     2.7 Security Impact:
> > 
> >         None. 
> >         
> > 
> > 
> > 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
> > 
> > _______________________________________________
> > opensolaris-arc mailing list
> > opensolaris-arc@opensolaris.org
> 
-- 

Harry.Lu@Sun.COM
Solaris Desktop Group, Sun Microsystems
Tel: +86-10-82618200 ext. 82870/ +86-10-62673870
Fax: +86-10-62780969


From Irene.Huang@sun.com Wed May 28 22:03:48 2008
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m4T53mUe007058
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 28 May 2008 22:03:48 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m4T53lVx033662;
	Wed, 28 May 2008 23:03:47 -0600 (MDT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K1M00E0762BCK00@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 28 May 2008 22:03:47 -0700 (PDT)
Received: from sineb-mail-2.sun.com ([192.18.19.7])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K1M00DPV62ALO00@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 28 May 2008 22:03:47 -0700 (PDT)
Received: from fe-apac-05.sun.com
 (fe-apac-05.sun.com [192.18.19.176] (may be forged))
	by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m4T54Ytt014507; Thu,
 29 May 2008 05:04:34 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0K1M00L015XSYT00@mail-apac.sun.com>
 (original mail from Irene.Huang@Sun.COM); Thu, 29 May 2008 13:03:29 +0800 (SGT)
Received: from [129.158.146.126] by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0K1M00MPK61R9M3Y@mail-apac.sun.com>; Thu,
 29 May 2008 13:03:28 +0800 (SGT)
Date: Thu, 29 May 2008 13:03:45 +0800
From: Irene Huang <Irene.Huang@sun.com>
Subject: Re: W3M [LSARC/2008/346 FastTrack timeout 06/03/2008]
In-reply-to: <483E1D8C.3000803@sun.com>
Sender: Irene.Huang@sun.com
To: Irene Huang <Irene.Huang@sun.com>
Cc: Darren J Moffat <Darren.Moffat@sun.com>,
        Shi-Ying Irene Huang <sh162551@sac.sfbay.sun.com>, lsarc-ext@sun.com,
        "tracker-dev@sun.com >> tracker-dev" <tracker-dev@sun.com>,
        Rick Ju <Rick.Ju@sun.com>
Message-id: <483E3931.6050505@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
 <483D295F.9000808@Sun.COM> <483E1D8C.3000803@sun.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
Status: RO
Content-Length: 378

Rick,

Could you please answer the question from Darren?

--Irene
Irene Huang wrote:
> Including the project team in this thread.
>
> --Irene
> Darren J Moffat wrote:
>> Why does this case import Firefox ?
>>
>> Exactly what from Firefox does it import ?  Surely not the whole thing ?
>>
>> Are there no use editable files in $HOME/.w3m/config ?
>>
>> -- 
>> Darren J Moffat
>


From Irene.Huang@sun.com Wed May 28 22:04:43 2008
Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m4T54hgN007074
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 28 May 2008 22:04:43 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m4T54g6N017359;
	Wed, 28 May 2008 22:04:42 -0700 (PDT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K1M00E0363TGS00@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 28 May 2008 22:04:41 -0700 (PDT)
Received: from sineb-mail-2.sun.com ([192.18.19.7])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K1M00DUV63SLO00@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 28 May 2008 22:04:41 -0700 (PDT)
Received: from fe-apac-06.sun.com
 (fe-apac-06.sun.com [192.18.19.177] (may be forged))
	by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m4T55RU0014623; Thu,
 29 May 2008 05:05:27 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0K1M00C015UJ7200@mail-apac.sun.com>
 (original mail from Irene.Huang@Sun.COM); Thu, 29 May 2008 13:03:13 +0800 (SGT)
Received: from [129.158.146.126] by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0K1M0093D61A8A10@mail-apac.sun.com>; Thu,
 29 May 2008 13:03:11 +0800 (SGT)
Date: Thu, 29 May 2008 13:04:36 +0800
From: Irene Huang <Irene.Huang@sun.com>
Subject: Re: W3M [LSARC/2008/346 FastTrack timeout 06/03/2008]
In-reply-to: <483E1DA8.3070004@sun.com>
Sender: Irene.Huang@sun.com
To: Irene Huang <Irene.Huang@sun.com>
Cc: Dan Price <dp@eng.sun.com>,
        Shi-Ying Irene Huang <sh162551@sac.sfbay.sun.com>, lsarc-ext@sun.com,
        "tracker-dev@sun.com >> tracker-dev" <tracker-dev@sun.com>,
        Rick Ju <Rick.Ju@sun.com>
Message-id: <483E3964.2010205@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
 <20080528170425.GA3570@eng.sun.com> <483E1DA8.3070004@sun.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
Status: RO
Content-Length: 1929

Rick,

Could you please answer the question of Dan?

Thanks

--Irene
Irene Huang wrote:
> Including the project team in this thread.
>
> --Irene
> Dan Price wrote:
>> On Tue 27 May 2008 at 08:44PM, 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:
>>>      W3M
>>>     1.2. Name of Document Author/Supplier:
>>>      Author:  Rick Ju
>>>     1.3  Date of This Document:
>>>     27 May, 2008
>>> 4. Technical Description
>>> 1. Introduction
>>>    1.1. Project/Component Working Name:
>>>
>>>         w3m  a text-based WWW browser
>>>     
>>
>> [Insert obligatory plug for 'elinks', which is better.  Oh well.]
>>
>> Can I assume we're talking about w3m-0.5.2 or higher?
>>
>> One concern I have is that the last time I built w3m, at least, it
>> had a dependency on libgc (the Boehm Garbage Collector).  I take
>> it that this case has a dependency on LSARC/2008/068?
>> Since libgc was not listed in imported interfaces, I'm confused.
>> Presumably you will amend the case and remember to record
>> a package dependency on SUNWlibgc.
>>
>> Given the use of libpng/gtk, am I to assume that you are enabling the
>> optional image rendering support?  (--with-imagelib ?)  I'm skeptical
>> that this is useful, and means that w3m might not be able to be
>> used on a system which has no X11/GTK packages.
>>
>> I would also note (although it is not architectural) that libgc has 
>> worked
>> poorly for me on x86, and led me to drop my usage of w3m (after about 6
>> years) for elinks.
>>
>>
>>  
>>>      Table rendering algorithm in w3m
>>>     
>>
>> This text seems entirely out of scope for a case like this.  Also, you
>> copied it verbatim from the documentation of w3m (doc/STORY.html) 
>> without
>> attribution.  That seems bad.
>>
>>         -dp
>>
>>   
>


From Irene.Huang@sun.com Wed May 28 22:05:21 2008
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m4T55L8h007090
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 28 May 2008 22:05:21 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m4T55K8t034342;
	Wed, 28 May 2008 23:05:20 -0600 (MDT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K1M00E0564WLG00@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 28 May 2008 22:05:20 -0700 (PDT)
Received: from sineb-mail-1.sun.com ([192.18.19.6])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K1M00D1164VLL10@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 28 May 2008 22:05:20 -0700 (PDT)
Received: from fe-apac-06.sun.com
 (fe-apac-06.sun.com [192.18.19.177] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m4T55d7a009076; Thu,
 29 May 2008 05:05:39 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0K1M00C015UJ7200@mail-apac.sun.com>
 (original mail from Irene.Huang@Sun.COM); Thu, 29 May 2008 13:03:52 +0800 (SGT)
Received: from [129.158.146.126] by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0K1M0097X62D8A10@mail-apac.sun.com>; Thu,
 29 May 2008 13:03:50 +0800 (SGT)
Date: Thu, 29 May 2008 13:05:16 +0800
From: Irene Huang <Irene.Huang@sun.com>
Subject: Re: W3M [LSARC/2008/346 FastTrack timeout 06/03/2008]
In-reply-to: <483E30E5.2030709@sun.com>
Sender: Irene.Huang@sun.com
To: Brian Cameron <Brian.Cameron@sun.com>
Cc: Shi-Ying Irene Huang <sh162551@sac.sfbay.sun.com>, lsarc-ext@sun.com,
        tracker-dev <tracker-dev@sun.com>, Rick Ju <Rick.Ju@sun.com>
Message-id: <483E398C.2070703@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
 <483E30E5.2030709@sun.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
Status: RO
Content-Length: 7393

Rick,

Could you please answer the question of Brian?

Thanks

--Irene
Brian Cameron wrote:
>
> Could you explain why W3M is needed on Solaris.  The FastTrack doesn't
> seem to indicate what need it fills.  Dan has suggested elinks is a
> better text-based web browser.  Did we consider elinks?  What made us
> want to integrate w3m instead of other alternatives?
>
> Brian
>
>
> 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:
>>      W3M
>>     1.2. Name of Document Author/Supplier:
>>      Author:  Rick Ju
>>     1.3  Date of This Document:
>>     27 May, 2008
>> 4. Technical Description
>> 1. Introduction
>>    1.1. Project/Component Working Name:
>>
>>         w3m  a text-based WWW browser
>>
>>    1.2. Name of Document Author/Supplier:
>>                 Author:         Rick Ju
>>         Sponser:        Irene Huang
>>
>>    1.3. Date of This Document:
>>
>>         05/11/2008
>>
>> 2. Technical Description:
>>     2.1. Details:
>>           w3m is a text-based web browser as well as a pager like 
>> `more' or `less'.
>>      With w3m you can browse web pages through a terminal emulator 
>> window
>>      (xterm, rxvt or something like that).  Moreover, w3m can be used 
>> as a
>>      text formatting tool which typesets HTML into plain text.
>>
>>      w3m has support for tables, frames, SSL connections, color and 
>> even inline
>>      images on suitable terminals. Generally, it renders pages in a 
>> form as true
>>      to their original layout as possible.  And W3m is small. Its 
>> stripped
>>      binary for Sparc is only 260kbyte.
>>
>>      w3m locally run cgi scripts to test html output (requires *no* 
>> webserver).
>>      w3m keystroke compatible with lynx and support the keybindings 
>> customize.
>>      w3m support SSL through the openssl library. And w3m could 
>> support cookies.
>>
>>      Table rendering algorithm in w3m
>>
>>      HTML table rendering is difficult. Tabular environment of LaTeX 
>> is not very
>>      difficult, which makes the width of a column either a specified 
>> value or
>>      the maximum width to put items into it. On the other hand, HTML 
>> table
>>      renderer has to decide the width of a column so that the entire 
>> table can
>>      fit into the display appropriately, and fold the contents of the 
>> table
>>      according to the column width.  Inappropriate column width 
>> decision makes
>>      the table ugly.  Moreover, table can be nested, which makes the 
>> algorithm
>>      more complicated.
>>
>>      1. First, calculate the maximum and minimum width of each 
>> column. The
>>         maximum width is the width required to display the column 
>> without
>>         folding the contents. Generally, it is the length of paragraph
>>         delimited by <BR> or <P>. The minimum width is the lower limit
>>         to display the contents.  If the column contains the word
>>         `internationalization', the minimum width will be 20. If the 
>> column
>>         contains <pre>..</pre>, the maximum width of the preformatted
>>         text will be the minimum width of the column.  2. If the 
>> width of
>>         the column is specified by WIDTH attribute, fix the column
>>         width using that value. If the specified width is smaller 
>> than the
>>         minimum width of the column, fix the column width to the minimum
>>         width.
>>
>>      3. Calculate the sum of the maximum width (or fixed width) of 
>> each column
>>         and check if the sum exceeds the screen width. If it is 
>> smaller than
>>         screen width, these values are used for width of each column.
>>
>>      4. If the sum is larger than the screen width, determine the 
>> widths of
>>         each column according to the following steps.
>>          1. Let W be the screen width subtracted by the sum of widths of
>>             fixed-width columns.
>>          2. Distribute W into the columns whose width are not 
>> decided, in
>>             proportion to the logarithm of the maximum width of each 
>> column.
>>          3. If the distributed width of a column is smaller than the 
>> minimum
>>             width, then fix the width of the column to the minimum 
>> width,
>>             and do the distribution again.
>>     In this process, distributed width is proportion to logarithm of 
>> maximum width.
>>
>>     The algorithm above assumes that the screen width is known. But 
>> it is not
>>     true for nested table. According the algorithm above, the column 
>> width of
>>     the outer table have to be known to render the inner table, while 
>> the total
>>     width of the inner table have to be known to determine the column 
>> width of
>>     the outer table. If WIDTH attribute exists there are no problems.
>>     Otherwise, w3m assumes that the inner table is 0.8 times as wide 
>> as the
>>     outer table. It works fine, but if there are two tables side by 
>> side in an
>>     outer table, the width of the outer table always exceeds the 
>> screen width.
>>     To render this kind of table correctly, one have to render the 
>> table once,
>>     check the width of outmost table, and then render the entire 
>> table again.
>>     Netscape might employ this kind of algorithm.
>>
>>     2.2. Interfaces:
>>            Exported Interfaces
>>                 Interface        Classification    Comments
>>                 --------------- ---------------    
>> -----------------------
>>                 w3m CLI           Volatile         See w3m-help.txt
>>
>>                 $HOME/.w3m/config Project Private  w3m Configuration 
>> information
>>                 SUNWw3m           Uncommited       w3m end-user 
>> packaging contains binary, libraries.
>>                 SUNWw3m-l10n      Uncommited       Localization.
>>
>>         Imported Interfaces
>>                 Interface        Classification        Comments
>>                 --------------- --------------- -----------------------
>>                 HTML/XML/HTTP       Stable           These specs are 
>> defined
>>                                                      W 3C.org
>>                 OpenSSL             Volatile         PSARC/2003/500
>>                 Firefox             Volatile         LSARC/2008/158
>>                 GTK+                Committed        LSARC/2006/202
>>                 libpng              Volatile         LSARC/2006/202
>>
>>     2.3. Doc Impact:
>>              Man page is needed.
>>          2.4. Packaging & Delivery:
>>          SUNWw3m (base package)             - application i.e binary, 
>> libraries
>>          SUNWw3m-l10n (localization)        - Localization.
>>
>>        2.5. Dependencies:
>>          w3m depends on OpenSSL, Firefox, GTK+, and libpng.
>>             2.6. L10N Impact:
>>          There are string changes. Hence this should be taken care.
>>
>>     2.7 Security Impact:
>>
>>         None.        
>>
>> 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
>>
>> _______________________________________________
>> opensolaris-arc mailing list
>> opensolaris-arc@opensolaris.org
>


From Jyri.Virkki@sun.com Wed May 28 22:52:19 2008
Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m4T5qIKK008286
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 28 May 2008 22:52:18 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m4T5qBqb004151;
	Thu, 29 May 2008 13:52:15 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K1M00J018B1MN00@nwk-avmta-2.sfbay.sun.com>; Wed,
 28 May 2008 22:52:13 -0700 (PDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K1M00B7P8B03Q40@nwk-avmta-2.sfbay.sun.com>; Wed,
 28 May 2008 22:52:12 -0700 (PDT)
Received: from dm-usca15-11.red.iplanet.com
 (host-185-56-18-192.iplanet.com [192.18.56.185] (may be forged))
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m4T5qBF8013303; Thu,
 29 May 2008 05:52:11 +0000 (GMT)
Received: from buye.red.iplanet.com (buye [192.18.65.224])
	by dm-usca15-11.red.iplanet.com (8.11.7p1+Sun/8.11.7/IPLANET,v1.2)
 with ESMTP id m4T5qBm01025; Wed, 28 May 2008 22:52:11 -0700 (PDT)
Received: from buye.red.iplanet.com (localhost [127.0.0.1])
	by buye.red.iplanet.com (8.13.7+Sun/8.13.7) with ESMTP id m4T5qBYR009045; Wed,
 28 May 2008 22:52:11 -0700 (PDT)
Received: (from jyri@localhost)
	by buye.red.iplanet.com (8.13.7+Sun/8.13.7/Submit) id m4T5qBBm009044; Wed,
 28 May 2008 22:52:11 -0700 (PDT)
Date: Wed, 28 May 2008 22:52:11 -0700
From: Jyri Virkki <Jyri.Virkki@sun.com>
Subject: Re: W3M [LSARC/2008/346 FastTrack timeout 06/03/2008]
In-reply-to: <1212036460.4149.23.camel@fulltime>
To: Harry Lu <Harry.Lu@sun.com>
Cc: Brian Cameron <Brian.Cameron@sun.com>,
        Shi-Ying Irene Huang <sh162551@sac.sfbay.sun.com>, lsarc-ext@sun.com,
        tracker-dev <tracker-dev@sun.com>
Reply-to: Jyri.Virkki@sun.com
Message-id: <20080529055211.GM4116@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-PMX-Version: 5.4.1.325704
References: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
 <483E30E5.2030709@sun.com> <1212036460.4149.23.camel@fulltime>
User-Agent: Mutt/1.5.11
Status: RO
Content-Length: 874

Harry Lu wrote:
>
> Including the project team in this thread.
> 
> Harry
> On Wed, 2008-05-28 at 23:28 -0500, Brian Cameron wrote:
> > Could you explain why W3M is needed on Solaris.  The FastTrack doesn't

Before this thread devolves into Yet Another Rathole, I suggest moving
that discussion elsewhere[1] as it is Not This Case.

+1 on making elinks available too. But that's Not This Case either.

IMO the directives from management are very clear in that OpenSolaris
is not going to be a 5th class citizen in terms of application
availability vs. Linux anymore. It's not the role of ARC to limit
customers application choices. 

If w3m is architecturally fundamentally broken in some way, let's hear
about that. Otherwise, not.



[1] With /dev/null being a good choice, but maybe lsarc-members if necessary.
-- 
Jyri J. Virkki - jyri.virkki@sun.com - Sun Microsystems

From Rick.Ju@sun.com Wed May 28 23:31:24 2008
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m4T6VOGw010831
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 28 May 2008 23:31:24 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m4T6VNkH021791;
	Wed, 28 May 2008 23:31:23 -0700 (PDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K1M00209A4A2800@brm-avmta-1.central.sun.com>; Thu,
 29 May 2008 00:31:22 -0600 (MDT)
Received: from sineb-mail-1.sun.com ([192.18.19.6])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K1M00MBDA49WE80@brm-avmta-1.central.sun.com>; Thu,
 29 May 2008 00:31:22 -0600 (MDT)
Received: from fe-apac-06.sun.com
 (fe-apac-06.sun.com [192.18.19.177] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m4T6VeSl016563; Thu,
 29 May 2008 06:31:40 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0K1M00M019RRU800@mail-apac.sun.com> (original mail from Rick.Ju@Sun.COM)
 ; Thu, 29 May 2008 14:29:54 +0800 (SGT)
Received: from [129.158.144.90] by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0K1M00966A1T8AB0@mail-apac.sun.com>; Thu,
 29 May 2008 14:29:54 +0800 (SGT)
Date: Thu, 29 May 2008 14:41:55 +0800
From: Rick Ju <Rick.Ju@sun.com>
Subject: Re: W3M [LSARC/2008/346 FastTrack timeout 06/03/2008]
In-reply-to: <483E3931.6050505@sun.com>
Sender: Rick.Ju@sun.com
To: Irene Huang <Irene.Huang@sun.com>
Cc: Darren J Moffat <Darren.Moffat@sun.com>,
        Shi-Ying Irene Huang <sh162551@sac.sfbay.sun.com>, lsarc-ext@sun.com,
        "tracker-dev@sun.com >> tracker-dev" <tracker-dev@sun.com>
Message-id: <483E5033.9070801@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
 <483D295F.9000808@Sun.COM> <483E1D8C.3000803@sun.com>
 <483E3931.6050505@sun.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20071009)
Status: RO
Content-Length: 753

Hi, Darren,

 >> Exactly what from Firefox does it import ?  Surely not the whole 
thing ?

w3m use firefox as its external browser which it could open url if users 
want to. So it depends on the whole firefox.

 >> Are there no use editable files in $HOME/.w3m/config ?
 
   If you mean "user editable", it is a text file and user could edit 
directly.  But mainly it is used by w3m itself. Should this be mentioned 
explicitly?


-rick
 
>> Including the project team in this thread.
>>
>> --Irene
>> Darren J Moffat wrote:
>>> Why does this case import Firefox ?
>>>
>>> Exactly what from Firefox does it import ?  Surely not the whole 
>>> thing ?
>>>
>>> Are there no use editable files in $HOME/.w3m/config ?
>>>
>>> -- 
>>> Darren J Moffat
>>
>


From Rick.Ju@sun.com Wed May 28 23:31:45 2008
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m4T6ViJQ010847
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 28 May 2008 23:31:45 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m4T6VgsZ023818;
	Thu, 29 May 2008 07:31:43 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K1M00103A4UB900@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 28 May 2008 23:31:42 -0700 (PDT)
Received: from sineb-mail-1.sun.com ([192.18.19.6])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K1M00DLTA4TLL90@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 28 May 2008 23:31:42 -0700 (PDT)
Received: from fe-apac-05.sun.com
 (fe-apac-05.sun.com [192.18.19.176] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m4T6W0UC016595; Thu,
 29 May 2008 06:32:00 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0K1M00M019YRY600@mail-apac.sun.com> (original mail from Rick.Ju@Sun.COM)
 ; Thu, 29 May 2008 14:31:23 +0800 (SGT)
Received: from [129.158.144.90] by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0K1M00MCTA4A9M9Y@mail-apac.sun.com>; Thu,
 29 May 2008 14:31:23 +0800 (SGT)
Date: Thu, 29 May 2008 14:42:15 +0800
From: Rick Ju <Rick.Ju@sun.com>
Subject: Re: W3M [LSARC/2008/346 FastTrack timeout 06/03/2008]
In-reply-to: <483E3964.2010205@sun.com>
Sender: Rick.Ju@sun.com
To: Dan Price <dp@eng.sun.com>
Cc: Shi-Ying Irene Huang <sh162551@sac.sfbay.sun.com>, lsarc-ext@sun.com,
        "tracker-dev@sun.com >> tracker-dev" <tracker-dev@sun.com>
Message-id: <483E5047.6050906@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
 <20080528170425.GA3570@eng.sun.com> <483E1DA8.3070004@sun.com>
 <483E3964.2010205@sun.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20071009)
Status: RO
Content-Length: 2652

Hi, Dan,

 >> Can I assume we're talking about w3m-0.5.2 or higher?
 
yes.

 >> Presumably you will amend the case and remember to record
 >> a package dependency on SUNWlibgc.

Thanks. Will fix this.

 >>  Given the use of libpng/gtk, am I to assume that you are enabling the
 >> optional image rendering support?  (--with-imagelib ?)  I'm skeptical
 >> that this is useful, and means that w3m might not be able to be
 >> used on a system which has no X11/GTK packages.

Actually this is enabled by default.

 >> I would also note (although it is not architectural) that libgc has 
worked
 >> poorly for me on x86, and led me to drop my usage of w3m (after about 6
 >> years) for elinks.

We are shipping this because tracker, a desktop search tool, depends on w3m.
I will add this info into materials.

-rick

>> Dan Price wrote:
>>> On Tue 27 May 2008 at 08:44PM, 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:
>>>>      W3M
>>>>     1.2. Name of Document Author/Supplier:
>>>>      Author:  Rick Ju
>>>>     1.3  Date of This Document:
>>>>     27 May, 2008
>>>> 4. Technical Description
>>>> 1. Introduction
>>>>    1.1. Project/Component Working Name:
>>>>
>>>>         w3m  a text-based WWW browser
>>>>     
>>>
>>> [Insert obligatory plug for 'elinks', which is better.  Oh well.]
>>>
>>> Can I assume we're talking about w3m-0.5.2 or higher?
>>>
>>> One concern I have is that the last time I built w3m, at least, it
>>> had a dependency on libgc (the Boehm Garbage Collector).  I take
>>> it that this case has a dependency on LSARC/2008/068?
>>> Since libgc was not listed in imported interfaces, I'm confused.
>>> Presumably you will amend the case and remember to record
>>> a package dependency on SUNWlibgc.
>>>
>>> Given the use of libpng/gtk, am I to assume that you are enabling the
>>> optional image rendering support?  (--with-imagelib ?)  I'm skeptical
>>> that this is useful, and means that w3m might not be able to be
>>> used on a system which has no X11/GTK packages.
>>>
>>> I would also note (although it is not architectural) that libgc has 
>>> worked
>>> poorly for me on x86, and led me to drop my usage of w3m (after about 6
>>> years) for elinks.
>>>
>>>
>>>  
>>>>      Table rendering algorithm in w3m
>>>>     
>>>
>>> This text seems entirely out of scope for a case like this.  Also, you
>>> copied it verbatim from the documentation of w3m (doc/STORY.html) 
>>> without
>>> attribution.  That seems bad.
>>>
>>>         -dp
>>>
>>>   
>>
>


From Rick.Ju@sun.com Wed May 28 23:32:04 2008
Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m4T6W3jQ010891
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 28 May 2008 23:32:04 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m4T6W1OO018528;
	Thu, 29 May 2008 14:32:02 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K1M00103A5EC300@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 28 May 2008 23:32:02 -0700 (PDT)
Received: from sineb-mail-1.sun.com ([192.18.19.6])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K1M00DQ9A5CLP90@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 28 May 2008 23:32:01 -0700 (PDT)
Received: from fe-apac-06.sun.com
 (fe-apac-06.sun.com [192.18.19.177] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m4T6WK0s016630; Thu,
 29 May 2008 06:32:20 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0K1M00M019RRU800@mail-apac.sun.com> (original mail from Rick.Ju@Sun.COM)
 ; Thu, 29 May 2008 14:30:34 +0800 (SGT)
Received: from [129.158.144.90] by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0K1M0092XA2W8G2N@mail-apac.sun.com>; Thu,
 29 May 2008 14:30:34 +0800 (SGT)
Date: Thu, 29 May 2008 14:42:36 +0800
From: Rick Ju <Rick.Ju@sun.com>
Subject: Re: W3M [LSARC/2008/346 FastTrack timeout 06/03/2008]
In-reply-to: <483E398C.2070703@sun.com>
Sender: Rick.Ju@sun.com
To: Brian Cameron <Brian.Cameron@sun.com>
Cc: Shi-Ying Irene Huang <sh162551@sac.sfbay.sun.com>, lsarc-ext@sun.com,
        tracker-dev <tracker-dev@sun.com>
Message-id: <483E505C.6050905@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
 <483E30E5.2030709@sun.com> <483E398C.2070703@sun.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20071009)
Status: RO
Content-Length: 7656

Hi, Brian,

We are shipping this because tracker, a desktop search tool, depends on w3m.
I will add this info into materials.

-rick

>
> Brian Cameron wrote:
>>
>> Could you explain why W3M is needed on Solaris.  The FastTrack doesn't
>> seem to indicate what need it fills.  Dan has suggested elinks is a
>> better text-based web browser.  Did we consider elinks?  What made us
>> want to integrate w3m instead of other alternatives?
>>
>> Brian
>>
>>
>> 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:
>>>      W3M
>>>     1.2. Name of Document Author/Supplier:
>>>      Author:  Rick Ju
>>>     1.3  Date of This Document:
>>>     27 May, 2008
>>> 4. Technical Description
>>> 1. Introduction
>>>    1.1. Project/Component Working Name:
>>>
>>>         w3m  a text-based WWW browser
>>>
>>>    1.2. Name of Document Author/Supplier:
>>>                 Author:         Rick Ju
>>>         Sponser:        Irene Huang
>>>
>>>    1.3. Date of This Document:
>>>
>>>         05/11/2008
>>>
>>> 2. Technical Description:
>>>     2.1. Details:
>>>           w3m is a text-based web browser as well as a pager like 
>>> `more' or `less'.
>>>      With w3m you can browse web pages through a terminal emulator 
>>> window
>>>      (xterm, rxvt or something like that).  Moreover, w3m can be 
>>> used as a
>>>      text formatting tool which typesets HTML into plain text.
>>>
>>>      w3m has support for tables, frames, SSL connections, color and 
>>> even inline
>>>      images on suitable terminals. Generally, it renders pages in a 
>>> form as true
>>>      to their original layout as possible.  And W3m is small. Its 
>>> stripped
>>>      binary for Sparc is only 260kbyte.
>>>
>>>      w3m locally run cgi scripts to test html output (requires *no* 
>>> webserver).
>>>      w3m keystroke compatible with lynx and support the keybindings 
>>> customize.
>>>      w3m support SSL through the openssl library. And w3m could 
>>> support cookies.
>>>
>>>      Table rendering algorithm in w3m
>>>
>>>      HTML table rendering is difficult. Tabular environment of LaTeX 
>>> is not very
>>>      difficult, which makes the width of a column either a specified 
>>> value or
>>>      the maximum width to put items into it. On the other hand, HTML 
>>> table
>>>      renderer has to decide the width of a column so that the entire 
>>> table can
>>>      fit into the display appropriately, and fold the contents of 
>>> the table
>>>      according to the column width.  Inappropriate column width 
>>> decision makes
>>>      the table ugly.  Moreover, table can be nested, which makes the 
>>> algorithm
>>>      more complicated.
>>>
>>>      1. First, calculate the maximum and minimum width of each 
>>> column. The
>>>         maximum width is the width required to display the column 
>>> without
>>>         folding the contents. Generally, it is the length of paragraph
>>>         delimited by <BR> or <P>. The minimum width is the lower limit
>>>         to display the contents.  If the column contains the word
>>>         `internationalization', the minimum width will be 20. If the 
>>> column
>>>         contains <pre>..</pre>, the maximum width of the preformatted
>>>         text will be the minimum width of the column.  2. If the 
>>> width of
>>>         the column is specified by WIDTH attribute, fix the column
>>>         width using that value. If the specified width is smaller 
>>> than the
>>>         minimum width of the column, fix the column width to the 
>>> minimum
>>>         width.
>>>
>>>      3. Calculate the sum of the maximum width (or fixed width) of 
>>> each column
>>>         and check if the sum exceeds the screen width. If it is 
>>> smaller than
>>>         screen width, these values are used for width of each column.
>>>
>>>      4. If the sum is larger than the screen width, determine the 
>>> widths of
>>>         each column according to the following steps.
>>>          1. Let W be the screen width subtracted by the sum of 
>>> widths of
>>>             fixed-width columns.
>>>          2. Distribute W into the columns whose width are not 
>>> decided, in
>>>             proportion to the logarithm of the maximum width of each 
>>> column.
>>>          3. If the distributed width of a column is smaller than the 
>>> minimum
>>>             width, then fix the width of the column to the minimum 
>>> width,
>>>             and do the distribution again.
>>>     In this process, distributed width is proportion to logarithm of 
>>> maximum width.
>>>
>>>     The algorithm above assumes that the screen width is known. But 
>>> it is not
>>>     true for nested table. According the algorithm above, the column 
>>> width of
>>>     the outer table have to be known to render the inner table, 
>>> while the total
>>>     width of the inner table have to be known to determine the 
>>> column width of
>>>     the outer table. If WIDTH attribute exists there are no problems.
>>>     Otherwise, w3m assumes that the inner table is 0.8 times as wide 
>>> as the
>>>     outer table. It works fine, but if there are two tables side by 
>>> side in an
>>>     outer table, the width of the outer table always exceeds the 
>>> screen width.
>>>     To render this kind of table correctly, one have to render the 
>>> table once,
>>>     check the width of outmost table, and then render the entire 
>>> table again.
>>>     Netscape might employ this kind of algorithm.
>>>
>>>     2.2. Interfaces:
>>>            Exported Interfaces
>>>                 Interface        Classification    Comments
>>>                 --------------- ---------------    
>>> -----------------------
>>>                 w3m CLI           Volatile         See w3m-help.txt
>>>
>>>                 $HOME/.w3m/config Project Private  w3m Configuration 
>>> information
>>>                 SUNWw3m           Uncommited       w3m end-user 
>>> packaging contains binary, libraries.
>>>                 SUNWw3m-l10n      Uncommited       Localization.
>>>
>>>         Imported Interfaces
>>>                 Interface        Classification        Comments
>>>                 --------------- --------------- -----------------------
>>>                 HTML/XML/HTTP       Stable           These specs are 
>>> defined
>>>                                                      W 3C.org
>>>                 OpenSSL             Volatile         PSARC/2003/500
>>>                 Firefox             Volatile         LSARC/2008/158
>>>                 GTK+                Committed        LSARC/2006/202
>>>                 libpng              Volatile         LSARC/2006/202
>>>
>>>     2.3. Doc Impact:
>>>              Man page is needed.
>>>          2.4. Packaging & Delivery:
>>>          SUNWw3m (base package)             - application i.e 
>>> binary, libraries
>>>          SUNWw3m-l10n (localization)        - Localization.
>>>
>>>        2.5. Dependencies:
>>>          w3m depends on OpenSSL, Firefox, GTK+, and libpng.
>>>             2.6. L10N Impact:
>>>          There are string changes. Hence this should be taken care.
>>>
>>>     2.7 Security Impact:
>>>
>>>         None.       
>>> 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
>>>
>>> _______________________________________________
>>> opensolaris-arc mailing list
>>> opensolaris-arc@opensolaris.org
>>
>


From Irene.Huang@Sun.COM Sun Jun  1 22:59:14 2008
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m525xECK024219
	for <LSARC-ext@sac.sfbay.sun.com>; Sun, 1 Jun 2008 22:59:14 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m525xCTq003356;
	Mon, 2 Jun 2008 06:59:13 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K1T00G01NAOCV00@nwk-avmta-2.sfbay.sun.com>; Sun,
 01 Jun 2008 22:59:12 -0700 (PDT)
Received: from sineb-mail-1.sun.com ([192.18.19.6])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K1T00MP8NAMGKB0@nwk-avmta-2.sfbay.sun.com>; Sun,
 01 Jun 2008 22:59:11 -0700 (PDT)
Received: from fe-apac-06.sun.com
 (fe-apac-06.sun.com [192.18.19.177] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m525xWNR026519; Mon,
 02 Jun 2008 05:59:32 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0K1T00H01N79IA00@mail-apac.sun.com>
 (original mail from Irene.Huang@Sun.COM); Mon, 02 Jun 2008 13:57:40 +0800 (SGT)
Received: from [129.158.217.138] by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0K1T009QNN808A5A@mail-apac.sun.com>; Mon,
 02 Jun 2008 13:57:37 +0800 (SGT)
Date: Mon, 02 Jun 2008 13:59:27 +0800
From: Irene Huang <Irene.Huang@Sun.COM>
Subject: Re: W3M [LSARC/2008/346 FastTrack timeout 06/03/2008]
In-reply-to: <483E505C.6050905@sun.com>
Sender: Irene.Huang@Sun.COM
To: Rick Ju <Rick.Ju@Sun.COM>
Cc: Brian Cameron <Brian.Cameron@Sun.COM>,
        Shi-Ying Irene Huang <sh162551@sac.sfbay.sun.com>, lsarc-ext@Sun.COM,
        tracker-dev <tracker-dev@Sun.COM>
Message-id: <1212386367.3368.68.camel@goalie>
MIME-version: 1.0
X-Mailer: Evolution 2.12.2
Content-type: text/plain
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
 <483E30E5.2030709@sun.com> <483E398C.2070703@sun.com>
 <483E505C.6050905@sun.com>
Status: RO
Content-Length: 8257

Hi, all 

If there's any issues with this case, please reply with an email. If
not, I am closing this case tomorrow as approved. 

Thanks 

--Irene
On Thu, 2008-05-29 at 14:42 +0800, Rick Ju wrote:
> Hi, Brian,
> 
> We are shipping this because tracker, a desktop search tool, depends on w3m.
> I will add this info into materials.
> 
> -rick
> 
> >
> > Brian Cameron wrote:
> >>
> >> Could you explain why W3M is needed on Solaris.  The FastTrack doesn't
> >> seem to indicate what need it fills.  Dan has suggested elinks is a
> >> better text-based web browser.  Did we consider elinks?  What made us
> >> want to integrate w3m instead of other alternatives?
> >>
> >> Brian
> >>
> >>
> >> 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:
> >>>      W3M
> >>>     1.2. Name of Document Author/Supplier:
> >>>      Author:  Rick Ju
> >>>     1.3  Date of This Document:
> >>>     27 May, 2008
> >>> 4. Technical Description
> >>> 1. Introduction
> >>>    1.1. Project/Component Working Name:
> >>>
> >>>         w3m  a text-based WWW browser
> >>>
> >>>    1.2. Name of Document Author/Supplier:
> >>>                 Author:         Rick Ju
> >>>         Sponser:        Irene Huang
> >>>
> >>>    1.3. Date of This Document:
> >>>
> >>>         05/11/2008
> >>>
> >>> 2. Technical Description:
> >>>     2.1. Details:
> >>>           w3m is a text-based web browser as well as a pager like 
> >>> `more' or `less'.
> >>>      With w3m you can browse web pages through a terminal emulator 
> >>> window
> >>>      (xterm, rxvt or something like that).  Moreover, w3m can be 
> >>> used as a
> >>>      text formatting tool which typesets HTML into plain text.
> >>>
> >>>      w3m has support for tables, frames, SSL connections, color and 
> >>> even inline
> >>>      images on suitable terminals. Generally, it renders pages in a 
> >>> form as true
> >>>      to their original layout as possible.  And W3m is small. Its 
> >>> stripped
> >>>      binary for Sparc is only 260kbyte.
> >>>
> >>>      w3m locally run cgi scripts to test html output (requires *no* 
> >>> webserver).
> >>>      w3m keystroke compatible with lynx and support the keybindings 
> >>> customize.
> >>>      w3m support SSL through the openssl library. And w3m could 
> >>> support cookies.
> >>>
> >>>      Table rendering algorithm in w3m
> >>>
> >>>      HTML table rendering is difficult. Tabular environment of LaTeX 
> >>> is not very
> >>>      difficult, which makes the width of a column either a specified 
> >>> value or
> >>>      the maximum width to put items into it. On the other hand, HTML 
> >>> table
> >>>      renderer has to decide the width of a column so that the entire 
> >>> table can
> >>>      fit into the display appropriately, and fold the contents of 
> >>> the table
> >>>      according to the column width.  Inappropriate column width 
> >>> decision makes
> >>>      the table ugly.  Moreover, table can be nested, which makes the 
> >>> algorithm
> >>>      more complicated.
> >>>
> >>>      1. First, calculate the maximum and minimum width of each 
> >>> column. The
> >>>         maximum width is the width required to display the column 
> >>> without
> >>>         folding the contents. Generally, it is the length of paragraph
> >>>         delimited by <BR> or <P>. The minimum width is the lower limit
> >>>         to display the contents.  If the column contains the word
> >>>         `internationalization', the minimum width will be 20. If the 
> >>> column
> >>>         contains <pre>..</pre>, the maximum width of the preformatted
> >>>         text will be the minimum width of the column.  2. If the 
> >>> width of
> >>>         the column is specified by WIDTH attribute, fix the column
> >>>         width using that value. If the specified width is smaller 
> >>> than the
> >>>         minimum width of the column, fix the column width to the 
> >>> minimum
> >>>         width.
> >>>
> >>>      3. Calculate the sum of the maximum width (or fixed width) of 
> >>> each column
> >>>         and check if the sum exceeds the screen width. If it is 
> >>> smaller than
> >>>         screen width, these values are used for width of each column.
> >>>
> >>>      4. If the sum is larger than the screen width, determine the 
> >>> widths of
> >>>         each column according to the following steps.
> >>>          1. Let W be the screen width subtracted by the sum of 
> >>> widths of
> >>>             fixed-width columns.
> >>>          2. Distribute W into the columns whose width are not 
> >>> decided, in
> >>>             proportion to the logarithm of the maximum width of each 
> >>> column.
> >>>          3. If the distributed width of a column is smaller than the 
> >>> minimum
> >>>             width, then fix the width of the column to the minimum 
> >>> width,
> >>>             and do the distribution again.
> >>>     In this process, distributed width is proportion to logarithm of 
> >>> maximum width.
> >>>
> >>>     The algorithm above assumes that the screen width is known. But 
> >>> it is not
> >>>     true for nested table. According the algorithm above, the column 
> >>> width of
> >>>     the outer table have to be known to render the inner table, 
> >>> while the total
> >>>     width of the inner table have to be known to determine the 
> >>> column width of
> >>>     the outer table. If WIDTH attribute exists there are no problems.
> >>>     Otherwise, w3m assumes that the inner table is 0.8 times as wide 
> >>> as the
> >>>     outer table. It works fine, but if there are two tables side by 
> >>> side in an
> >>>     outer table, the width of the outer table always exceeds the 
> >>> screen width.
> >>>     To render this kind of table correctly, one have to render the 
> >>> table once,
> >>>     check the width of outmost table, and then render the entire 
> >>> table again.
> >>>     Netscape might employ this kind of algorithm.
> >>>
> >>>     2.2. Interfaces:
> >>>            Exported Interfaces
> >>>                 Interface        Classification    Comments
> >>>                 --------------- ---------------    
> >>> -----------------------
> >>>                 w3m CLI           Volatile         See w3m-help.txt
> >>>
> >>>                 $HOME/.w3m/config Project Private  w3m Configuration 
> >>> information
> >>>                 SUNWw3m           Uncommited       w3m end-user 
> >>> packaging contains binary, libraries.
> >>>                 SUNWw3m-l10n      Uncommited       Localization.
> >>>
> >>>         Imported Interfaces
> >>>                 Interface        Classification        Comments
> >>>                 --------------- --------------- -----------------------
> >>>                 HTML/XML/HTTP       Stable           These specs are 
> >>> defined
> >>>                                                      W 3C.org
> >>>                 OpenSSL             Volatile         PSARC/2003/500
> >>>                 Firefox             Volatile         LSARC/2008/158
> >>>                 GTK+                Committed        LSARC/2006/202
> >>>                 libpng              Volatile         LSARC/2006/202
> >>>
> >>>     2.3. Doc Impact:
> >>>              Man page is needed.
> >>>          2.4. Packaging & Delivery:
> >>>          SUNWw3m (base package)             - application i.e 
> >>> binary, libraries
> >>>          SUNWw3m-l10n (localization)        - Localization.
> >>>
> >>>        2.5. Dependencies:
> >>>          w3m depends on OpenSSL, Firefox, GTK+, and libpng.
> >>>             2.6. L10N Impact:
> >>>          There are string changes. Hence this should be taken care.
> >>>
> >>>     2.7 Security Impact:
> >>>
> >>>         None.       
> >>> 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
> >>>
> >>> _______________________________________________
> >>> opensolaris-arc mailing list
> >>> opensolaris-arc@opensolaris.org
> >>
> >
> 


From Irene.Huang@SUN.COM Wed Jun  4 03:12:52 2008
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m54ACqEA010748
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 4 Jun 2008 03:12:52 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id m54ACnY3028469;
	Wed, 4 Jun 2008 03:12:51 -0700 (PDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K1X00I05ODF9T00@brm-avmta-1.central.sun.com>; Wed,
 04 Jun 2008 04:12:51 -0600 (MDT)
Received: from sineb-mail-1.sun.com ([192.18.19.6])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K1X0091DODDFD60@brm-avmta-1.central.sun.com>; Wed,
 04 Jun 2008 04:12:50 -0600 (MDT)
Received: from fe-apac-05.sun.com
 (fe-apac-05.sun.com [192.18.19.176] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m54ADBPa027958; Wed,
 04 Jun 2008 10:13:11 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0K1X00A01O9RXD00@mail-apac.sun.com>
 (original mail from Irene.Huang@Sun.COM); Wed, 04 Jun 2008 18:12:30 +0800 (SGT)
Received: from [129.158.146.215] by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0K1X007NROCTXJ4F@mail-apac.sun.com>; Wed,
 04 Jun 2008 18:12:30 +0800 (SGT)
Date: Wed, 04 Jun 2008 18:12:47 +0800
From: Irene Huang <Irene.Huang@SUN.COM>
Subject: Re: W3M [LSARC/2008/346 FastTrack timeout 06/03/2008]
In-reply-to: <1212386367.3368.68.camel@goalie>
Sender: Irene.Huang@SUN.COM
To: Irene Huang <Irene.Huang@SUN.COM>
Cc: Rick Ju <Rick.Ju@SUN.COM>, Brian Cameron <Brian.Cameron@SUN.COM>,
        Shi-Ying Irene Huang <sh162551@sac.sfbay.sun.com>, lsarc-ext@SUN.COM,
        tracker-dev <tracker-dev@SUN.COM>
Message-id: <48466A9F.20007@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200805280344.m4S3ilnh015561@sac.sfbay.sun.com>
 <483E30E5.2030709@sun.com> <483E398C.2070703@sun.com>
 <483E505C.6050905@sun.com> <1212386367.3368.68.camel@goalie>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
Status: RO
Content-Length: 8641

Closing as approved

Newest version of proposal at
http://sac.eng/Archives/CaseLog/arc/LSARC/2008/346/w3m-proposal-v2.txt
a diff from the old version is at
http://sac.eng/Archives/CaseLog/arc/LSARC/2008/346/w3m-proposal.diff

OR at

http://www.opensolaris.org/os/community/arc/caselog/2008/346/

--Irene

Irene Huang wrote:
> Hi, all 
>
> If there's any issues with this case, please reply with an email. If
> not, I am closing this case tomorrow as approved. 
>
> Thanks 
>
> --Irene
> On Thu, 2008-05-29 at 14:42 +0800, Rick Ju wrote:
>   
>> Hi, Brian,
>>
>> We are shipping this because tracker, a desktop search tool, depends on w3m.
>> I will add this info into materials.
>>
>> -rick
>>
>>     
>>> Brian Cameron wrote:
>>>       
>>>> Could you explain why W3M is needed on Solaris.  The FastTrack doesn't
>>>> seem to indicate what need it fills.  Dan has suggested elinks is a
>>>> better text-based web browser.  Did we consider elinks?  What made us
>>>> want to integrate w3m instead of other alternatives?
>>>>
>>>> Brian
>>>>
>>>>
>>>> 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:
>>>>>      W3M
>>>>>     1.2. Name of Document Author/Supplier:
>>>>>      Author:  Rick Ju
>>>>>     1.3  Date of This Document:
>>>>>     27 May, 2008
>>>>> 4. Technical Description
>>>>> 1. Introduction
>>>>>    1.1. Project/Component Working Name:
>>>>>
>>>>>         w3m  a text-based WWW browser
>>>>>
>>>>>    1.2. Name of Document Author/Supplier:
>>>>>                 Author:         Rick Ju
>>>>>         Sponser:        Irene Huang
>>>>>
>>>>>    1.3. Date of This Document:
>>>>>
>>>>>         05/11/2008
>>>>>
>>>>> 2. Technical Description:
>>>>>     2.1. Details:
>>>>>           w3m is a text-based web browser as well as a pager like 
>>>>> `more' or `less'.
>>>>>      With w3m you can browse web pages through a terminal emulator 
>>>>> window
>>>>>      (xterm, rxvt or something like that).  Moreover, w3m can be 
>>>>> used as a
>>>>>      text formatting tool which typesets HTML into plain text.
>>>>>
>>>>>      w3m has support for tables, frames, SSL connections, color and 
>>>>> even inline
>>>>>      images on suitable terminals. Generally, it renders pages in a 
>>>>> form as true
>>>>>      to their original layout as possible.  And W3m is small. Its 
>>>>> stripped
>>>>>      binary for Sparc is only 260kbyte.
>>>>>
>>>>>      w3m locally run cgi scripts to test html output (requires *no* 
>>>>> webserver).
>>>>>      w3m keystroke compatible with lynx and support the keybindings 
>>>>> customize.
>>>>>      w3m support SSL through the openssl library. And w3m could 
>>>>> support cookies.
>>>>>
>>>>>      Table rendering algorithm in w3m
>>>>>
>>>>>      HTML table rendering is difficult. Tabular environment of LaTeX 
>>>>> is not very
>>>>>      difficult, which makes the width of a column either a specified 
>>>>> value or
>>>>>      the maximum width to put items into it. On the other hand, HTML 
>>>>> table
>>>>>      renderer has to decide the width of a column so that the entire 
>>>>> table can
>>>>>      fit into the display appropriately, and fold the contents of 
>>>>> the table
>>>>>      according to the column width.  Inappropriate column width 
>>>>> decision makes
>>>>>      the table ugly.  Moreover, table can be nested, which makes the 
>>>>> algorithm
>>>>>      more complicated.
>>>>>
>>>>>      1. First, calculate the maximum and minimum width of each 
>>>>> column. The
>>>>>         maximum width is the width required to display the column 
>>>>> without
>>>>>         folding the contents. Generally, it is the length of paragraph
>>>>>         delimited by <BR> or <P>. The minimum width is the lower limit
>>>>>         to display the contents.  If the column contains the word
>>>>>         `internationalization', the minimum width will be 20. If the 
>>>>> column
>>>>>         contains <pre>..</pre>, the maximum width of the preformatted
>>>>>         text will be the minimum width of the column.  2. If the 
>>>>> width of
>>>>>         the column is specified by WIDTH attribute, fix the column
>>>>>         width using that value. If the specified width is smaller 
>>>>> than the
>>>>>         minimum width of the column, fix the column width to the 
>>>>> minimum
>>>>>         width.
>>>>>
>>>>>      3. Calculate the sum of the maximum width (or fixed width) of 
>>>>> each column
>>>>>         and check if the sum exceeds the screen width. If it is 
>>>>> smaller than
>>>>>         screen width, these values are used for width of each column.
>>>>>
>>>>>      4. If the sum is larger than the screen width, determine the 
>>>>> widths of
>>>>>         each column according to the following steps.
>>>>>          1. Let W be the screen width subtracted by the sum of 
>>>>> widths of
>>>>>             fixed-width columns.
>>>>>          2. Distribute W into the columns whose width are not 
>>>>> decided, in
>>>>>             proportion to the logarithm of the maximum width of each 
>>>>> column.
>>>>>          3. If the distributed width of a column is smaller than the 
>>>>> minimum
>>>>>             width, then fix the width of the column to the minimum 
>>>>> width,
>>>>>             and do the distribution again.
>>>>>     In this process, distributed width is proportion to logarithm of 
>>>>> maximum width.
>>>>>
>>>>>     The algorithm above assumes that the screen width is known. But 
>>>>> it is not
>>>>>     true for nested table. According the algorithm above, the column 
>>>>> width of
>>>>>     the outer table have to be known to render the inner table, 
>>>>> while the total
>>>>>     width of the inner table have to be known to determine the 
>>>>> column width of
>>>>>     the outer table. If WIDTH attribute exists there are no problems.
>>>>>     Otherwise, w3m assumes that the inner table is 0.8 times as wide 
>>>>> as the
>>>>>     outer table. It works fine, but if there are two tables side by 
>>>>> side in an
>>>>>     outer table, the width of the outer table always exceeds the 
>>>>> screen width.
>>>>>     To render this kind of table correctly, one have to render the 
>>>>> table once,
>>>>>     check the width of outmost table, and then render the entire 
>>>>> table again.
>>>>>     Netscape might employ this kind of algorithm.
>>>>>
>>>>>     2.2. Interfaces:
>>>>>            Exported Interfaces
>>>>>                 Interface        Classification    Comments
>>>>>                 --------------- ---------------    
>>>>> -----------------------
>>>>>                 w3m CLI           Volatile         See w3m-help.txt
>>>>>
>>>>>                 $HOME/.w3m/config Project Private  w3m Configuration 
>>>>> information
>>>>>                 SUNWw3m           Uncommited       w3m end-user 
>>>>> packaging contains binary, libraries.
>>>>>                 SUNWw3m-l10n      Uncommited       Localization.
>>>>>
>>>>>         Imported Interfaces
>>>>>                 Interface        Classification        Comments
>>>>>                 --------------- --------------- -----------------------
>>>>>                 HTML/XML/HTTP       Stable           These specs are 
>>>>> defined
>>>>>                                                      W 3C.org
>>>>>                 OpenSSL             Volatile         PSARC/2003/500
>>>>>                 Firefox             Volatile         LSARC/2008/158
>>>>>                 GTK+                Committed        LSARC/2006/202
>>>>>                 libpng              Volatile         LSARC/2006/202
>>>>>
>>>>>     2.3. Doc Impact:
>>>>>              Man page is needed.
>>>>>          2.4. Packaging & Delivery:
>>>>>          SUNWw3m (base package)             - application i.e 
>>>>> binary, libraries
>>>>>          SUNWw3m-l10n (localization)        - Localization.
>>>>>
>>>>>        2.5. Dependencies:
>>>>>          w3m depends on OpenSSL, Firefox, GTK+, and libpng.
>>>>>             2.6. L10N Impact:
>>>>>          There are string changes. Hence this should be taken care.
>>>>>
>>>>>     2.7 Security Impact:
>>>>>
>>>>>         None.       
>>>>> 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
>>>>>
>>>>> _______________________________________________
>>>>> opensolaris-arc mailing list
>>>>> opensolaris-arc@opensolaris.org
>>>>>           
>
>   


