Good morning Branden, Tadziu,
On 25/7/24 11:10, G. Branden Robinson wrote:
At 2024-07-24T22:27:31+0200, Tadziu Hoffmann wrote:
a "margin" measures an extent of whitespace (or "negative space"),
whereas the `sp` request positions the _text baseline_,
The first is correct and the second incorre
Hi Tadziu,
At 2024-07-24T22:27:31+0200, Tadziu Hoffmann wrote:
> > > a "margin" measures an extent of whitespace (or "negative space"),
> > > whereas the `sp` request positions the _text baseline_,
>
> The first is correct and the second incorrect for [g]troff.
I will defend my formulation. `sp
> > a "margin" measures an extent of whitespace (or "negative space"),
> > whereas the `sp` request positions the _text baseline_,
The first is correct and the second incorrect for [g]troff.
In troff (and nroff), if you say
.sp |0
then this does not mean "put the baseline at the top of the pa
[self-follow-up]
At 2024-07-24T13:28:04-0500, G. Branden Robinson wrote:
> I notice now that those claims about the margin sizes might be off by
> one vee; in my experience, a "margin" measures an extent of whitespace
> (or "negative space"), whereas the `sp` request positions the _text
> baseline
Hi Tomek,
the Tibetan font isssue is a difficult nut to crack, for two main reasons:
- the groff font tables do not contain information provided by the
ligature mechanism of Truetype or Opentype fonts
- groff itself is only set up ("hard wired") for a small number of
conventional ligatures used
At 2024-07-24T10:15:47+0200, me.gr...@mro.name wrote:
> to keep it simple I went without macros and figured out the commands
> from https://www.gnu.org/software/groff/manual/groff.html without
> further help.
I'm glad the manual proved adequate here! I've spent several years
attempting to improve
Hi Lukas,
Are you subscribed to groff@gnu? I prefer not to mail both lists and
people unless they express a preference for that (ideally via mail
headers that communicate this, and if my MUA is clueful enough to
interpret such indications).
At 2024-07-24T11:04:04+0200, Lukas Javorsky wrote:
> I
Hi,
I found multiple defects in Groff's source code, and I would like to
help with fixing them by contributing several commits.
I didn't find much information about the contribution process on the
website [1], so I decided to ask here for more information. Could you
please help me figure out what
to keep it simple I went without macros and figured out the commands from
https://www.gnu.org/software/groff/manual/groff.html without further help.
For now I may go with https://mro.name/2024/brief-dina4.roff
Having an automatic header line on subsequent pages would be a plus, but isn't
wort
