From sacadmin Mon Jul  7 17:41:25 2008
Received: from almas.sfbay.sun.com (almas.SFBay.Sun.COM [129.146.106.93])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m680fPfY006790;
	Mon, 7 Jul 2008 17:41:25 -0700 (PDT)
Received: from almas.sfbay.sun.com (localhost [127.0.0.1])
	by almas.sfbay.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m680fPi2022236;
	Mon, 7 Jul 2008 17:41:25 -0700 (PDT)
Received: (from alanc@localhost)
	by almas.sfbay.sun.com (8.14.2+Sun/8.14.2/Submit) id m680fP8B022232;
	Mon, 7 Jul 2008 17:41:25 -0700 (PDT)
Date: Mon, 7 Jul 2008 17:41:25 -0700 (PDT)
Message-Id: <200807080041.m680fP8B022232@almas.sfbay.sun.com>
From: Alan Coopersmith <alan.coopersmith@Sun.COM>
To: LSARC@sac.sfbay.sun.com
Cc: Padraig.Obriain@Sun.COM
Subject: GNU Troff (groff) [LSARC/2008/425 FastTrack timeout 07/14/2008]
Status: RO
Content-Length: 11784

I am sponsoring this fasttrack for Padraig O'Briain of the Desktop team.
The timeout is set for one week from today, Monday July 14, and the case
requests a patch release binding as it only introduces new commands.

        -Alan Coopersmith-           alan.coopersmith@sun.com
         Sun Microsystems, Inc. - X Window System Engineering

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:
	 GNU Troff (groff)
    1.2. Name of Document Author/Supplier:
	 Author:  Padraig O'Briain
    1.3  Date of This Document:
	07 July, 2008
