Identify myself as the copyright holder. I've never executed copyright
assignment paperwork with the FSF, so my "legally significant"[1]
origination of this file in 2022 can't be under the FSF's copyright.
[1] "A change of just a few lines (less than 15 or so) is not legally
significant for copyright." Conversely, >= 15 lines would be.
https://www.gnu.org/prep/maintain/html_node/Legally-Significant.html
...and fix goof in test script.
* src/roff/nroff/nroff.sh: Replace proxy `unset`-based test with an
actual measurement of parameter expansion.
* src/roff/nroff/tests/verbose_option_works.sh: Fix spurious failure of
test for grep(1) supporting `-q` and `-x` options. Continues commit
e05cf6d3b3, 4 December.
Every time I have to deal with Solaris, it's like gazing into the Abyss.
A test failure of "src/roff/nroff/tests/verbose_option_works.sh" is
expected on Solaris 10, because 2 of the checks in that script verify
that option clustering works, and with Solaris 10 /bin/sh, it doesn't.
The test failure is therefore not spurious. One can edit the installed
nroff script in place to use "/usr/xpg4/bin" in its shebang line.
...lacking a shell or grep conforming to POSIX Issue 4 (1994).
* src/roff/groff/tests/msoquiet-request-works.sh:
* src/roff/groff/tests/soquiet-request-works.sh:
* tmac/tests/an_UR-works.sh: Do it.
* tmac/tests/an_UR-works.sh: Also cope with versions of pdftotext(1)
that transcribe "fi" as a ligature.
* HACKING:
* PROBLEMS: Update advice.
* contrib/hdtbl/examples/fonts_n.in:
* contrib/hdtbl/examples/fonts_x.in: Guard against substandard tr(1)
implementation on Solaris 10 by forcing locale to "C" when using a
POSIX regular expression character class.
* HACKING: Document this land mine.
* HACKING: Document another macOS od(1) irritation.
* src/roff/groff/tests/dvi-device-smoke-test.sh: Work around macOS
od(1)'s injection of extra spaces into its "-tx1" output.
Fixes <https://savannah.gnu.org/bugs/?66479>. Thanks to Sven Schober
for the report, analysis, and for proposing fixes.
Use the term "expression", which is of import in U.S. Code Title 17,
§501(a)-(b).
Also fix noun/verb agreement. (I have them separated by about 52 words.
Maybe I should recast...)
...to reflect substanial addition of material discussing...
...copyright, and when to bump the year in the copyright notice.
:-|
Continues commit 90b15242d0, 6 July.
Also fix wordo and tighten language.
* tmac/tests/an_TS-do-not-keep-tables-when-cR-set.sh: Improve
portability of script by using shell constructs instead of the
nonstandard GNU coreutils 'seq' utility. Resolves test failure on
Solaris 10.
* HACKING: Document this problem.
* tmac/tests/s_TC-works-with-percent-in-custom-titles.sh: Put newlines
after opening braces in sed scripts. macOS and GNU sed tolerate their
absence, but this sed does not.
* HACKING: Document this problem.
* tmac/tests/latin2_works.sh:
* tmac/tests/latin5_works.sh:
* tmac/tests/latin9_works.sh: Port to work around macOS's apparently
POSIX non-conforming 'od' command. Use single-byte octal output
format instead of "character", and update test expectations
accordingly. Apparently gratuitously, macOS also puts more spaces
after the octal address field when using this output format.
* HACKING: Document, and elaborate upon, this problem.
Also distinguish identical test failure diagnostics.
ANNOUNCE: Remove caveat about automated test failures on macOS.
* tmac/tests/doc_heading-font-remapping-works.sh: Put semicolons between
commands and closing braces in sed script. Put each of multiple
closing braces on a separate input line, because macOS doesn't accept
them otherwise. Resolves test failure observed on macOS.
* HACKING: Document the closing brace sequence problem.
* ANNOUNCE: Drop notice of failing test case, now resolved.
* tmac/tests/an_TS-adds-no-vertical-space.sh: Put semicolons between
commands and closing braces in sed script. Separate command stream
into multiple '-e' expressions, breaking them after branch and label
commands. Resolves test failure observed on macOS.
* HACKING: Document the above problems.
* ANNOUNCE: Drop notice of failing test case, now resolved.
* src/roff/groff/tests/some_escapes_accept_newline_delimiters.sh: Weaken
regexes in two test cases to accommodate excessive output from macOS's
'od' command. Resolves test failure seen on macOS.
* HACKING: Add section "Writing Tests" and document the above since this
is the second time I've cracked my shin on this.
* ANNOUNCE: Drop notice of failing test case, now resolved.
* FOR-RELEASE: Split-off ChangeLog files need to be added to the
distribution archive.
* HACKING: Clarify non-ChangeLoggable items. Generally, an item that
resolves a Savannah ticket should be ChangeLogged even if it would not
normally meet that threshold. Also clarify a point in an example; we
certainly expect table entries containing the word "FOOBAR" to show up
that way when formatted.
* INSTALL.REPO: Correct prose description of what to do with unpacked
"gnulib" snapshot.
* README: Clarify that the '.version' file is produced by the build
process. Clarify origins and provenance of various groff components.
Use a more appropriate URL for the Savannah issue tracker. Lightly
recast.
This scoops up the 'automake.mom' material just dropped from
'INSTALL.REPO', and summarizes a couple of discussions from the mailing
list over the past 2 years or so.
