Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

troff: support \~ as an alias for \ #83

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

g-branden-robinson
Copy link

In groff, Heirloom Doctools troff, and neatroff, the \~ escape
sequence produces an adjustable (paddable) but unbreakable space.
mandoc, which does not perform adjustment or render to typesetters,
supports the escape sequence as a synonym for \ , the same as \0.

This extension is of long pedigree: groff has supported it for at least
30 years, Heirloom for 17, mandoc for 13, and neatroff for 6.

Do the same as mandoc to prevent mis-rendering of documents using this
escape sequence. Heirloom Doctools troff, a descendant of Documenter's
Workbench troff, would be a good place to look for a compatible
implementation of the adjustable semantics for this sequence.

In groff, Heirloom Doctools troff, and neatroff, the `\~` escape
sequence produces an adjustable (paddable) but unbreakable space.
mandoc, which does not perform adjustment or render to typesetters,
supports the escape sequence as a synonym for `\ `, the same as `\0`.

This extension is of long pedigree: groff has supported it for at least
30 years, Heirloom for 17, mandoc for 13, and neatroff for 6.

Do the same as mandoc to prevent mis-rendering of documents using this
escape sequence.  Heirloom Doctools troff, a descendant of Documenter's
Workbench troff, would be a good place to look for a compatible
implementation of the adjustable semantics for this sequence.
@jclulow
Copy link
Member

jclulow commented Aug 13, 2022

Hi @g-branden-robinson!

First up, welcome, and thanks for working on a change to contribute! Though we mirror our source to GitHub, we generally prefer to discuss contributions on our developer mailing list and get them reviewed through our Gerrit instance.

Our contribution process is outlined on our site: https://illumos.org/docs/contributing/

If you have any questions, we're always available on the mailing list and in #illumos on Libera IRC to help out!

Cheers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants