Create Local Manual

From Audacity Wiki
Revision as of 19:20, 24 June 2012 by MartynShaw (talk | contribs) (more consistent naming)
Jump to: navigation, search

This page describes how to prepare the local help for Audacity(R).
If the advice here is inaccurate or incomplete, please e-mail audacity-devel_AT_lists_DOT_sourceforge_DOT_net.
Related article(s):

Manual - Building

These instructions are for Windows, but the basics are the same for any platform. We use a script to pull the manual from the wiki and turn it into static html.

Remove the old manual and make sure you can rebuild a new one:

  1. Make sure you have Python installed and on your PATH. Use version 2.7.*, not 3.2.*.
  2. Delete audacity\help\manual if it exists.
  3. On VS, the manual can be built in audacity\help\manual by building the 'help' project.
  4. On Windows if you just want to get the manual, go to audacity\scripts\mw2html_audacity, run wiki2htm and wait for it to complete.
  5. There is also a, which may still work (untested here, feel free to update this comment)

Manual - Testing

Test the unzipped manual using or similar, and report errors/warnings as appropriate.

Manual - Zipping and Uploading

For a Release, somebody should follow these instructions just after the 'manual freeze' so that builders have the same manual for all OSs. That person will be agreed as part of the Release Process.

  1. Zip the result of the above as audacity-manual-<version.rcX>.zip (for example When unzipped, it should produce a "help" folder with the "manual" folder inside that.
  2. Upload the audacity-manual-<version.rcX>.zip onto Google code for use by the people making installers etc.
  3. Make sure that people are aware of the upload, and any new ones that are done, including
    1. RM
    2. People making installers etc.

When the release happens, rename audacity-manual-<version.rcX>.zip as the final version (for example

Unused/optional step

(The following step has not been used for recent Win builds, but has been left here for historical reasons.)

A currently optional step, at least for beta builds, is to reduce the size of the manual by reducing the size of the .png files. A way to do this on Windows with ImageMagick installed is shown as a batch script below, started from the image directory:

 FOR /R %%a IN (*.png) DO mogrify -posterize 64 %%a 
 FOR /R %%a IN (*.png) DO convert -quality 90 %%a %%a

This reduces the number of colors to 64 and then uses a hint to the .png compressor to be aggressive about compression. The %%a works on Win7. Martyn found that %a was needed instead on his platform (Win XP?). This reduces total images size from about 12Mb to about 5.2Mb. Some of the largest files are already being replaced on the wiki. If we do the whole wiki, then this step can be removed. If someone wants to post the equivalent script for Linux that would be appreciated.