G. Branden Robinson to Anton Shepelev:
> > I wonder what Debian user or developer dis-
> > liked those SGR sequences emitted by groff...
>
> Well, here's one of them.
>
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=312935
>
> ...with my lengthy rebuttal and defense of groff's
> behav
Jim Hall:
> Several weeks ago, I interviewed Dr. Marshall Kirk
> McKusick about how he writes his books using groff:
> https://technicallywewrite.com/2023/10/13/groffbooks
McKusick writes about orphan elimination, end-of-
line tweaking, and balancing of text on facing
pages. Does that
Dear All,
while experimenting with the mm macro package for the first time I
noticed that from the very start it did not behave exactly as expected
--- which was entirely due to my lacking of understanding of some basics.
Starting a text without any macro yields just a page flooded with text
---
Hi Oliver,
At 2023-11-21T13:37:13+0100, Oliver Corff via wrote:
> while experimenting with the mm macro package for the first time I
> noticed that from the very start it did not behave exactly as expected
> --- which was entirely due to my lacking of understanding of some
> basics.
Before diggin
Hi Anton,
At 2023-11-21T11:36:09+0300, Anton Shepelev wrote:
> G. Branden Robinson to Anton Shepelev:
> >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=312935
[...]
> > The more I learned, the more I realized just how
> > wrong that guy was.
>
> I have read it and agree with you. `grott
Dear Branden,
you got me immediately on this one. Please accept my sincerest
apologies, the production environment here still is based on 1.22.4.
I'll take a new tour of the 1.23.0 man pages.
Best regards,
Oliver.
On 21/11/2023 14:51, G. Branden Robinson wrote:
Hi Oliver,
At 2023-11-21T13:
Dear All,
currently I am working on a translation of a scientific article. So I
prepared an mm source file, one paragraph original text, to be commented
out once the translation of that paragraph is finished, then followed by
the next paragraph, to be commented out and followed by translation, an
On 11/21/23, Oliver Corff wrote:
> So the first line effectively was:
>
> .ig
>
> No wonder it did not work. Would it be meaningful to (optionally) tell
> groff to jump over or throw away BOMs it encounters at the beginning of
> a file? Or should sanity and awareness be left with the astute user?
Hi David,
thank you for your insight!
You are right, currently I do not need Chinese in the translation, it is
all kept within .id .. blocks.
However, there may always be a case that I'll have to quote single
Chinese words or phrases in my translation.
Best regards,
Oliver.
On 21/11/2023 17
Dear All,
the first steps with mm look quite promising, and the (optional) goal of
approaching the typesetting appearance of the original in the
translation (for the benefit of the reader who wants to consult the
original) is definitely achievable.
Two small hurdles remain:
1. In mm, I did not
Dear All,
I came across another weird problem.
In my document, I have
.TL
My document title
.AF "¹ First Institute; ² Second Institute; ³ Third Institute"
.AU
John First¹
Bob Second²
Martha Third³
.AS
My abstract
.AE
.MT 4
Which produces
John First¹ Bob Second² Martha Third³
My document titl
For convenience, I add a stripped down minimal example with real-life data.
Best regards,
Oliver.
On 21/11/2023 19:49, Oliver Corff wrote:
Dear All,
I came across another weird problem.
In my document, I have
.TL
My document title
.AF "¹ First Institute; ² Second Institute; ³ Third Institut
eqn issues a .lf for every .EN. In 1.23.0 the line number is assigned as if
there were only one line of eqn text between .EQ and .EN, regardless of how
many lines actually are present. Thus the two fragments below yield
identical sequences of .lf requests
.EQ.EQ
1
Hi Doug,
At 2023-11-21T15:06:45-0500, Douglas McIlroy wrote:
> eqn issues a .lf for every .EN. In 1.23.0 the line number is assigned
> as if there were only one line of eqn text between .EQ and .EN,
> regardless of how many lines actually are present. Thus the two
> fragments below yield identical
At 2023-11-21T12:02:20+0300, Anton Shepelev wrote:
> Jim Hall:
>
> > Several weeks ago, I interviewed Dr. Marshall Kirk
> > McKusick about how he writes his books using groff:
> > https://technicallywewrite.com/2023/10/13/groffbooks
>
> McKusick writes about orphan elimination, end-of-
> line
Hi Oliver,
At 2023-11-21T15:06:37+0100, Oliver Corff via wrote:
> Dear Branden,
>
> you got me immediately on this one. Please accept my sincerest
> apologies, the production environment here still is based on 1.22.4.
No apologies necessary; as a Debian user since the 1990s I know how long
it ca
Hi Oliver,
At 2023-11-21T18:56:51+0100, Oliver Corff wrote:
> the first steps with mm look quite promising, and the (optional) goal
> of approaching the typesetting appearance of the original in the
> translation (for the benefit of the reader who wants to consult the
> original) is definitely ach
Dear Branden,
thank you very much for the answer!
The journal title can be repeated in the page header. The original
document happens do to it, too, and thus this is a perfect solution for
my particular case.
I get it: the .AF points to the company or institution publishing the
document, unlike
Hi Oliver,
At 2023-11-21T19:49:09+0100, Oliver Corff wrote:
> I tried to play with 4.MT by copying and renaming it as 6.MT and
> calling .MT 6, but then the result is as if I had no .MT call at all.
> Strange.
As weird as it seems, that's documented.
MT [type [addressee]]
Selec
Hi Branden,
I get *your* point, but I was lured to believe that I could write my own
Memorandum Type by copying an existing one in the ../tmac/mm/ directory
and assigning an appropriate number. I thought "types 0 to 5 are
supported" can be interpreted as "a file for these types is provided",
whic
Hi Oliver,
At 2023-11-21T22:58:45+0100, Oliver Corff via wrote:
> I get *your* point, but I was lured to believe that I could write my
> own Memorandum Type by copying an existing one in the ../tmac/mm/
> directory and assigning an appropriate number. I thought "types 0 to 5
> are supported" can b
21 matches
Mail list logo
