Hi Joe, All, See comments below.
On 01/23/2014 01:26 PM, Joe Taylor wrote: > Hi Greg (and all), > > Thanks for your continued work on the User's Guide. As it happens, I > did more-or-less the same thing, yesterday, splitting wsjtx-main.txt > into a number of smaller files. I then did some extensive editing on them. > > Today I merged my edits into (more or less) your file structure, and > committed everything to the SVN repository. As noted in the commit Log > message, Sections 6.2, 8, and beyond definitely need work. Other > polishing is also desirable, and no doubt there will be further > additions and/or changes. ** I pulled the latest svn this evening, looks pretty good. I'll wait until you've finished your edits before messing about any further. > [Note: It's possible that we've gone somewhat too far in splitting the > files into small pieces. Some of the new files are only a few hundred > characters long.] ** Yes, that is a potential problem using this method. Maybe a standard practice, at the Section level, leave the first paragraph in wsjtx-main.txt or something? > > By tomorrow I hope to finish what I know needs to be done to Section 6.2 > and from Section 8 to the end. Then I'll let it stand for a bit. > At that point, others can look it over and decide what they think still > needs work, what parts they'd like to work on, etc. ** Section 9: The JT9 Protocol, decoding discrete blocks - I found a few Asciidoc plug-in's that may be useful in building a diagram for this. It would require a couple small python modules, but they are in the repo's. The following links illustrate the possibilities: Main Plug-in Page: http://asciidoc.org/plugins.html Diag Specific Page: https://code.google.com/p/asciidoc-diag-filter/ - I can have a crack at this, but I'm not sure I fully understand all the elements in play, so it may need a bit of editing after. > If you want to see what it looks like now, do something like this: > > $ cd wsjtx > $ svn up > $ cd doc > $ build-dos-sh toc2 ** To Build: ./build-doc.sh toc2 - We can drop the .sh extension(s) if it is easier to use that way. General Comments: ** build-check.sh - I have the basic script finished. As it stands now it only pulls the "review" flag, as the files have not been updated yet. - If we want to utilize this capability, it may be worth writing up what which tags will be used initially, then I can add to the check capabilities for them. - The tag line can contain more that just status=review, etc etc. It could have release version info, editor, or whatever information is deemed appropriate. Then we simply parse the line for whatever is needed. ** Stylesheet, Config, and .js - It's too much for this post, but I'll send a separate e-mail on recommendations for setting up a standalone build system, which will allow customizing the stylesheet. > ... and then point your browser at the newly generated file > wsjtx-main-toc2.html > > -- Joe, K1JT 73's Greg [email protected] > _______________________________________________ > Wsjt-devel mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/wsjt-devel _______________________________________________ Wsjt-devel mailing list [email protected] https://lists.berlios.de/mailman/listinfo/wsjt-devel
