Given that much of Pd development happens off of GitHub, I'd like to
draw some attention to a perhaps scandalous and contentious PR I've

This PR replaces the existing HTML manual with a single HTML file,
generated with [Pandoc]( from a new `` file
(which was generated from the existing HTML manual).

A render the HTML manual can be found here:

A PDF output is also linked.

The proposed future workflow for updating the HTML manual would
therefore be to make changes to `` and regenerated
with Pandoc.

The command to convert ` -> index.htm` is:

    $ pandoc -s -N -S --toc -c pdmanual.css -o index.htm

### Advantages

- a single file
- sections can be linked by name, e.g. `(see [Audio and MIDI])` links to
  3.1 Audio and MIDI
- sections are automatically numbered
- table of contents is automatically generated
- smart typography
- easier to keep up to date
- easier to convert to other formats
- can be rendered nicely on GitHub

### Changes

- a single file
- I fixed all sections headings to use title case
- given that sections can now be anchored by name and are automatically
  numbered, I replaced some links e.g. (see section 1.2) -> (see Other
  Resources); this has the advantage of never again needing to
  know/update the section number when updating the manual
- fixed a bunch of obvious errors/typos
- fixed Windows paths, which I'm pretty sure are `C:\Program Files` not
  `C:Program Files`


Pd-dev mailing list

Reply via email to