[tldistro] texlive2021 pretest images & rfp

[Karl Berry]

    as every year, I send the patches

It would be fine to send patches during the year too, i.e., when they
come in. (Here or tlbuild or tex-k, whatever.)

    Mostly man pages

It would be nice to send bugs for programs maintained somewhere else to
their maintainers. I try to keep the Build/source/*/README files in TL
up to date wrt upstream info. Anyway, I sent these on, after some
further changes/correction per below.

As for the code changes:

    fix for hurd and MAXPATHLEN[GTH], and silencing synctex which is a bit too
    noisy when no synctex file is available - a lib shouldn't ship out that.

Ok x 2.

    -.TH "axohelp" "1.1" "22 Jan 2018" ""
    +.TH "axohelp" "1" "22 Jan 2018" ""

The current version of axohelp is 1.3. I changed it to that.
Also updated the date.

    Index: texlive-bin/texk/detex/detex-src/detex.man
    -option tries to naively replace $..$, $$..$$, \(..\) and \[..\]
    +option tries to naively replace $..$, $$..$$, (..) and [..]

What's intended here is clearly \\(..\\) and \\[..\\], i.e., the LaTeX
math mode commands, so stripping the backslashes was wrong. I doubled
them instead.

    Index: texlive-bin/texk/dvi2tty/dvi2tty-src/dvi2tty.1
    ...
    -ordinary ascii terminal, such as the '+' and '-' symbol.
    +ordinary ascii terminal, such as the '+' and '\-' symbol.

I don't see the need to replace every - in every man page with \-.  A
regular hyphen seems like the correct thing to me to introduce options,
etc. And definitely a regular hyphen is what's on the keyboard. 

So I made it consistent in the other direction, and took out all the
backslashes. (Also, as long as we're puttering with trivialities, might
as well capitalize ASCII.)

    -devices (e.g. laser printers). To show that a broken line is really
    +devices (e.g., laser printers). To show that a broken line is really

A space following e.g. (or i.e.) is not incorrect. American usage is to
have a comma, British/other usage not. But since in this case there were
also instances of the definitely incorrect "e g", ok.


Thanks for all,
Karl