-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello All,

As of r3662, the doc changes listed below are now in branch/wsjtx/doc/

I've removed the .tar.gz package and link

The build process an options remain the same:
- - cd doc/ && ./build-doc.sh toc2
- - Open wsjtx-main-toc2.html with your browser, for example:
  term-prompt$: chromium-browser ./wsjtx-main-toc2.html

73's
Greg, KI7MT
[email protected]


On 01/24/2014 11:09 PM, Greg Beam wrote:
> Hello All,
> 
> Based on Joe's latest commit, SVN r3659, I've made the following 
> changes, outside the source tree. The changes have "not" been 
> committed to svn yet.
> 
> ** build-doc.sh - Updated for rig-config* file changes - Updated
> wsjtx-main include::<file-name>.adoc[] links.
> 
> ** <file-name>.adoc update - Changed .txt file extension to .adoc
> 
> ** Appendix B - Rig Configuration - Reworked / renamed all pages -
> Updated wsjtx-main to reflect name changes - Added the following
> pages: 
> rig-config-{adat,alinco,aor,drake,electro,flexrad,kenwood,icom,softrock,tentec}.adoc
>
> 
- - Updated all pages / templates + rig-config-main.adoc
> 
> ** Quick Reference Guide - Started working on a toc2 style quick
> reference guide, focused on <blocks>, <lists>, <notes>, <texts> and
> <tables> currently being used in the User Guide.
> 
> The old file / link for docs.tar.gz has been removed.
> 
> New Download Link: http://ubuntuone.com/0YzW1iuM5FbE1qMBzmpy2S 
> md5sum: 53fae0978f769ad568304013eca39000 shasum:
> e9a8e5746684718ca98b74a0204da1b3f9f1974c
> 
> To Build: cd to download dir && tar -xzvf doc-2014-01-24.tar.gz cd
> doc-2014-01-24 ./build-doc.sh all
> 
> Then, open wsjtx-main-toc2.html in your browser.
> 
> 73's Greg, KI7MT [email protected]
> 
> 
> On 01/24/2014 01:32 PM, Joe Taylor wrote:
>> Here's a brief update on the WSJT-X User's Guide.
> 
>> The SVN repository presently has the sources for a version that, 
>> when processed by asciidoc, yield an html file that in most 
>> respects is accurate, looks good, and reads well.
> 
>> Here's a list (not necessarily complete) of things that I know 
>> still need to be done:
> 
>> 1. Section 6.2 (on the use of Compound Callsigns) is incomplete
>> and in some respects inaccurate.  I will rework it.
> 
>> 2. The lists of installed and runtime files, sections 10.1 and 
>> 10.2, need updating.
> 
>> 3. All links need to be tested.
> 
>> 4. All steps in the Tutorial need testing (preferable by someone 
>> other than me).
> 
>> 5. Text written by Murray on "DXCC and Worked B4" needs to be 
>> integrated somewhere.
> 
>> And finally, several new sections should probably be written:
> 
>> 1. Cooperative Programs: basic description of the way WSJT-X
>> works together with JT-Alertm, Commander, and HRD.
> 
>> 2. Frequenctly Asked Questions
> 
>> 3. Troubleshooting
> 
>> I'm very open to critiques of the User's Guide as it now stands, 
>> and to all suggestions on things that would improve it.
> 
>> My next efforts will be on sections 6.2 (Compound Callsigns) and 
>> 10 (Appendix A).  If you would like to work on another one of
>> the above items, or something else that you think desirable,
>> please make your intentions known!
> 
>> -- 73, Joe, K1JT _______________________________________________
>>  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
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS5FdsAAoJEAmfcyeKlj0xD1oIAIURJtewNo4k1SooP8e1XQoT
9mvq70+nfCnLWNxUfW63ExGw3FhOtOITIuaYhaA8f49/ptprNFeE8auMF9MVMQi3
nl6Kv3ZNwkLEEsA/yg7RiknTBtZcoijSwLJ4sM5HRwVtE10sY+CfvjZNdgO7uZUm
4AONyaItJsj38NYWS78sMzxKzVwKGxWAK6fUKDyTj/TWVFQ0l7U4m2Bv7cQTPAAS
wpn1Km/mdbCGbcKU6uz2FVi35BCLmnspWaHmNC4QONu2FFWZDs3KAN63bOGhNuUZ
ziZvWwkncRfyrux1lwnYPMEfUW5u8Dgb15n825Ga0XTLnDMJmRXCF9cba1DrNyY=
=iRsF
-----END PGP SIGNATURE-----
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel

Reply via email to