On Wed, May 28, 2014, Ulrich Lauther wrote:
> I think, the experiment shows that running time is no issue at all.
This is terrific news. One of groff's greatest strengths is speed. It
will be wonderful if improved formatting can be achieved with no
loss in that department. Thanks, Ulrich, for t
> The following line is from groff_char.man:
>
> \[vA] \e[vA] uni21D5 u21D5 vertical double arrow in both directions
>
> I couldn't find this character \[vA]. Some idea?
Originally contained in the glyph sets of -Tlj4 and -Tdvi; added to
-Tps later on, using the standard AGL name `uni21D5'.
> The notes in `groff_char.7' are complete now, that makes this
> man-page into a useful information center.
Thanks.
> The man-page `groff.7' has a section about `special characters'.
> This section is not really useful. It is far from being complete.
> I see the following kinds of improvement:
Hello,
in troff the Times Roman Bold \(sq is filled solid black. In groff there is no
difference between any Times Roman font.
Is there a way to get the standard (UNIX V7) behaviour of a solid filled bold
\(sq?
(I also checked heirloom troff, there bold \(sq is as expected.)
Or is there any o
On Mon, Mar 31, 2014 at 07:44:07PM -0400, Peter Schaffter wrote:
> Here's the bare bones version of the algorithm I was thinking of
> when I proposed improving line formatting by getting groff to
> shoulder the burden for some of the work we do manually. It's
> written out in brute-force pseudo-co
