Re: [Emc-developers] Lack of attribution to NIST

2012-01-16 Thread John Thornton
Kent, Good idea on putting it in the catch-all section of the HTML. Can you think of a more general title for that section? Thanks John On 1/16/2012 7:48 AM, Kent A. Reed wrote: > On 1/16/2012 7:13 AM, John Thornton wrote: >> I put the file asciidoc-markup.txt in the /docs directory with all I

Re: [Emc-developers] Lack of attribution to NIST

2012-01-16 Thread Kent A. Reed
On 1/16/2012 7:13 AM, John Thornton wrote: > I put the file asciidoc-markup.txt in the /docs directory with all I > know about asciidoc. I use gedit with the Draw Spaces plugin that way I > can see the difference between tab and space and also see trailing spaces. > > I think a separate history.txt

Re: [Emc-developers] Lack of attribution to NIST

2012-01-16 Thread John Thornton
I put the file asciidoc-markup.txt in the /docs directory with all I know about asciidoc. I use gedit with the Draw Spaces plugin that way I can see the difference between tab and space and also see trailing spaces. I think a separate history.txt file is appropriate. I don't see where it would

Re: [Emc-developers] Lack of attribution to NIST

2012-01-16 Thread Anders Wallin
+1 on this. When the wikipedia-police wanted to take down the emc2 wikipedia entry I spent an afternoon digging up as many emc2-references as I could find. They are listed here: http://en.wikipedia.org/wiki/Enhanced_Machine_Controller In addition to historical references I would think there is ro

[Emc-developers] Lack of attribution to NIST

2012-01-15 Thread Kent A. Reed
Gentle persons: In reviewing the 2.5 documentation I came to realize that neither the docs nor the web/wiki site gives proper attribution to foundational documents from NIST, although there are tips of the hat to NIST as the originator of the EMC project and there are brief mentions of "the NI