4. Technical Description

    4.1. Details:

       The groff (GNU Troff) software is a typesetting package which 
       reads plain text mixed with formatting commands and produces 
       formatted output.

       It is a GNU implementation of troff. It supports GNU extensions
       which are not supported by troff.

       Since `groff' provides such low-level facilities, it can be quite
       difficult to use by itself.  However, `groff' provides a "macro"
       facility to specify how certain routine operations (e.g. starting
       paragraphs, printing headers and footers, etc.)  should be done.  These
       macros can be collected together into a "macro package". 

       groff belongs to an older generation of document preparation 
       systems, which operate more like compilers than the more recent 
       interactive WYSIWYG systems.  groff and its contemporary counterpart,
       TeX, both work using a "batch" paradigm: The input (or "source") 
       files are normal text files with embedded formatting commands.  
       These files can then be processed by groff to produce a typeset 
       document on a variety of devices.

       Likewise, groff should not be confused with a "word processor",
       since that term connotes an integrated system that includes an editor
       and a text formatter.  Also, many word processors follow the WYSIWYG
       paradigm discussed earlier.

       Although WYSIWYG systems may be easier to use, they have a number of
       disadvantages compared to troff:

       * They must be used on a graphics display to work on a document.
       * Most of the WYSIWYG systems are either non-free or are not very
         portable.
       * troff is firmly entrenched in all UNIX systems.
       * It is difficult to have a wide range of capabilities available
         within the confines of a GUI/window system.
       * It is more difficult to make global changes to a document.
         "GUIs normally make it simple to accomplish simple actions and
         impossible to accomplish complex actions."  -Doug Gwyn (22/Jun/91
         in `comp.unix.wizards')

    4.2. Bug/RFE Number(s):

        None.

    4.3. In Scope:

        See above.

    4.4. Out of Scope:

        See above.

    4.5. Interfaces:

        --------------------------------------------------------------------
        Exported                            Stability     Comments                
        --------------------------------------------------------------------
        SUNWgroff                           Uncommitted   Package name

         The following are all              Uncommitted

        /usr/bin/addftinfo                  
        /usr/bin/afmtodit                  
        /usr/bin/eqn2graph                
        /usr/bin/geqn                    
        /usr/bin/ggrn                   
        /usr/bin/gindxbib              
        /usr/bin/glookbib             
        /usr/bin/gneqn              
        /usr/bin/gnroff            
        /usr/bin/gpic                                      
        /usr/bin/grap2graph                                 
        /usr/bin/grefer                                     
        /usr/bin/grodvi                                     
        /usr/bin/groff                                      
        /usr/bin/groffer                                    
        /usr/bin/grog                                       
        /usr/bin/grolbp                                     
        /usr/bin/grolj4                                     
        /usr/bin/grops                           
        /usr/bin/grotty                                     
        /usr/bin/gsoelim                                    
        /usr/bin/gxditview                                  
        /usr/bin/hpftodit                                   
        /usr/bin/lkbib                                      
        /usr/bin/mmroff                                     
        /usr/bin/pdfroff                                    
        /usr/bin/pfbtops                                    
        /usr/bin/pic2graph                                  
        /usr/bin/post-grohtml                               
        /usr/bin/pre-grohtml                                
        /usr/bin/tfmtodit                                   
        /usr/bin/xtotroff                                   

        /usr/gnu/bin/eqn         link to ../../bin/geqn
        /usr/gnu/bin/grn         link to ../../bin/ggrn
        /usr/gnu/bin/indxbib     link to ../../bin/gindxbib
        /usr/gnu/bin/lookbib     link to ../../bin/glookbib
        /usr/gnu/bin/neqn        link to ../../bin/gneqn
        /usr/gnu/bin/nroff       link to ../../bin/gnroff
        /usr/gnu/bin/pic         link to ../../bin/gpic
        /usr/gnu/bin/refer       link to ../../bin/grefer
        /usr/gnu/bin/soelim      link to ../../bin/gsoleim

        /usr/lib/groff/groffer/groffer2.sh  Private
        This is a script which should not be run independently and is
	run by the groffer program.

        /usr/lib/groff/site-tmac/*          Private       Macro packages
        These macro packages just redirect to macro packages in
        /usr/share/lib/tmac.

        /usr/share/doc/groff/1.19.2/*       Uncommitted   Documentation

        This seems to be random pieces of documentation:

        /usr/share/doc/groff/1.19.2/meintro.me
        /usr/share/doc/groff/1.19.2/meintro.ps
        /usr/share/doc/groff/1.19.2/meref.me
        /usr/share/doc/groff/1.19.2/meref.ps
        /usr/share/doc/groff/1.19.2/pic.ms
        /usr/share/doc/groff/1.19.2/pic.ps
        /usr/share/doc/groff/1.19.2/examples/grnexmpl.g
        /usr/share/doc/groff/1.19.2/examples/grnexmpl.me
        /usr/share/doc/groff/1.19.2/examples/grnexmpl.ps
        /usr/share/doc/groff/1.19.2/examples/groff.css
        /usr/share/doc/groff/1.19.2/examples/mom/README.txt
        /usr/share/doc/groff/1.19.2/examples/mom/elvis_syntax
        /usr/share/doc/groff/1.19.2/examples/mom/elvis_syntax.new
        /usr/share/doc/groff/1.19.2/examples/mom/letter.mom
        /usr/share/doc/groff/1.19.2/examples/mom/letter.ps
        /usr/share/doc/groff/1.19.2/examples/mom/penguin.ps
        /usr/share/doc/groff/1.19.2/examples/mom/sample_docs.mom
        /usr/share/doc/groff/1.19.2/examples/mom/sample_docs.ps
        /usr/share/doc/groff/1.19.2/examples/mom/typesetting.mom
        /usr/share/doc/groff/1.19.2/examples/mom/typesetting.ps
        /usr/share/doc/groff/1.19.2/examples/webpage.ms
        /usr/share/doc/groff/1.19.2/examples/webpage.ps
        /usr/share/doc/groff/1.19.2/html/mom/appendices.html
        /usr/share/doc/groff/1.19.2/html/mom/color.html
        /usr/share/doc/groff/1.19.2/html/mom/cover.html
        /usr/share/doc/groff/1.19.2/html/mom/definitions.html
        /usr/share/doc/groff/1.19.2/html/mom/docelement.html
        /usr/share/doc/groff/1.19.2/html/mom/docprocessing.html
        /usr/share/doc/groff/1.19.2/html/mom/goodies.html
        /usr/share/doc/groff/1.19.2/html/mom/headfootpage.html
        /usr/share/doc/groff/1.19.2/html/mom/inlines.html
        /usr/share/doc/groff/1.19.2/html/mom/intro.html
        /usr/share/doc/groff/1.19.2/html/mom/letters.html
        /usr/share/doc/groff/1.19.2/html/mom/macrolist.html
        /usr/share/doc/groff/1.19.2/html/mom/rectoverso.html
        /usr/share/doc/groff/1.19.2/html/mom/refer.html
        /usr/share/doc/groff/1.19.2/html/mom/reserved.html
        /usr/share/doc/groff/1.19.2/html/mom/toc.html
        /usr/share/doc/groff/1.19.2/html/mom/typemacdoc.html
        /usr/share/doc/groff/1.19.2/html/mom/typesetting.html
        /usr/share/doc/groff/1.19.2/html/mom/using.html
        /usr/share/doc/groff/1.19.2/pdf/pdfmark.pdf
        
        /usr/X11/lib/X11/app-defaults/GXditview
                                            Uncommitted
        Application default file for /usr/bin/gxditview.

	/usr/share/groff/1.19.2/tmac/*      Uncommitted   macro packages 
	/usr/share/info/groff*              Uncommitted   info documentation

	/usr/share/groff/1.19.2/font/*      Uncommitted   font files


    4.6. Doc Impact:

        Community provided man pages and help (info) documentation will be 
        installed. 

    4.7. Admin/Config Impact:

        None.

    4.8. HA Impact:

        None.

    4.9. I18N/L10N Impact:

        The JDS team and the G11N are working together to evaluate and
        provide I18N/L10N support.

    4.10. Packaging & Delivery:
    
        Adds new package, SUNWgroff, approximately 12 Mb.


    4.11. Security Impact:

        None.

    4.12. Dependencies:

        groff's HTML backend (grohtml) depends on the programs
        pnmcut, pnmcrop, pnmtopng, pnmtops which are part of netpbm.
        netbpm is not available on OpenSolaris.

5. Reference Documents:

        GNU Troff (Groff) - a GNU project
        - http://www.gnu.org/software/groff/

	Man pages:

        /usr/share/man/man1/addftinfo.1
        /usr/share/man/man1/afmtodit.1
        /usr/share/man/man1/eqn2graph.1
        /usr/share/man/man1/gdiffmk.1
        /usr/share/man/man1/geqn.1
        /usr/share/man/man1/ggrn.1
        /usr/share/man/man1/gindxbib.1
        /usr/share/man/man1/glookbib.1
        /usr/share/man/man1/gneqn.1
        /usr/share/man/man1/gnroff.1
        /usr/share/man/man1/gpic.1 
        /usr/share/man/man1/grap2graph.1
        /usr/share/man/man1/grefer.1   
        /usr/share/man/man1/grodvi.1  
        /usr/share/man/man1/groff.1  
        /usr/share/man/man1/groffer.1
        /usr/share/man/man1/grog.1 
        /usr/share/man/man1/grohtml.1 
        /usr/share/man/man1/grolbp.1 
        /usr/share/man/man1/grolj4.1
        /usr/share/man/man1/grops.1
        /usr/share/man/man1/grotty.1
        /usr/share/man/man1/gsoelim.1
        /usr/share/man/man1/gtroff.1
        /usr/share/man/man1/gxditview.1
        /usr/share/man/man1/hpftodit.1
        /usr/share/man/man1/lkbib.1  
        /usr/share/man/man1/mmroff.1
        /usr/share/man/man1/pdfroff.1
        /usr/share/man/man1/pfbtops.1
        /usr/share/man/man1/pic2graph.1
        /usr/share/man/man1/tfmtodit.1
        /usr/share/man/man1/xtoroff.1

        /usr/share/man/man4/groff_font.4
        /usr/share/man/man4/groff_out.4
        /usr/share/man/man4/groff_tmac.4
        /usr/share/man/man4/lj4_font.4 

        /usr/share/man/man5/ditroff.5 
        /usr/share/man/man5/groff.5  
        /usr/share/man/man5/groff_char.5
        /usr/share/man/man5/groff_diff.5
        /usr/share/man/man5/groff_man.5
        /usr/share/man/man5/groff_mdoc.5
        /usr/share/man/man5/groff_me.5
        /usr/share/man/man5/groff_mm.5 
        /usr/share/man/man5/groff_mmse.5
        /usr/share/man/man5/groff_mom.5
        /usr/share/man/man5/groff_ms.5
        /usr/share/man/man5/groff_trace.5
        /usr/share/man/man5/groff_www.5
        /usr/share/man/man5/roff.5    

6. Resources and Schedule
    6.4. Steering Committee requested information
   	6.4.1. Consolidation C-team Name:
		Desktop (JDS)
    6.5. ARC review type: FastTrack
    6.6. ARC Exposure: open


From sacadmin Mon Jul  7 18:53:53 2008
Received: from zruty.sfbay.sun.com (zruty.SFBay.Sun.COM [129.146.168.40])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m681rrFw008843
	for <LSARC@sac.sfbay.sun.com>; Mon, 7 Jul 2008 18:53:53 -0700 (PDT)
Received: from zruty.sfbay.sun.com (localhost [127.0.0.1])
	by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m681rrn5000112;
	Mon, 7 Jul 2008 18:53:53 -0700 (PDT)
Received: (from dduvall@localhost)
	by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2/Submit) id m681rrX7000111;
	Mon, 7 Jul 2008 18:53:53 -0700 (PDT)
Date: Mon, 7 Jul 2008 18:53:53 -0700
From: Danek Duvall <danek.duvall@Sun.COM>
To: Alan Coopersmith <Alan.Coopersmith@Sun.COM>
Cc: LSARC@sac.sfbay.sun.com, Padraig.Obriain@Sun.COM
Subject: Re: GNU Troff (groff) [LSARC/2008/425 FastTrack timeout 07/14/2008]
Message-ID: <20080708015353.GF4978@zruty.sfbay.sun.com>
References: <200807080041.m680fP8B022232@almas.sfbay.sun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200807080041.m680fP8B022232@almas.sfbay.sun.com>
User-Agent: Mutt/1.5.16 (2007-06-27)
Status: RO
Content-Length: 876

On Mon, Jul 07, 2008 at 05:41:25PM -0700, Alan Coopersmith wrote:

> 	/usr/share/groff/1.19.2/tmac/*      Uncommitted   macro packages 
> 	/usr/share/groff/1.19.2/font/*      Uncommitted   font files

What are the interfaces here -- the full paths, or just the names of the
macro packages and font files?  If the full paths are Uncommitted, then you
will have trouble upgrading groff in the future without forcing all these
guys into the (by then) outdated "1.19.2" directory.

But I assume that these are interfaces expected to be used by name, not
path, and that groff will map those names into paths internally; i.e., via
the -m command-line flag, or via the \f macro.  Correct?

The same would apply to the documentation in the versioned directory,
which, for some reason people keep including in their interface table.
But documentation isn't an interface, folks.

Danek

From sacadmin Tue Jul  8 00:54:45 2008
Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02.SFBay.Sun.COM [129.146.11.31])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m687sjQb016252
	for <LSARC@sac.sfbay.sun.com>; Tue, 8 Jul 2008 00:54:45 -0700 (PDT)
Received: from gmp-eb-inf-1.sun.com (gmp-eb-inf-1.EU.Sun.COM [192.18.6.21])
	by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m687siK4039723
	for <LSARC@sac.sfbay.sun.com>; Tue, 8 Jul 2008 00:54:45 -0700 (PDT)
Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe1.eu.sun.com [192.18.6.10])
	by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m687scNO012531
	for <LSARC@sac.sfbay.sun.com>; Tue, 8 Jul 2008 07:54:39 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 <0K3O00A01G1P8R00@fe-emea-10.sun.com>
 (original mail from Padraig.Obriain@Sun.COM) for LSARC@sac.sfbay.sun.com; Tue,
 08 Jul 2008 08:54:38 +0100 (BST)
Received: from [129.156.234.22] by fe-emea-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0K3O004N3GMZ9670@fe-emea-10.sun.com>; Tue,
 08 Jul 2008 08:54:36 +0100 (BST)
Date: Tue, 08 Jul 2008 08:41:04 +0100
From: "Padraig O'Briain" <Padraig.Obriain@Sun.COM>
Subject: Re: GNU Troff (groff) [LSARC/2008/425 FastTrack timeout 07/14/2008]
In-reply-to: <20080708015353.GF4978@zruty.sfbay.sun.com>
Sender: Padraig.Obriain@Sun.COM
To: Danek Duvall <Danek.Duvall@Sun.COM>
Cc: Alan Coopersmith <Alan.Coopersmith@Sun.COM>, LSARC@sac.sfbay.sun.com
Message-id: <48731A10.3080700@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_pbzEuohXqiWA4IFdr1GUSg)"
References: <200807080041.m680fP8B022232@almas.sfbay.sun.com>
 <20080708015353.GF4978@zruty.sfbay.sun.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080602)
Status: RO
Content-Length: 2789

This is a multi-part message in MIME format.

--Boundary_(ID_pbzEuohXqiWA4IFdr1GUSg)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT



Danek Duvall wrote:
> On Mon, Jul 07, 2008 at 05:41:25PM -0700, Alan Coopersmith wrote:
>
>   
>> 	/usr/share/groff/1.19.2/tmac/*      Uncommitted   macro packages 
>> 	/usr/share/groff/1.19.2/font/*      Uncommitted   font files
>>     
>
> What are the interfaces here -- the full paths, or just the names of the
> macro packages and font files?  If the full paths are Uncommitted, then you
> will have trouble upgrading groff in the future without forcing all these
> guys into the (by then) outdated "1.19.2" directory.
>
> But I assume that these are interfaces expected to be used by name, not
> path, and that groff will map those names into paths internally; i.e., via
> the -m command-line flag, or via the \f macro.  Correct?
>   

Yes, I believe so.
> The same would apply to the documentation in the versioned directory,
> which, for some reason people keep including in their interface table.
> But documentation isn't an interface, folks.
>
> Danek
>   

--Boundary_(ID_pbzEuohXqiWA4IFdr1GUSg)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Danek Duvall wrote:
<blockquote cite="mid:20080708015353.GF4978@zruty.sfbay.sun.com"
 type="cite">
  <pre wrap="">On Mon, Jul 07, 2008 at 05:41:25PM -0700, Alan Coopersmith wrote:

  </pre>
  <blockquote type="cite">
    <pre wrap="">	/usr/share/groff/1.19.2/tmac/*      Uncommitted   macro packages 
	/usr/share/groff/1.19.2/font/*      Uncommitted   font files
    </pre>
  </blockquote>
  <pre wrap=""><!---->
What are the interfaces here -- the full paths, or just the names of the
macro packages and font files?  If the full paths are Uncommitted, then you
will have trouble upgrading groff in the future without forcing all these
guys into the (by then) outdated "1.19.2" directory.

But I assume that these are interfaces expected to be used by name, not
path, and that groff will map those names into paths internally; i.e., via
the -m command-line flag, or via the \f macro.  Correct?
  </pre>
</blockquote>
<br>
Yes, I believe so.<br>
<blockquote cite="mid:20080708015353.GF4978@zruty.sfbay.sun.com"
 type="cite">
  <pre wrap="">
The same would apply to the documentation in the versioned directory,
which, for some reason people keep including in their interface table.
But documentation isn't an interface, folks.

Danek
  </pre>
</blockquote>
</body>
</html>

--Boundary_(ID_pbzEuohXqiWA4IFdr1GUSg)--

From sacadmin Tue Jul  8 03:32:35 2008
Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02.SFBay.Sun.COM [129.146.11.31])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m68AWZl7020578
	for <LSARC@sac.sfbay.sun.com>; Tue, 8 Jul 2008 03:32:35 -0700 (PDT)
Received: from gmp-eb-inf-1.sun.com (gmp-eb-inf-1.EU.Sun.COM [192.18.6.21])
	by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m68AWYda043718
	for <LSARC@sac.sfbay.sun.com>; Tue, 8 Jul 2008 03:32:34 -0700 (PDT)
Received: from fe-emea-09.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 m68AWTCQ007101
	for <LSARC@sac.sfbay.sun.com>; Tue, 8 Jul 2008 10:32:29 GMT
Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0K3O00801KDMXK00@fe-emea-09.sun.com>
 (original mail from Darren.Moffat@Sun.COM) for LSARC@sac.sfbay.sun.com; Tue,
 08 Jul 2008 11:32:29 +0100 (BST)
Received: from [129.156.173.21] by fe-emea-09.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0K3O00C11NXSY720@fe-emea-09.sun.com> for
 LSARC@sac.sfbay.sun.com; Tue, 08 Jul 2008 11:32:17 +0100 (BST)
Date: Tue, 08 Jul 2008 11:32:16 +0100
From: Darren J Moffat <Darren.Moffat@Sun.COM>
Subject: Re: GNU Troff (groff) [LSARC/2008/425 FastTrack timeout 07/14/2008]
In-reply-to: <200807080041.m680fP8B022232@almas.sfbay.sun.com>
Sender: Darren.Moffat@Sun.COM
To: Alan Coopersmith <Alan.Coopersmith@Sun.COM>
Cc: LSARC@sac.sfbay.sun.com, Padraig.Obriain@Sun.COM
Message-id: <48734230.3010309@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <200807080041.m680fP8B022232@almas.sfbay.sun.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080602)
Status: RO
Content-Length: 274

Is GNU Troff a true and fully compatible superset of the existing 
troff/nroff family we already have ?  In otherwords can GNU Troff 
replace what we have rather than being in addition to it.

I don't know of there are any standards issues in this area.

--
Darren J Moffat

From sacadmin Tue Jul  8 05:35:31 2008
Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02.SFBay.Sun.COM [129.146.11.31])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m68CZVXL023142
	for <LSARC@sac.sfbay.sun.com>; Tue, 8 Jul 2008 05:35:31 -0700 (PDT)
Received: from gmp-eb-inf-1.sun.com (gmp-eb-inf-1.EU.Sun.COM [192.18.6.21])
	by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m68CZUPn028990
	for <LSARC@sac.sfbay.sun.com>; Tue, 8 Jul 2008 05:35:31 -0700 (PDT)
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 m68CZPex023698
	for <LSARC@sac.sfbay.sun.com>; Tue, 8 Jul 2008 12:35:25 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 <0K3O00J01RLK3X00@fe-emea-10.sun.com>
 (original mail from Padraig.Obriain@Sun.COM) for LSARC@sac.sfbay.sun.com; Tue,
 08 Jul 2008 13:35:25 +0100 (BST)
Received: from [129.156.234.22] by fe-emea-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0K3O001E6TMQME70@fe-emea-10.sun.com> for
 LSARC@sac.sfbay.sun.com; Tue, 08 Jul 2008 13:35:15 +0100 (BST)
Date: Tue, 08 Jul 2008 13:21:41 +0100
From: "Padraig O'Briain" <Padraig.Obriain@Sun.COM>
Subject: Re: GNU Troff (groff) [LSARC/2008/425 FastTrack timeout 07/14/2008]
In-reply-to: <48734230.3010309@Sun.COM>
Sender: Padraig.Obriain@Sun.COM
To: Darren J Moffat <Darren.Moffat@Sun.COM>
Cc: Alan Coopersmith <Alan.Coopersmith@Sun.COM>, LSARC@sac.sfbay.sun.com
Message-id: <48735BD5.8030104@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <200807080041.m680fP8B022232@almas.sfbay.sun.com>
 <48734230.3010309@Sun.COM>
User-Agent: Thunderbird 2.0.0.14 (X11/20080602)
Status: RO
Content-Length: 436

It is hard to tell. I have not found this claim in the groff 
documentation but one would probably not expect it.

Padraig

Darren J Moffat wrote:
> Is GNU Troff a true and fully compatible superset of the existing 
> troff/nroff family we already have ?  In otherwords can GNU Troff 
> replace what we have rather than being in addition to it.
>
> I don't know of there are any standards issues in this area.
>
> -- 
> Darren J Moffat

From sacadmin Tue Jul  8 06:26:16 2008
Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01.SFBay.Sun.COM [129.145.155.118])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m68DQG8o025530
	for <LSARC@sac.sfbay.sun.com>; Tue, 8 Jul 2008 06:26:16 -0700 (PDT)
Received: from gmp-eb-inf-2.sun.com (gmp-eb-inf-2.EU.Sun.COM [192.18.6.24])
	by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m68DQF4U013697
	for <LSARC@sac.sfbay.sun.com>; Tue, 8 Jul 2008 06:26:16 -0700 (PDT)
Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12])
	by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m68DQAGC013924
	for <LSARC@sac.sfbay.sun.com>; Tue, 8 Jul 2008 13:26:10 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 <0K3O00B01VBX7V00@fe-emea-10.sun.com>
 (original mail from Darren.Moffat@Sun.COM) for LSARC@sac.sfbay.sun.com; Tue,
 08 Jul 2008 14:26: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 <0K3O0015YVZ7MEA0@fe-emea-10.sun.com> for
 LSARC@sac.sfbay.sun.com; Tue, 08 Jul 2008 14:25:56 +0100 (BST)
Date: Tue, 08 Jul 2008 14:25:55 +0100
From: Darren J Moffat <Darren.Moffat@Sun.COM>
Subject: Re: GNU Troff (groff) [LSARC/2008/425 FastTrack timeout 07/14/2008]
In-reply-to: <48735BD5.8030104@sun.com>
Sender: Darren.Moffat@Sun.COM
To: "Padraig O'Briain" <Padraig.Obriain@Sun.COM>
Cc: Alan Coopersmith <Alan.Coopersmith@Sun.COM>, LSARC@sac.sfbay.sun.com
Message-id: <48736AE3.3010509@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <200807080041.m680fP8B022232@almas.sfbay.sun.com>
 <48734230.3010309@Sun.COM> <48735BD5.8030104@sun.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080602)
Status: RO
Content-Length: 505

Padraig O'Briain wrote:
> It is hard to tell. I have not found this claim in the groff 
> documentation but one would probably not expect it.

Okay then I guess they co-exist.

> Padraig
> 
> Darren J Moffat wrote:
>> Is GNU Troff a true and fully compatible superset of the existing 
>> troff/nroff family we already have ?  In otherwords can GNU Troff 
>> replace what we have rather than being in addition to it.
>>
>> I don't know of there are any standards issues in this area.


-- 
Darren J Moffat

From sacadmin Tue Jul  8 09:20:42 2008
Received: from zruty.sfbay.sun.com (zruty.SFBay.Sun.COM [129.146.168.40])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m68GKg5n000232
	for <LSARC@sac.sfbay.sun.com>; Tue, 8 Jul 2008 09:20:42 -0700 (PDT)
Received: from zruty.sfbay.sun.com (localhost [127.0.0.1])
	by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2) with ESMTP id m68GKgo8004435;
	Tue, 8 Jul 2008 09:20:42 -0700 (PDT)
Received: (from dduvall@localhost)
	by zruty.sfbay.sun.com (8.14.2+Sun/8.14.2/Submit) id m68GKgQt004434;
	Tue, 8 Jul 2008 09:20:42 -0700 (PDT)
Date: Tue, 8 Jul 2008 09:20:42 -0700
From: Danek Duvall <danek.duvall@sun.com>
To: Darren J Moffat <Darren.Moffat@sun.com>
Cc: "Padraig O'Briain" <Padraig.Obriain@sun.com>,
        Alan Coopersmith <Alan.Coopersmith@sun.com>, LSARC@sac.sfbay.sun.com
Subject: Re: GNU Troff (groff) [LSARC/2008/425 FastTrack timeout 07/14/2008]
Message-ID: <20080708162042.GA1920@zruty.sfbay.sun.com>
References: <200807080041.m680fP8B022232@almas.sfbay.sun.com> <48734230.3010309@Sun.COM> <48735BD5.8030104@sun.com> <48736AE3.3010509@Sun.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <48736AE3.3010509@Sun.COM>
User-Agent: Mutt/1.5.16 (2007-06-27)
Status: RO
Content-Length: 530

On Tue, Jul 08, 2008 at 02:25:55PM +0100, Darren J Moffat wrote:

> Padraig O'Briain wrote:
>> It is hard to tell. I have not found this claim in the groff documentation 
>> but one would probably not expect it.
>
> Okay then I guess they co-exist.

Still, it would be worth looking into.  If it can replace the existing
*roff commands, or can do so with a little work, it might be worth running
a project to do so at some point in the future.

I suppose we could make the switch in Indiana and see if anyone hollers.  ;-)

Danek

From sacadmin Tue Jul 15 09:57:46 2008
Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01.SFBay.Sun.COM [129.145.155.118])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m6FGvkeP017283
	for <LSARC@sac.sfbay.sun.com>; Tue, 15 Jul 2008 09:57:46 -0700 (PDT)
Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133])
	by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m6FGvk4P044793
	for <LSARC@sac.sfbay.sun.com>; Tue, 15 Jul 2008 09:57:46 -0700 (PDT)
Received: from fe-sfbay-10.sun.com ([192.18.43.129])
	by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m6FGvfJN002435
	for <LSARC@sac.sfbay.sun.com>; Tue, 15 Jul 2008 09:57:41 -0700 (PDT)
Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0K42009013UZUO00@fe-sfbay-10.sun.com>
 (original mail from Alan.Coopersmith@Sun.COM) for LSARC@sac.sfbay.sun.com;
 Tue, 15 Jul 2008 09:57:41 -0700 (PDT)
Received: from almas.sfbay.sun.com ([129.146.106.93])
 by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb
 28 2007)) with ESMTPSA id <0K42003TE4FB4ME0@fe-sfbay-10.sun.com> for
 LSARC@sac.sfbay.sun.com; Tue, 15 Jul 2008 09:57:11 -0700 (PDT)
Date: Tue, 15 Jul 2008 09:57:11 -0700
From: Alan Coopersmith <Alan.Coopersmith@Sun.COM>
Subject: Re: GNU Troff (groff) [LSARC/2008/425 FastTrack timeout 07/14/2008]
In-reply-to: <200807080041.m680fP8B022232@almas.sfbay.sun.com>
Sender: Alan.Coopersmith@Sun.COM
To: LSARC@sac.sfbay.sun.com
Cc: Padraig.Obriain@Sun.COM
Message-id: <487CD6E7.7090308@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Enigmail-Version: 0.95.1
References: <200807080041.m680fP8B022232@almas.sfbay.sun.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20071203)
Status: RO
Content-Length: 712

Alan Coopersmith wrote:
> I am sponsoring this fasttrack for Padraig O'Briain of the Desktop team.
> The timeout is set for one week from today, Monday July 14, and the case
> requests a patch release binding as it only introduces new commands.

With no remaining open questions, this case is timed out, and closed approved.

The project team is given the informal advice (i.e. I'm not writing an opinion
just to say this) to work with the ON utilities team that owns nroff/troff &
possibly the Indiana team, to evaluate if any of these tools can replace the
old *roff tools in a future project.

-- 
	-Alan Coopersmith-           alan.coopersmith@sun.com
	 Sun Microsystems, Inc. - X Window System Engineering


From sacadmin Tue Jul 15 10:16:54 2008
Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02.SFBay.Sun.COM [129.146.11.31])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m6FHGsaw018695
	for <LSARC@sac.sfbay.sun.com>; Tue, 15 Jul 2008 10:16:54 -0700 (PDT)
Received: from sca-es-mail-1.sun.com (sca-es-mail-1.Sun.COM [192.18.43.132])
	by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m6FHGs2s010837
	for <LSARC@sac.sfbay.sun.com>; Tue, 15 Jul 2008 10:16:54 -0700 (PDT)
Received: from fe-sfbay-09.sun.com ([192.18.43.129])
	by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m6FHGn5H028645
	for <LSARC@sac.sfbay.sun.com>; Tue, 15 Jul 2008 10:16:49 -0700 (PDT)
Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0K4200J01513OC00@fe-sfbay-09.sun.com>
 (original mail from tom.childers@sun.com) for LSARC@sac.sfbay.sun.com; Tue,
 15 Jul 2008 10:16:49 -0700 (PDT)
Received: from [10.0.1.5] ([75.101.10.39])
 by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb
 28 2007)) with ESMTPSA id <0K4200HUK5BUBA30@fe-sfbay-09.sun.com> for
 LSARC@sac.sfbay.sun.com; Tue, 15 Jul 2008 10:16:42 -0700 (PDT)
Date: Tue, 15 Jul 2008 10:15:23 -0700
From: Tom Childers <tom.childers@sun.com>
Subject: Re: GNU Troff (groff) [LSARC/2008/425 FastTrack timeout 07/14/2008]
In-reply-to: <487CD6E7.7090308@sun.com>
Sender: Thomas.Childers@sun.com
To: Alan Coopersmith <Alan.Coopersmith@sun.com>
Cc: LSARC@sac.sfbay.sun.com, Padraig.Obriain@sun.com
Message-id: <0B3D0110-7E99-4831-8EF4-5C9657041912@sun.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.928.1)
Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII
Content-transfer-encoding: 7BIT
References: <200807080041.m680fP8B022232@almas.sfbay.sun.com>
 <487CD6E7.7090308@sun.com>
Status: RO
Content-Length: 1164

Alan,

I'm still wondering if the groff tool is backward compatible with any  
other *roff tools. I would like a statement, and preferably man page  
documentation to that effect. Otherwise, why are we promoting a new  
*roff tool?

Please keep the case open until this issue is resolved. I imagine it's  
available from the groff authors.
-tdc

On Jul 15, 2008, at 9:57 AM, Alan Coopersmith wrote:

> Alan Coopersmith wrote:
>> I am sponsoring this fasttrack for Padraig O'Briain of the Desktop  
>> team.
>> The timeout is set for one week from today, Monday July 14, and the  
>> case
>> requests a patch release binding as it only introduces new commands.
>
> With no remaining open questions, this case is timed out, and closed  
> approved.
>
> The project team is given the informal advice (i.e. I'm not writing  
> an opinion
> just to say this) to work with the ON utilities team that owns nroff/ 
> troff &
> possibly the Indiana team, to evaluate if any of these tools can  
> replace the
> old *roff tools in a future project.
>
> -- 
> 	-Alan Coopersmith-           alan.coopersmith@sun.com
> 	 Sun Microsystems, Inc. - X Window System Engineering
>


From Alan.Coopersmith@Sun.COM Tue Jul 15 10:36:12 2008
Received: from dm-sfbay-02.sfbay.sun.com (dm-sfbay-02.SFBay.Sun.COM [129.146.11.31])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m6FHaCdB020257
	for <LSARC-ext@sac.sfbay.sun.com>; Tue, 15 Jul 2008 10:36:12 -0700 (PDT)
Received: from sca-es-mail-2.sun.com (sca-es-mail-2.Sun.COM [192.18.43.133])
	by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m6FHaBU4024015
	for <LSARC-ext@sac.sfbay.sun.com>; Tue, 15 Jul 2008 10:36:11 -0700 (PDT)
Received: from fe-sfbay-09.sun.com ([192.18.43.129])
	by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m6FHa6W5007454
	for <LSARC-ext@sac.sfbay.sun.com>; Tue, 15 Jul 2008 10:36:06 -0700 (PDT)
Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0K4200F015LNSN00@fe-sfbay-09.sun.com>
 (original mail from Alan.Coopersmith@Sun.COM) for LSARC-ext@sac.sfbay.sun.com;
 Tue, 15 Jul 2008 10:36:06 -0700 (PDT)
Received: from almas.sfbay.sun.com ([129.146.106.93])
 by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb
 28 2007)) with ESMTPSA id <0K4200HIR67XBAC0@fe-sfbay-09.sun.com> for
 LSARC-ext@sac.sfbay.sun.com; Tue, 15 Jul 2008 10:35:58 -0700 (PDT)
Date: Tue, 15 Jul 2008 10:35:57 -0700
From: Alan Coopersmith <Alan.Coopersmith@Sun.COM>
Subject: Re: GNU Troff (groff) [LSARC/2008/425 FastTrack timeout 07/14/2008]
In-reply-to: <0B3D0110-7E99-4831-8EF4-5C9657041912@sun.com>
Sender: Alan.Coopersmith@Sun.COM
To: Tom Childers <tom.childers@Sun.COM>
Cc: LSARC-ext@sac.sfbay.sun.com, Padraig.Obriain@Sun.COM
Message-id: <487CDFFD.2010507@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Enigmail-Version: 0.95.1
References: <200807080041.m680fP8B022232@almas.sfbay.sun.com>
 <487CD6E7.7090308@sun.com> <0B3D0110-7E99-4831-8EF4-5C9657041912@sun.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20071203)
Status: RO
Content-Length: 2140

I'll re-open the case for now, but at least part of the answers are clear:

1) We're shipping groff because it works with documents we get from developers
   who work on other distros that our nroff/troff don't work with.  (Examples
   include CR's 6720105, 6675433, 6510256 and probably a bunch more.)

2) We're shipping groff because it includes long-standing pieces of the *roff
   toolchain that are missing from Solaris, such as pic & grap.  (CR 4470869)

3) We're shipping groff because it's a tool that's familiar to Linux & BSD
   developers that Solaris doesn't have, and that alone has been declared to
   be reason enough.

I'll let the project team research the compatibility issue, though I wonder
if it's really an issue for this case or the advised future project to replace
Solaris *roff with groff.

	-Alan Coopersmith-           alan.coopersmith@sun.com
	 Sun Microsystems, Inc. - X Window System Engineering

Tom Childers wrote:
> Alan,
> 
> I'm still wondering if the groff tool is backward compatible with any
> other *roff tools. I would like a statement, and preferably man page
> documentation to that effect. Otherwise, why are we promoting a new
> *roff tool?
> 
> Please keep the case open until this issue is resolved. I imagine it's
> available from the groff authors.
> -tdc
> 
> On Jul 15, 2008, at 9:57 AM, Alan Coopersmith wrote:
> 
>> Alan Coopersmith wrote:
>>> I am sponsoring this fasttrack for Padraig O'Briain of the Desktop team.
>>> The timeout is set for one week from today, Monday July 14, and the case
>>> requests a patch release binding as it only introduces new commands.
>>
>> With no remaining open questions, this case is timed out, and closed
>> approved.
>>
>> The project team is given the informal advice (i.e. I'm not writing an
>> opinion
>> just to say this) to work with the ON utilities team that owns
>> nroff/troff &
>> possibly the Indiana team, to evaluate if any of these tools can
>> replace the
>> old *roff tools in a future project.
>>
>> -- 
>>     -Alan Coopersmith-           alan.coopersmith@sun.com
>>      Sun Microsystems, Inc. - X Window System Engineering
>>
> 

From tom.childers@sun.com Tue Jul 15 17:46:52 2008
Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01.SFBay.Sun.COM [129.145.155.118])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m6G0kqBo003223
	for <LSARC-ext@sac.sfbay.sun.com>; Tue, 15 Jul 2008 17:46:52 -0700 (PDT)
Received: from sca-es-mail-1.sun.com (sca-es-mail-1.Sun.COM [192.18.43.132])
	by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m6G0kqaH010358
	for <LSARC-ext@sac.sfbay.sun.com>; Tue, 15 Jul 2008 17:46:52 -0700 (PDT)
Received: from fe-sfbay-10.sun.com ([192.18.43.129])
	by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m6G0klwE019785
	for <LSARC-ext@sac.sfbay.sun.com>; Tue, 15 Jul 2008 17:46:47 -0700 (PDT)
Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0K4200901Q1HDO00@fe-sfbay-10.sun.com>
 (original mail from tom.childers@sun.com) for LSARC-ext@sac.sfbay.sun.com;
 Tue, 15 Jul 2008 17:46:47 -0700 (PDT)
Received: from [10.0.1.5] ([75.101.10.39])
 by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb
 28 2007)) with ESMTPSA id <0K4200A8CQ5YPQ00@fe-sfbay-10.sun.com> for
 LSARC-ext@sac.sfbay.sun.com; Tue, 15 Jul 2008 17:46:47 -0700 (PDT)
Date: Tue, 15 Jul 2008 17:45:27 -0700
From: Tom Childers <tom.childers@sun.com>
Subject: Re: GNU Troff (groff) [LSARC/2008/425 FastTrack timeout 07/14/2008]
In-reply-to: <487CDFFD.2010507@sun.com>
Sender: Thomas.Childers@sun.com
To: Alan Coopersmith <Alan.Coopersmith@sun.com>
Cc: LSARC-ext@sac.sfbay.sun.com, Padraig.Obriain@sun.com
Message-id: <57DB333B-B5DB-4F7F-8A29-E136206D4034@sun.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.928.1)
Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII
Content-transfer-encoding: 7BIT
References: <200807080041.m680fP8B022232@almas.sfbay.sun.com>
 <487CD6E7.7090308@sun.com> <0B3D0110-7E99-4831-8EF4-5C9657041912@sun.com>
 <487CDFFD.2010507@sun.com>
Status: RO
Content-Length: 2572

Thanks, Alan.  That's good enough for me. I also went through the info  
on the gnu website, and see that there are troff and nroff  
compatibility modes.

Now that this info is in the mail archive for the case, I'm happy to  
see it approved.
-tdc

On Jul 15, 2008, at 10:35 AM, Alan Coopersmith wrote:

> I'll re-open the case for now, but at least part of the answers are  
> clear:
>
> 1) We're shipping groff because it works with documents we get from  
> developers
>   who work on other distros that our nroff/troff don't work with.   
> (Examples
>   include CR's 6720105, 6675433, 6510256 and probably a bunch more.)
>
> 2) We're shipping groff because it includes long-standing pieces of  
> the *roff
>   toolchain that are missing from Solaris, such as pic & grap.  (CR  
> 4470869)
>
> 3) We're shipping groff because it's a tool that's familiar to Linux  
> & BSD
>   developers that Solaris doesn't have, and that alone has been  
> declared to
>   be reason enough.
>
> I'll let the project team research the compatibility issue, though I  
> wonder
> if it's really an issue for this case or the advised future project  
> to replace
> Solaris *roff with groff.
>
> 	-Alan Coopersmith-           alan.coopersmith@sun.com
> 	 Sun Microsystems, Inc. - X Window System Engineering
>
> Tom Childers wrote:
>> Alan,
>>
>> I'm still wondering if the groff tool is backward compatible with any
>> other *roff tools. I would like a statement, and preferably man page
>> documentation to that effect. Otherwise, why are we promoting a new
>> *roff tool?
>>
>> Please keep the case open until this issue is resolved. I imagine  
>> it's
>> available from the groff authors.
>> -tdc
>>
>> On Jul 15, 2008, at 9:57 AM, Alan Coopersmith wrote:
>>
>>> Alan Coopersmith wrote:
>>>> I am sponsoring this fasttrack for Padraig O'Briain of the  
>>>> Desktop team.
>>>> The timeout is set for one week from today, Monday July 14, and  
>>>> the case
>>>> requests a patch release binding as it only introduces new  
>>>> commands.
>>>
>>> With no remaining open questions, this case is timed out, and closed
>>> approved.
>>>
>>> The project team is given the informal advice (i.e. I'm not  
>>> writing an
>>> opinion
>>> just to say this) to work with the ON utilities team that owns
>>> nroff/troff &
>>> possibly the Indiana team, to evaluate if any of these tools can
>>> replace the
>>> old *roff tools in a future project.
>>>
>>> -- 
>>>    -Alan Coopersmith-           alan.coopersmith@sun.com
>>>     Sun Microsystems, Inc. - X Window System Engineering
>>>
>>


From Alan.Coopersmith@Sun.COM Thu Jul 17 18:02:45 2008
Received: from dm-sfbay-01.sfbay.sun.com (dm-sfbay-01.SFBay.Sun.COM [129.145.155.118])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m6I12jT0029577
	for <LSARC-ext@sac.sfbay.sun.com>; Thu, 17 Jul 2008 18:02:45 -0700 (PDT)
Received: from sca-es-mail-1.sun.com (sca-es-mail-1.Sun.COM [192.18.43.132])
	by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m6I12jT3035145
	for <LSARC-ext@sac.sfbay.sun.com>; Thu, 17 Jul 2008 18:02:45 -0700 (PDT)
Received: from fe-sfbay-10.sun.com ([192.18.43.129])
	by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m6I12eUX004448
	for <LSARC-ext@sac.sfbay.sun.com>; Thu, 17 Jul 2008 18:02:40 -0700 (PDT)
Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0K4600501G49MJ00@fe-sfbay-10.sun.com>
 (original mail from Alan.Coopersmith@Sun.COM) for LSARC-ext@sac.sfbay.sun.com;
 Thu, 17 Jul 2008 18:02:40 -0700 (PDT)
Received: from almas.sfbay.sun.com ([129.146.106.93])
 by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb
 28 2007)) with ESMTPSA id <0K4600HJ7G8FXY50@fe-sfbay-10.sun.com> for
 LSARC-ext@sac.sfbay.sun.com; Thu, 17 Jul 2008 18:02:40 -0700 (PDT)
Date: Thu, 17 Jul 2008 18:02:39 -0700
From: Alan Coopersmith <Alan.Coopersmith@Sun.COM>
Subject: Re: GNU Troff (groff) [LSARC/2008/425 FastTrack timeout 07/14/2008]
In-reply-to: <57DB333B-B5DB-4F7F-8A29-E136206D4034@sun.com>
Sender: Alan.Coopersmith@Sun.COM
To: Tom Childers <tom.childers@Sun.COM>
Cc: LSARC-ext@sac.sfbay.sun.com, Padraig.Obriain@Sun.COM
Message-id: <487FEBAF.7030202@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Enigmail-Version: 0.95.1
References: <200807080041.m680fP8B022232@almas.sfbay.sun.com>
 <487CD6E7.7090308@sun.com> <0B3D0110-7E99-4831-8EF4-5C9657041912@sun.com>
 <487CDFFD.2010507@sun.com> <57DB333B-B5DB-4F7F-8A29-E136206D4034@sun.com>
User-Agent: Thunderbird 2.0.0.6 (X11/20071203)
Status: RO
Content-Length: 2816

Thanks, I've now re-marked it as closed approved.

	-alan-

Tom Childers wrote:
> Thanks, Alan.  That's good enough for me. I also went through the info
> on the gnu website, and see that there are troff and nroff compatibility
> modes.
> 
> Now that this info is in the mail archive for the case, I'm happy to see
> it approved.
> -tdc
> 
> On Jul 15, 2008, at 10:35 AM, Alan Coopersmith wrote:
> 
>> I'll re-open the case for now, but at least part of the answers are
>> clear:
>>
>> 1) We're shipping groff because it works with documents we get from
>> developers
>>   who work on other distros that our nroff/troff don't work with. 
>> (Examples
>>   include CR's 6720105, 6675433, 6510256 and probably a bunch more.)
>>
>> 2) We're shipping groff because it includes long-standing pieces of
>> the *roff
>>   toolchain that are missing from Solaris, such as pic & grap.  (CR
>> 4470869)
>>
>> 3) We're shipping groff because it's a tool that's familiar to Linux &
>> BSD
>>   developers that Solaris doesn't have, and that alone has been
>> declared to
>>   be reason enough.
>>
>> I'll let the project team research the compatibility issue, though I
>> wonder
>> if it's really an issue for this case or the advised future project to
>> replace
>> Solaris *roff with groff.
>>
>>     -Alan Coopersmith-           alan.coopersmith@sun.com
>>      Sun Microsystems, Inc. - X Window System Engineering
>>
>> Tom Childers wrote:
>>> Alan,
>>>
>>> I'm still wondering if the groff tool is backward compatible with any
>>> other *roff tools. I would like a statement, and preferably man page
>>> documentation to that effect. Otherwise, why are we promoting a new
>>> *roff tool?
>>>
>>> Please keep the case open until this issue is resolved. I imagine it's
>>> available from the groff authors.
>>> -tdc
>>>
>>> On Jul 15, 2008, at 9:57 AM, Alan Coopersmith wrote:
>>>
>>>> Alan Coopersmith wrote:
>>>>> I am sponsoring this fasttrack for Padraig O'Briain of the Desktop
>>>>> team.
>>>>> The timeout is set for one week from today, Monday July 14, and the
>>>>> case
>>>>> requests a patch release binding as it only introduces new commands.
>>>>
>>>> With no remaining open questions, this case is timed out, and closed
>>>> approved.
>>>>
>>>> The project team is given the informal advice (i.e. I'm not writing an
>>>> opinion
>>>> just to say this) to work with the ON utilities team that owns
>>>> nroff/troff &
>>>> possibly the Indiana team, to evaluate if any of these tools can
>>>> replace the
>>>> old *roff tools in a future project.
>>>>
>>>> -- 
>>>>    -Alan Coopersmith-           alan.coopersmith@sun.com
>>>>     Sun Microsystems, Inc. - X Window System Engineering
>>>>
>>>
> 

-- 
	-Alan Coopersmith-           alan.coopersmith@sun.com
	 Sun Microsystems, Inc. - X Window System Engineering


