DESIGNERCOUNCIL Archives

1996

DesignerCouncil@IPC.ORG

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Received:
by ipc.org (Smail3.1.28.1 #2) id m0uHB0N-0000EDC; Wed, 8 May 96 10:18 CDT
Encoding:
13 TEXT
Old-Return-Path:
Date:
Wed, 08 May 96 10:31:00 EDT
Precedence:
list
Resent-From:
Resent-Sender:
DesignerCouncil-request [log in to unmask]
X-Status:
Status:
O
X-Mailing-List:
<[log in to unmask]> archive/latest/1690
TO:
Designer Council <[log in to unmask]>
Return-Path:
<DesignerCouncil-request>
Resent-Message-ID:
<"uEMgB2.0.tO9.wiBan"@ipc>
Subject:
From:
Steve Willis <[log in to unmask]>
X-Loop:
Message-Id:
X-Mailer:
Microsoft Mail V3.0
From [log in to unmask] Wed May 15 18:
15:37 1996
Parts/Attachments:
text/plain (16 lines)

In working with several of our customers recently, we have been asked to 
generate documentation from our tools to help in their ECO process.  While 
the outputs have been very similar in format, they have been varied enough 
to require customization.

What I am looking for here is whether or not there is any industry standard 
format for this type of output.  Obviously I am looking for the least common 
denominator to limit the amount of work needed for each customer.  There may 
not be.

Steve Willis
[log in to unmask]



ATOM RSS1 RSS2