On Thu, Sep 5, 2024 at 2:31 PM Deri wrote:
> if Dave wants to use use Spin̈al Tap
> This seems to work:-
>
> printf ".ft TINOR\n.ps 18\nSpin\h'-5p'\[u0308]\h'+5p'al Tap\n.pdfbookmark 1
> Spi\[u006E_0308]al Tap"|test-groff -Tpdf -ms > Spin̈alTap.pdf
Just want to point out that the \h escapes shoul
would help me any.
Nah, why would anyone waste effort on THAT? Real hackers go straight to
the source, every time. Specs are for suits. UTSL!
> > Though some irritated Swede is bound to knock us about like tenpins
> > if we keep deliberately misspelling "också" li
On Thursday, 5 September 2024 04:15:44 BST G. Branden Robinson wrote:
> [fair warning: _gigantic_ message, 5.7k words]
> Hi Deri & Dave,
Hi Branden,
> I'll quote Dave first since his message was brief and permits me to make
> a concession early.
>
> At 2024-09-04T15:05:38-0500, Dave Kemper wro
[fair warning: _gigantic_ message, 5.7k words]
Hi Deri & Dave,
I'll quote Dave first since his message was brief and permits me to make
a concession early.
At 2024-09-04T15:05:38-0500, Dave Kemper wrote:
> On Wed, Sep 4, 2024 at 11:04 AM Deri
> wrote:
> > The example using \[u012F] is superior
On Wed, Sep 4, 2024 at 11:04 AM Deri wrote:
> The example using \
> [u012F] is superior (in my opinion) because it is using a single glyph the
> font designer intended for that character rather than combining two glyphs
> that don't marry up too well.
I agree with this opinion.
> If you know of
On Sunday, 1 September 2024 06:09:17 BST G. Branden Robinson wrote:
> Hi Deri,
>
> At 2024-08-31T17:07:28+0100, Deri wrote:
> > On Saturday, 31 August 2024 00:07:57 BST G. Branden Robinson wrote:
> [fixing two of my own typos and one wordo in the following]
>
> > > It would be cleaner and simpler
Hi Deri,
At 2024-08-31T17:07:28+0100, Deri wrote:
> On Saturday, 31 August 2024 00:07:57 BST G. Branden Robinson wrote:
[fixing two of my own typos and one wordo in the following]
> > It would be cleaner and simpler to provide a mechanism for
> > processing a string directly, discarding escape seq
On Saturday, 31 August 2024 00:07:57 BST G. Branden Robinson wrote:
> It would be cleaner and simpler to provide a mechanism for processing a
> string directly, discarding escape sequences (like vertical motions or
> break points [with or without hyphenation). This point is even more
> emphatic be
Hi folks,
Those of us who worked with groff 1.22.4 may remember a couple of
diagnostic messages that gobsmacked one with their incomprehensibility.
Here's the source code that produced them.
error("can't transparently output node at top level");
error("can't translate %1 to special character
