| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Doug McIlroy noted this vague term, which groff employs for multiple
purposes. Eliminate its application to input processing. There is now
no longer such a thing as an "entity" in the groff language.
* doc/groff.texi (Character Translations): Do it. Also clarify
"nothing" as "the dummy character".
(Using Symbols): Do it. Also recast explanation of difference between
characters and glyphs. Explicitly state that spaces aren't glyphs.
Document that `rchar` request can't remove definitions supplied by
font description files.
(Ligatures and Kerning): Speak of "special characters", not
"entities".
(Other Differences): Recast discussion of character-to-glyph
transformation. Stop qualifying characters as "input". Recast
discussion of example.
* font/devutf8/NOTES: Revise use of terminology. Perform a Kemper
notectomy. Wrap long lines.
* man/groff.7.man (Request short reference) <char>: Speak of a "special
character", not an "entity".
<rchar>: Document that request can't remove definitions supplied by
font description files.
* man/groff_diff.7.man (Implementation differences): Sync with our
Texinfo manual.
The use of "entity" to describe how a glyph gets mapped back to a
character (sequence) for the HTML and terminal output devices is
retained. That usage is restricted to discussion of output drivers
(code comments and function names notwithstanding).
|
|
|
|
| |
Use "@code{\@key{RET}}" and "@code{\@key{SP}}" consistently.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This material dates to commit 21260e1cd2, 7 June 2002. Anyone using
.tr éÉ
back then, or, since December 2005 when preconv(1) became available,
using that, must have long since migrated.
Also this passage is getting in the way of my terminological reforms.
Entities begone!
|
|
|
|
|
|
|
|
|
|
| |
* Introduce term "ordinary character", an input character that is not
invalid (cf. "special character").
* Recast discussion of control, no-break control, and escape control
characters in terms of ordinary characters, ruling out the surmise
that a special character can serve as any of these.
* Parallelize wording of these.
* Tighten and align wording with this terminology.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(One hopes.)
* doc/groff.texi (Sentences):
* man/roff.7 (Concepts): Do it.
Fixes <https://savannah.gnu.org/bugs/?64091>. Thanks to Ingo Schwarze
and Dave Kemper for the report.
Also fix whitespace nit. Thanks to Dave Kemper, he of the unflinching
osprey gaze.
|
|
|
|
| |
Thanks to Dave Kemper for catching this.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Qualify claim that text lines produce output--they don't (right away)
if they're diverted.
* Fix copy-and-paste goof in description of `rj` request.
* Use Texinfo @key command to mark keyboard control character input.
* Refer to enablement _status_ as a Boolean value.
* Prefer "non-positive" over "nonpositive".
* Use Texinfo @: command after prose colons, for consistency with the
rest of this document.
* Drop unnecessary commas.
* Drop empty requests in an example where we desperately need the vees.
* Use active voice more, and otherwise tighten wording to buy vees and
improve page layout.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Discuss alignment, adjustment, and margins more carefully. Adjustment
doesn't spread output lines to "both margins" if the indentation is
nonzero. Describe the adjustment process explicitly. Add emphasis
distinguishing `.ce` from `.ad c`. Drop terms "ragged-left" and
"ragged-right" from running text (but keep their concept index entries).
|
| |
|
|
|
|
|
| |
The changes I attributed to DWB 1.0 occurred earlier, in Unix System
III.
|
|
|
|
|
|
|
|
| |
* The no-break control character influences the interpretation of
control lines, not requests per se.
* Replace examples of typesetting output devices with their names in
groff (i.e., as arguments to '-T')--not the names of the file formats
these output devices generate.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Kick mention of region option case-invariance down to "GNU tbl
enhancements" subsection.
* Discuss the content of column descriptors _before_ discussing how
they're separated.
* Arrange mentions of column modifier correspondence to *roff requests
consistently, _after_ covering the syntax of those modifiers.
* Clarify that tbl doesn't perform measurements itself; it constructs
formatter instructions to do so.
* Tighten wording.
Also adjust dead-tree pagination.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Per Bruno Haible, GNU/Hurd is passing all tests as of 1.23.0.rc4.
Regarding shebangs, groff has unfortunately done its part in spreading a
myth. See <https://savannah.gnu.org/bugs/?64058>.
|
|
|
|
|
| |
* Advise reader to not necessarily take "/usr/local" literally.
* Admit that SunOS employed non-standard extensions to man(7) as well.
|
|
|
|
| |
Also borrow wording from "ANNOUNCE".
|
| |
|
|
|
|
|
|
|
| |
Explain the order that it's in, to aid readers and, I hope, help
maintainers keep it in order.
Still to do: replace Git commit info with groff release info.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* doc/groff.texi (Postprocessor Access):
* man/groff.7 (Request short reference): Do it.
Fixes <https://savannah.gnu.org/bugs/?62695>.
I don't know if we need to keep these. They do much the same thing as
`device`, and are implemented nearly identically to each other. They
have only one user, the also undocumented "devtag.tmac".
One difference is that the `device` request constructs a "macro"
(internally to GNU troff), and `tag{,a}` construct strings (from groff's
string class, not the C++ standard library's).
Possibly the type used for storage of the node contents is intended to
address some of the same problems we've seen crop up in issues like
Savannah #63074.
|
|
|
|
| |
Use correct metasyntactic variable name. Use font alternation macro.
|
|
|
|
|
| |
Align language with forthcoming (post-1.23.0) changes from Savannah
ticket #63967.
|
| |
|
|
|
|
| |
Thanks to Doug McIlroy and Ralph Corderoy for the feedback.
|
| |
|
| |
|
| |
|
|
|
|
| |
Use font alternation, not simple font selection.
|
| |
|
|
|
|
| |
The list below this subsection title isn't comprehensive.
|
|
|
|
| |
When forcing a page break to start a new section, break the line first.
|
|
|
|
|
| |
* Mention the special behavior of the % character in titles.
* Characterize traps as a formatter feature.
|
| |
|
|
|
|
|
| |
Also fix an orphaned line by adjusting dead-tree typography of `P` macro
description.
|
|
|
|
|
|
|
| |
* Drop redundant use of `No` macro immediately after `Ns`.
* Drop second argument to `Xr` where it is needlessly specific.
* Clarify: Replace "flush left" with "indentation of zero".
* Tweak grammar.
|
|
|
|
|
| |
Since "call" is an important term of art in mdoc composition, use a
different word for its mundane meaning of appellation.
|
| |
|
|
|
|
| |
...but drop one cross reference that is already quite close to another.
|
| |
|
| |
|
|
|
|
| |
Fix orphaned partial word and buy a vee for a forthcoming commit.
|
|
|
|
| |
We have a "Diversions" section for it to follow now.
|
|
|
|
| |
Use correct lettercase.
|