>> Surprise: in a font description file "scalesize" is called "sizescale".
>> [...]
> Huh?
> $ man 7 groff_diff | grep scalesize | wc -l
> 0
All too true. I don't know how I managed to copy the quote from
groff_diff(7) wrongly.
I hope the rest of my note is more accurate.
Doug
On Mon Feb 10, 2025 at 12:07 AM CET, Douglas McIlroy wrote:
> groff_diff(7) says scalesize is 1 by default and gives this
> rule for interpreting scalesize:
>
>[given] arguments that represent a type size in points the
>formatter multiplies by scalesize and converts to an integer
>
> Surpri
groff_diff(7) says scalesize is 1 by default and gives this
rule for interpreting scalesize:
[given] arguments that represent a type size in points the
formatter multiplies by scalesize and converts to an integer
Surprise: in a font description file "scalesize" is called "sizescale".
I ran
Hi Branden,
On Sun Feb 9, 2025 at 3:28 PM CET, G. Branden Robinson wrote:
> At 2025-02-07T16:20:23+0100, onf wrote:
> > I've been wondering lately about the rationale behind solving the
> > problem of font sizes being integer-only by adding scaled points.
>
> It's covered in groff_diff(7), the man
Hello Ingo,
thank you for your detailed response.
On Sun Feb 9, 2025 at 7:38 PM CET, Ingo Schwarze wrote:
> onf wrote on Sat, Feb 08, 2025 at 01:35:31AM +0100:
> [...]
> > 1. Escape sequences in the sense of inline commands, i.e. how to mark
> > up syntax like \f[font]? Does it fit under Cm?
Hi onf,
On Sun, Feb 09, 2025 at 09:17:56PM +0100, onf wrote:
> Hi Alex,
>
> On Sun Feb 9, 2025 at 8:11 PM CET, Alejandro Colomar wrote:
> > This is off-topic, but I don't know where to ask.
> >
> > Thing is, I found a bug in a Plan9 string API: seprintf(2).
> > I discussed the bug with Doug some
Hi Alex,
On Sun Feb 9, 2025 at 8:11 PM CET, Alejandro Colomar wrote:
> This is off-topic, but I don't know where to ask.
>
> Thing is, I found a bug in a Plan9 string API: seprintf(2).
> I discussed the bug with Doug some time ago, and ISTR that we agreed
> that the API has a design bug. And we m
Hi,
This is off-topic, but I don't know where to ask.
Thing is, I found a bug in a Plan9 string API: seprintf(2).
I discussed the bug with Doug some time ago, and ISTR that we agreed
that the API has a design bug. And we might be able to fix it. But I
don't know who maintains that code. I thin
Hello,
onf wrote on Sat, Feb 08, 2025 at 01:35:31AM +0100:
> On Fri Jan 24, 2025 at 7:51 PM CET, Ingo Schwarze wrote:
>> While parts of it may be a bit dusty and i might have to check whether
>> a few things could become even better by providing more stringent or
>> more relaxed advice as experie
At 2025-02-07T16:20:23+0100, onf wrote:
> I've been wondering lately about the rationale behind solving the
> problem of font sizes being integer-only by adding scaled points.
It's covered in groff_diff(7), the man page I believe you said you
always forget about.
groff_diff(7):
Fractional type
On Sat, Feb 08, 2025 at 08:37:58PM +0100, onf wrote:
> I understand your use case, but it still seems simpler to me to use
> sp over strings. You could define registers which specify the ratio
> between the top and bottom space, so that instead of 1v:1v it becomes
> e.g. 0.4v:0.6v. Obviously the ra
[CC += Ingo]
Hi Branden,
On Sat, Feb 08, 2025 at 06:45:31PM -0600, G. Branden Robinson wrote:
> https://git.savannah.gnu.org/cgit/groff.git/tree/tmac/an.tmac?h=1.23.0#n162
Hmmm. What would be affected by changing that default? Does it affect
anything other than a literal tab in source code? I
12 matches
Mail list logo
