On Wed, Sep 07, 2005 at 04:18:42PM -0400, Timothy Miller wrote:
> On 9/7/05, Jack Carroll <[EMAIL PROTECTED]> wrote:
>
> > Would you like me to continue developing the number system?
>
> Please do, but I apologize in advance that I may have to have you
> repeat yourself when it comes time for me to have a more urgent need
> for this.
>
> One good place for you to put this is the wiki on duskglow
> (opengraphics.org). Start a section on part numbering and all that,
> list Traversal part numbers, etc. But published there, it would be a
> great resource for other organizations to model themselves after also.
>
> What do you think?
I can probably do something like that. I could possibly put
summaries and strategies into Wiki formatting; the coding looks easy to
learn. Depending how that goes, I might start the first root number logs in
Wiki form.
Actual engineering standards like the A-100A series will have to go
up as PDFs for now, and probably as editable OO.o documents once I get
enough of a handle on how to use it.
I'm thinking of splitting up the numbering system standard suite as
follows:
A-100A1 Main body, numbering system standard
A-100A2 Category list
A-100A3 Drawing class prefix list
We really need the layout power of a good desktop publishing package
to handle all the tables and page formats that occur in engineering text
documents. For the moment, that will have to be FrameMaker 3.1 because
that's what I'm proficient on, but it's not a good long-term solution for
others to maintain these documents. I don't think we need the
re-targetability of DocBook-XML for engineering drawings, because they're
never going to be re-laid-out on different paper sizes.
How would I send in files to the server, scp with write permission?
BTW, about the only major number that doesn't appear to be set so
far is the ASIC root number. TRV14? TRV10? Any decision?
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)
