(j3.2006) documents and votes (tempest in a teapot)
Bill Long
longb
Tue Feb 7 13:41:05 EST 2017
How about doing what we already do for PDF documents - have a .txt file with proper headers/date information that references the .docx file. We vote the .txt paper.
Cheers,
Bill
On Feb 7, 2017, at 12:26 PM, Dan Nagle <danlnagle at me.com> wrote:
> Hi,
>
> I have a ballot, in docx format, that ustag must vote at 212.
> Debbie has approved the wording and wants it to be
> a numbered meeting document.
>
> The document has so many "formatting features" that export to txt
> is pointless. I can likely make something readable, but it's
> a one-off copy-paste-intensive operation.
>
> Do we wish to forego our "txt only" rule for meeting documents?
> Only for INCITS documents? With some other criteria? (see 16-013)
>
> I don't see that we must decide this before 212, but I must return
> the document with votes per organization recorded and a paper number.
> So I must know the paper number when I return it, directly following
> the meeting.
>
> The committee's pleasure?
>
> --
>
> Cheers!
> Dan Nagle
>
>
>
>
> _______________________________________________
> J3 mailing list
> J3 at mailman.j3-fortran.org
> http://mailman.j3-fortran.org/mailman/listinfo/j3
Bill Long longb at cray.com
Fortran Technical Support & voice: 651-605-9024
Bioinformatics Software Development fax: 651-605-9142
Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101
More information about the J3
mailing list