[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #64588] [mm] H1dot register is inflexible
From: |
G. Branden Robinson |
Subject: |
[bug #64588] [mm] H1dot register is inflexible |
Date: |
Thu, 24 Aug 2023 04:16:43 -0400 (EDT) |
URL:
<https://savannah.gnu.org/bugs/?64588>
Summary: [mm] H1dot register is inflexible
Group: GNU roff
Submitter: gbranden
Submitted: Thu 24 Aug 2023 08:16:41 AM UTC
Category: Macro mm
Severity: 1 - Wish
Item Group: Feature change
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Thu 24 Aug 2023 08:16:41 AM UTC By: G. Branden Robinson <gbranden>
I have some complaints.
* I don't like the name "H1dot".
* The document author might want the dots to appear in headings only at a
certain heading level; in other words, why don't we have a threshold register
for this as we do almost all other heading behavior?
* The document author might want dots in the formatted heading but not in
cross references to them using _groff mm_'s "new (sic) reference system".
They get unconditionally stored, except at the first level if `H1dot` is
cleared. This is inflexible; it's much easier to not store the dot in the
first place than strip it out later.
For example, the package defaults give us outcomes like this.
See chapter 3., page 5.
See chapter 2.1, page 3.
We might consider storing strings for the headings in end-dotted _and_
non-end-dotted forms, trusting the user to (re-)define the Qrf string as
needed (and as already encouraged).
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64588>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug #64588] [mm] H1dot register is inflexible,
G. Branden Robinson <=