Submit patches for documentation

[Kevin Walzer]

What's the best way to submit patches for Python documentation at the
SourceForge patch tracker if you are not writing LaTeX? I would like to
submit some simple text updates. However, if I do this, I'm not clear
what files I should run a diff against.

Or is simply submitting the updates as a text file, with a note
indicating which documentation files they replace, sufficient?

 

[Steve Holden]

What's the best way to submit patches for Python documentation at the
SourceForge patch tracker if you are not writing LaTeX? I would like to
submit some simple text updates. However, if I do this, I'm not clear
what files I should run a diff against.

Or is simply submitting the updates as a text file, with a note
indicating which documentation files they replace, sufficient?

The doc authors would much rather have plain English text than nothing,
and are willing to do the markup themselves to incorporate wothwhile
changes.

regards
Steve

 

[Terry Reedy]

| What's the best way to submit patches for Python documentation at the
| SourceForge patch tracker if you are not writing LaTeX? I would like to
| submit some simple text updates. However, if I do this, I'm not clear
| what files I should run a diff against.
|
| Or is simply submitting the updates as a text file, with a note
| indicating which documentation files they replace, sufficient?

Identify the document, version (hopefully latest), and section.

I have submitted informal 'diffs' like

Typo: change psot to post

Paragraph 3 is unclear. Suggest replacement with
"qui ipsit locum....."

tjr