bug-groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #61710] [me] $v and $V are in the wrong namespace


From: Dave
Subject: [bug #61710] [me] $v and $V are in the wrong namespace
Date: Wed, 5 Jan 2022 14:09:05 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Firefox/45.0

Follow-up Comment #8, bug #61710 (project groff):

[comment #4 comment #4:]
> Yes, and registers `fv`, `pv`, `qv`, `sv`, tv` are not implemented to
> manage the vertical spacing of the various contextual type faces.
> 
> Should they be?  Happily, all five names are available.
> 
> This would make me(7)'s design more orthogonal, the cost of five
> registers that will seldom be used (because having the vertical spacing
> be proportional to the type size is frequently what is desired), and for
> the sake of backward compatibility we'll have to retain `sz` own
> non-orthogonality which will stand out all the more.

Hold on, let me make sure I understand this proposal.  Are you saying the five
new *v registers would be, like their *p counterparts, specified in points (or
other size units)?

I ask because, as you note, making vertical spacing proportional to the type
size is common.  So the user who currently sets $v to, say, 140 (a
percentage), at the top of a document, can forget about it thereafter, and
change pp a dozen times over the course of the document, knowing that the
leading will follow the type size.  If the new pv register is also a
percentage, then the transition from $v to pv is easy.  But if pv is a fixed
size, and $v goes away, the migration has gotten a lot more complicated for
this user.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61710>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]