Hello John, I didn't want to stir up a big business, and I am not going to write mails about some typing errors in the manuals. I just wanted to tell the editors, by which means I could have caught on faster or, the other way around, what would have helped me to understand EMC better in the beginning. By now, I have dug into it, and the feeling of insecurity is disappearing (not gone yet, though). It may add to this that I have to translate everything into German because I made the mistake to chose German as language in the beginning of installation (can I switch back?), and re-translate the screen into English to make it match with the manuals.
Being a physicist I am used to approach things from the bottom and therefore have difficulties to get in sideways. Only knowing the basics of systems helps me to build up my imagination and understand what I'm doing. But this is private little me, maybe others go at things differently. So, I have a dull feeling in my stomach calling an automatic installation routine. Of course, I know that a manual is outdated once it is printed, but I can't sit at the screen hours and hours - a piece of paper is my weather, I may be old-fashioned. <snip> If you spot something just send it to the list with the subject of "Documents" >or similar and we should catch it. Please use the manual name, chapter, >section >when pointing out anything. > - What I missed reading the manuals were >drawings. One picture says > > more > > than a thousand words. What I mean is e.g. a flow chart showing the order in which programs run and read .ini and other files. I wohld also point out what the contents and meanings of the various .* files is (I can't imagine what NML means, for instance). <snip> > > - If I had had an overwiew right from the beginning in which order > > all > > those .ini and .hal files are read by what program I could get a > > better > > feeling editing them (and faster!). > >In what section do you think this is needed? >Perhaps in the Configuration Chapter in the Config Files section >of the Integrators Manual? What I mean is something like fig.1.1. in the User's Manual, Chapter 1. Chapter 3 (on Axis), 3.3.2 is also great: all the buttons are pictured and explained (as is the whole Axis chapter). The Integrators Manual seems a little more abstract. Right, Ch.5 says "some of them (files) are read repeatedly while EMC is running" - hao about a program flow chart? Frankly, it's hard for me now to tell what exactly I missed when I was completely new to this business. >or in the Stepper Configurations/Modifying section >of the Getting Started Guide? Yes, in Ch.3.6 of Geting Started I had expected a little more descriptiveness of what is going to happen once I start the installation process and where the EMC components will be situated at. > > - A very humble suggestion: it should be possible to arrange the > > .pdf's > > pages so that when printing the manuals the odd page numbers are at > > right, > > the even ones at the left and the page numbers appear in the upper > > (or > > lower) outside corner like in ordinary book printing. > >It looks like the page numbering is some random mix... we use lyx to >create the docs as well >as some custom things to create the html's. I took a quick look and didn't >find a way to >specifiy where the page numbers should be... >I'll look into it a bit more to see what I can find. > >Part of the > > problem > > is that the contents pages at the front end are numbered by roman > > numerals > > which are not correctly recognized by the adobe printing tool (?) or > > my > > printer driver. > > > >As Alex noted the roman numbers are quite common and should print >correctly... Of course, they do, but page numbering suffers (also from the penguin on the very first page which seems to be no. 0). It's hard to keep printer pages and manual pages apart. O well, as I said, this doesn't matter at all, let's not discuss it further. >Have a nice cold one on me. Forgive me for not understanding what you mean. If it has to do with drinking, you be sure tonight. >John Peter Blodow ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
