Re: [BUG] italics run past where they should

Hi Alex, At 2022-08-16T23:36:40+0200, Alejandro Colomar wrote: > Okay, so I tried with Debian stable, and groff built from source > doesn't have a bug there. > > To reproduce the bug you need: > > - Debian Sid > - Any pager that does highlighting will do (tried less and batcat). > - Any

[groff] 28/31: [ms]: Support pic(1) "flyback" feature.

gbranden pushed a commit to branch master in repository groff. commit 33c2f8cf681ff93804ea8a389f31f29764349d4e Author: G. Branden Robinson AuthorDate: Mon Aug 15 01:04:08 2022 -0500 [ms]: Support pic(1) "flyback" feature. * tmac/s.tmac (PF): Add macro; it does what `PE` formerly

[groff] 30/31: NEWS: Add item for me(7)'s `PF` macro.

gbranden pushed a commit to branch master in repository groff. commit b4bf6ddaf4b4bd3a5fe67826e5635c2b013dc5b0 Author: G. Branden Robinson AuthorDate: Mon Aug 15 21:08:54 2022 -0500 NEWS: Add item for me(7)'s `PF` macro. --- NEWS | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-)

[groff] 16/31: groff_man_style(7): Drop claim about \c behavior.

gbranden pushed a commit to branch master in repository groff. commit 61e1f10ea969db1f465de4057fa92471beaa3355 Author: G. Branden Robinson AuthorDate: Sun Aug 14 05:20:47 2022 -0500 groff_man_style(7): Drop claim about \c behavior. groff 1.22.4's groff(7) page said, "Anything after

[groff] 27/31: doc/groff.texi: Fix missing bracket in synopsis.

gbranden pushed a commit to branch master in repository groff. commit 86484635302b9d127b2592f3af003910264c74a2 Author: G. Branden Robinson AuthorDate: Mon Aug 15 00:35:11 2022 -0500 doc/groff.texi: Fix missing bracket in synopsis. --- doc/groff.texi | 2 +- 1 file changed, 1 insertion(+),

[groff] 25/31: [mm]: Add new `PY` macro for pic flyback support.

gbranden pushed a commit to branch master in repository groff. commit 9101cecb3b2a7b08f5469497faffc0e2ba5001eb Author: G. Branden Robinson AuthorDate: Mon Aug 15 00:00:02 2022 -0500 [mm]: Add new `PY` macro for pic flyback support. * contrib/mm/m.tmac (PY): Add new macro.

[groff] 31/31: groff_mm(7): Revise discussion of eqn features.

gbranden pushed a commit to branch master in repository groff. commit 342a115cdeb1a4d1f4a7e16e2fbfcb53516d7cd7 Author: G. Branden Robinson AuthorDate: Tue Aug 16 04:55:58 2022 -0500 groff_mm(7): Revise discussion of eqn features. * Stop using the term "delimiter" confusingly. It

[groff] 15/31: groff_man*(7): Use plan9port's formal name.

gbranden pushed a commit to branch master in repository groff. commit 4571cd8bc62d968c1a56740bed8fa5af0bc228df Author: G. Branden Robinson AuthorDate: Sun Aug 14 05:18:49 2022 -0500 groff_man*(7): Use plan9port's formal name. --- tmac/groff_man.7.man.in | 4 ++-- 1 file changed, 2

[groff] 29/31: groff_ms(7): Adjust dead-tree typography.

gbranden pushed a commit to branch master in repository groff. commit 96c7ea4f96ba5ff8a185eb30ac0b44758e144d26 Author: G. Branden Robinson AuthorDate: Mon Aug 15 01:05:07 2022 -0500 groff_ms(7): Adjust dead-tree typography. --- tmac/groff_ms.7.man | 7 +++ 1 file changed, 7

[groff] 14/31: groff_man_style(7): Adjust dead-tree typography.

gbranden pushed a commit to branch master in repository groff. commit e3501a9351abfcdae236ef1021e89b171f711bae Author: G. Branden Robinson AuthorDate: Sun Aug 14 05:16:53 2022 -0500 groff_man_style(7): Adjust dead-tree typography. Give quote-like characters ' " and ` some "elbow

[groff] 18/31: tbl(1): Document nroff mode vertical space issue.

gbranden pushed a commit to branch master in repository groff. commit 7925122f390decc2cdcc6072645b9e16190587ad Author: G. Branden Robinson AuthorDate: Sun Aug 14 05:59:16 2022 -0500 tbl(1): Document nroff mode vertical space issue. For me, at least, this knowledge was hard-won.

[groff] 17/31: groff_man_style(7): Clarify and tighten wording.

gbranden pushed a commit to branch master in repository groff. commit e683a7670651bea6c8e7afd399ef424ca676a2a7 Author: G. Branden Robinson AuthorDate: Sun Aug 14 05:52:53 2022 -0500 groff_man_style(7): Clarify and tighten wording. --- tmac/groff_man.7.man.in | 10 +++--- 1 file

[groff] 26/31: [ms]: Validate `PS` arguments better.

gbranden pushed a commit to branch master in repository groff. commit b16ad66b8e4d50ba0b76536833eab853fc2ff8d0 Author: G. Branden Robinson AuthorDate: Mon Aug 15 00:24:48 2022 -0500 [ms]: Validate `PS` arguments better. * tmac/s.tmac (@PS): Validate better; check for 2 arguments

[groff] 12/31: groff_man_style(7): Relocate material.

gbranden pushed a commit to branch master in repository groff. commit b612a98bc5c70f22fc0e6465480bf02f9a63d3f8 Author: G. Branden Robinson AuthorDate: Sat Aug 13 12:44:04 2022 -0500 groff_man_style(7): Relocate material. Shift special character discussion so we can give it a

[groff] 10/31: [docs]: Document plan9port troff support for `\~`.

gbranden pushed a commit to branch master in repository groff. commit 14eebb6b7471de5903098178cc6b11db49289864 Author: G. Branden Robinson AuthorDate: Sat Aug 13 11:59:26 2022 -0500 [docs]: Document plan9port troff support for `\~`. Update Plan 9 from User Space troff info thanks

[groff] 23/31: [pic]: Refactor `flyback_flag`.

gbranden pushed a commit to branch master in repository groff. commit 52964e94c67fbf0c8dc167464f90c925caf2f2ed Author: G. Branden Robinson AuthorDate: Sun Aug 14 22:47:29 2022 -0500 [pic]: Refactor `flyback_flag`. * src/preproc/pic/main.cpp: * src/preproc/pic/pic.h: *

[groff] 24/31: [pic]: Recognize `.PY` as synonym of `.PF`.

gbranden pushed a commit to branch master in repository groff. commit 1ac8764fa7f3b91e7d2a84261edbdc84c1ae4158 Author: G. Branden Robinson AuthorDate: Sun Aug 14 23:52:40 2022 -0500 [pic]: Recognize `.PY` as synonym of `.PF`. * src/preproc/pic/main.cpp: * src/preproc/pic/pic.h:

[groff] 06/31: pic(1): Guard dot from end-of-sentence detection.

gbranden pushed a commit to branch master in repository groff. commit 0fd411def4db9ad56fe31aa0658d64c59f824b86 Author: G. Branden Robinson AuthorDate: Thu Aug 11 22:31:34 2022 -0500 pic(1): Guard dot from end-of-sentence detection. --- src/preproc/pic/pic.1.man | 4 ++-- 1 file changed, 2

[groff] 09/31: [docs]: Shift discussion of `\~` portability.

gbranden pushed a commit to branch master in repository groff. commit cc1af07711c7b8ea3a060b3b76c8353ddf270b1d Author: G. Branden Robinson AuthorDate: Sat Aug 13 03:38:46 2022 -0500 [docs]: Shift discussion of `\~` portability. * doc/groff.texi (Request and Macro Arguments): Move

[groff] 22/31: [mm]: Tweak diagnostic handling.

gbranden pushed a commit to branch master in repository groff. commit bd06e20cd9692b427293619843a0623e49c37689 Author: G. Branden Robinson AuthorDate: Sun Aug 14 22:25:08 2022 -0500 [mm]: Tweak diagnostic handling. * contrib/mm/m.tmac (@warning, @error): Stop pointlessly using

[groff] 05/31: [docs]: Fix content, style, and markup nits.

gbranden pushed a commit to branch master in repository groff. commit acae9d3827237c702ea5fc3315a7f35273f757e0 Author: G. Branden Robinson AuthorDate: Thu Aug 11 17:32:11 2022 -0500 [docs]: Fix content, style, and markup nits. * man/groff_font.5.man: - Tighten wording.

[groff] 03/31: groff(1): Fix unescaped hyphen.

gbranden pushed a commit to branch master in repository groff. commit 2e5a9c79f0b28b1f31a3e741ce3fe3483c2fa49b Author: G. Branden Robinson AuthorDate: Tue Aug 9 14:21:05 2022 -0500 groff(1): Fix unescaped hyphen. Thanks to Dave Kemper for the catch. --- src/roff/groff/groff.1.man

[groff] 21/31: [mm]: Validate `PS` macro calls better.

gbranden pushed a commit to branch master in repository groff. commit e3335548f7b1bc13d48371bcd0641499e6f8ad56 Author: G. Branden Robinson AuthorDate: Sun Aug 14 22:08:48 2022 -0500 [mm]: Validate `PS` macro calls better. * contrib/mm/m.tmac (PS): Validate better; check for 2

[groff] 20/31: [mm]: Refactor; drop dead code in `PS` macro.

gbranden pushed a commit to branch master in repository groff. commit 4c40d20e7bfdd753f8c4b76c90319533078342d2 Author: G. Branden Robinson AuthorDate: Sun Aug 14 22:06:25 2022 -0500 [mm]: Refactor; drop dead code in `PS` macro. * contrib/mm/m.tmac (PS): Refactor; drop dead code.

[groff] 08/31: groff_man*(7): Adjust dead-tree typography.

gbranden pushed a commit to branch master in repository groff. commit 2d722b94286e28ffa603c39f761561e42d36334e Author: G. Branden Robinson AuthorDate: Sat Aug 13 03:37:10 2022 -0500 groff_man*(7): Adjust dead-tree typography. --- tmac/groff_man.7.man.in | 10 ++ 1 file changed, 10

[groff] 01/31: groff_man*(7): Fix content nits.

gbranden pushed a commit to branch master in repository groff. commit a7c8d0fb9569ea2486c9ead838d27d57220ecd03 Author: G. Branden Robinson AuthorDate: Fri Aug 5 12:46:03 2022 -0500 groff_man*(7): Fix content nits. Strictly, no macro ever accepts any arguments "on the next line"

[groff] 02/31: groff_man_style(7): Fix terminology nit.

gbranden pushed a commit to branch master in repository groff. commit 402da0123b6c21bf778e938406b3ad558544535c Author: G. Branden Robinson AuthorDate: Fri Aug 5 13:42:28 2022 -0500 groff_man_style(7): Fix terminology nit. Say "split" instead of "break", to avoid confusion with

[groff] 11/31: groff_man_style(7): Document portability of `\:`.

gbranden pushed a commit to branch master in repository groff. commit 4dc92d1ad89801a18cd7b6b03bd98a7a6351e690 Author: G. Branden Robinson AuthorDate: Sat Aug 13 12:30:30 2022 -0500 groff_man_style(7): Document portability of `\:`. Lift information from comments to formatted text.

[groff] 19/31: eqn(1): List recognized primitives, predef macros.

gbranden pushed a commit to branch master in repository groff. commit 8f841ba67cc98dc5bb8ade57c440261819e71067 Author: G. Branden Robinson AuthorDate: Sun Aug 14 19:34:24 2022 -0500 eqn(1): List recognized primitives, predef macros. * src/preproc/eqn/eqn.1.man: Expand to include

[groff] 04/31: groff_man*(7): Tighten and generalize.

gbranden pushed a commit to branch master in repository groff. commit 4f4dbf92ba4525332b3c00448a74ff28b9bf1e27 Author: G. Branden Robinson AuthorDate: Wed Aug 10 13:25:38 2022 -0500 groff_man*(7): Tighten and generalize. "tty" isn't an "output device"; that is, it is not a

[groff] 13/31: groff_man_style(7): Clarify spec char portability.

gbranden pushed a commit to branch master in repository groff. commit fd09dfe8851d3a1b95cc0255eb0f92369ee4bc96 Author: G. Branden Robinson AuthorDate: Sat Aug 13 12:47:20 2022 -0500 groff_man_style(7): Clarify spec char portability. Discuss the portability of the reverse solidus

[groff] 07/31: doc/groff.texi: Fix factual error about mandoc.

gbranden pushed a commit to branch master in repository groff. commit 8a49f10dd2c0cac10401f54318bc0c16d5acc552 Author: G. Branden Robinson AuthorDate: Fri Aug 12 20:15:03 2022 -0500 doc/groff.texi: Fix factual error about mandoc. mandoc began recognizing the `\~` escape sequence in

[groff] 01/01: ChangeLog: Fix typo.

gbranden pushed a commit to branch master in repository groff. commit 5b7382dbc7b28c5611400810f31124d2c89e54b2 Author: G. Branden Robinson AuthorDate: Fri Aug 5 02:59:27 2022 -0500 ChangeLog: Fix typo. --- ChangeLog | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: deroff availability

Am Wed, Aug 17, 2022 at 03:47:31AM + schrieb DJ Chase: > Does anyone know how I could get a copy of deroff(1) on my machine > (Fedora Linux 36)? It’s not in the repos — or seemingly any Linux repos > for that matter — and I can’t seem to find the source for it. The Arch Linux User Repository

Re: About groff and dformat

Hello Thomas, Finally I was able to use the dformat without problems. The problem was the order in the pipe. In the original paper the author provided an example on the order of the preprocessors. I did not have the correct order. It should have been !sh dformat.sh format-test.ms | pic | tbl |

Re: About groff and dformat

Hello Thomas, To make sure, I have this in my dformat.sh awk -f dformat.awk $* I tried with the dformat.awk that I have found (https://github.com/arnoldrobbins/dformat) and the dformat.awk that you have pointed out (https://github.com/sathlan/dformat). But still I am getting the same error

deroff availability

Hi everyone, Does anyone know how I could get a copy of deroff(1) on my machine (Fedora Linux 36)? It’s not in the repos — or seemingly any Linux repos for that matter — and I can’t seem to find the source for it. I’ve also tried to find similar tools, such as roff2text, but that actually

Re: Standardize roff

Sam Varshavchik writes: I believe that for man pages, roff should've been replaced by Docbook XML a long time ago. Personally, i'm grateful that it hasn't. Apart from Ingo's thorough critique of DocBook: https://undeadly.org/cgi?action=article=20190419101505 i doubt i'd have had as

Re: Standardize roff

Ingo Schwarze writes: Hi San, Sam Varshavchik wrote on Sun, Aug 14, 2022 at 08:20:34PM -0400: > Ingo Schwarze writes: >> DJ Chase wrote on Sat, Aug 13, 2022 at 05:27:34PM +: >>> Have we ever considered a de jure *roff standard? >> No, i think that would be pure madness given the amount

Re: [BUG] italics run past where they should

Hi Branden, On 8/16/22 22:52, Alejandro Colomar wrote: Hi Branden, On 8/16/22 18:58, Alejandro Colomar wrote: Heh, I just installed three virtual machines: debian stable, testing, and unstable.  Guess what?  None of them reproduce the issue. This is very weird.  AFAIR, the only difference

Re: [BUG] italics run past where they should

Hi Branden, On 8/16/22 18:58, Alejandro Colomar wrote: Heh, I just installed three virtual machines: debian stable, testing, and unstable.  Guess what?  None of them reproduce the issue. This is very weird.  AFAIR, the only difference that I have compared to a clean Sid install, is that I

Re: About groff and dformat

Riza Dindir wrote: > Hello All, Hi! > I am trying to get dformat to work. What I did was this. > > I first tried to include an example dformat script into my document. I > got the first example from the troff.org site > (https://troff.org/prog.html). The first example for the dformat >

Re: [BUG] italics run past where they should

Hi Branden, On 8/16/22 15:31, G. Branden Robinson wrote: At 2022-08-16T15:13:54+0200, Alejandro Colomar wrote: That's weird; I used both xterm and xfce-terminal, and both seem to reproduce it. I documented all of the software I used to reproduce it in this message:

Re: [BUG] italics run past where they should

On 8/16/22 15:31, G. Branden Robinson wrote: printf '\e[1mbold\e[7minversebold\e[27mbold\e[22mnormal\e[0m\n' I see what the words tell. Nothing weird. -- Alejandro Colomar OpenPGP_signature Description: OpenPGP digital signature

About groff and dformat

Hello All, I am trying to get dformat to work. What I did was this. I first tried to include an example dformat script into my document. I got the first example from the troff.org site (https://troff.org/prog.html). The first example for the dformat processor. That example has been using inline

Re: Regarding groff and eqn

Thank you Branden, that was it. Now I can create an inline math expression, although the inline math expression was nonsense in the document :) On Tue, Aug 16, 2022 at 4:23 PM Riza Dindir wrote: > > Oh oh. Tooo many mistakes. What was i thinking. Will try these. Thanks. > > On Tue, Aug 16, 2022,

Re: [BUG] italics run past where they should

At 2022-08-16T15:13:54+0200, Alejandro Colomar wrote: > That's weird; I used both xterm and xfce-terminal, and both seem to > reproduce it. I documented all of the software I used to reproduce it > in this message: > > Ah right,

Re: [BUG] italics run past where they should

Hi Alex, At 2022-08-16T13:57:00+0200, Alejandro Colomar wrote: > On 8/16/22 03:59, G. Branden Robinson wrote: > > I didn't realize you were waiting on me--sorry. It would be good if > > you could collect the pager output _including terminal escape > > sequences_, for instance using the script(1)

Re: Regarding groff and eqn

Oh oh. Tooo many mistakes. What was i thinking. Will try these. Thanks. On Tue, Aug 16, 2022, 13:17 G. Branden Robinson < g.branden.robin...@gmail.com> wrote: > At 2022-08-16T12:56:30+0300, Riza Dindir wrote: > > I am using groff 1.22.4 on FreBSD 13.1. Wanted to write inline > > equations (in a

Re: [BUG] italics run past where they should

On 8/16/22 14:40, G. Branden Robinson wrote: Hi Alex, At 2022-08-16T13:57:00+0200, Alejandro Colomar wrote: On 8/16/22 03:59, G. Branden Robinson wrote: I didn't realize you were waiting on me--sorry. It would be good if you could collect the pager output _including terminal escape

Re: Standardize roff

Hi San, Sam Varshavchik wrote on Sun, Aug 14, 2022 at 08:20:34PM -0400: > Ingo Schwarze writes: >> DJ Chase wrote on Sat, Aug 13, 2022 at 05:27:34PM +: >>> Have we ever considered a de jure *roff standard? >> No, i think that would be pure madness given the amount of working >> time

Re: [BUG] italics run past where they should

On 8/16/22 13:57, Alejandro Colomar wrote: Hi Branden, On 8/16/22 03:59, G. Branden Robinson wrote: I didn't realize you were waiting on me--sorry.  It would be good if you could collect the pager output _including terminal escape sequences_, for instance using the script(1) command (as

Re: [BUG] italics run past where they should

Hi Branden, On 8/16/22 03:59, G. Branden Robinson wrote: I didn't realize you were waiting on me--sorry. It would be good if you could collect the pager output _including terminal escape sequences_, for instance using the script(1) command (as Ralph pointed out). Attach it to your email. It

Re: One Page Dungeon Layout in groff?

On Tuesday, 16 August 2022 10:18:17 BST Ralph Corderoy wrote: > > Interestingly if you use the command "convert file.png file.pdf" a > > valid pdf is produced which works with gropdf. > > That was Laurens' original command but I found the convert(1) here > sticks an ASCII NUL after the title,

Re: Standardize roff (was: *roff `\~` support)

Hi Alejandro, Alejandro Colomar wrote on Mon, Aug 15, 2022 at 01:59:24PM +0200: > On 8/14/22 21:43, DJ Chase wrote: >> Do you think that a descriptive/trailing standard could be beneficial >> or would you still say that it could mostly hinder *roff >> implementations? When prepared with

Savannah bug->email gateway problems affecting groff

[CCing Bob Proulx] This message just is not showing up on the savannah-hackers-public list (after two attempts 6 hours apart), so maybe there is more than one email problem going on. groff list subscribers may wish to consult

Re: Regarding groff and eqn

At 2022-08-16T12:56:30+0300, Riza Dindir wrote: > I am using groff 1.22.4 on FreBSD 13.1. Wanted to write inline > equations (in a document that uses ms macros), and it does not give me > any inline equations. I must be missing something or doing something > wrong. > > Here is my simple document.

Regarding groff and eqn

Hello All, I am using groff 1.22.4 on FreBSD 13.1. Wanted to write inline equations (in a document that uses ms macros), and it does not give me any inline equations. I must be missing something or doing something wrong. Here is my simple document. .TH Inline math .NH Start .LP .EQ delim $$ .EN

Re: One Page Dungeon Layout in groff?

On 8/15/22, Ralph Corderoy wrote: > First, pdfinfo(1) was writing a NUL byte as part of the name of the PDF > produced by ImageMagick's convert(1) This has been reported as a bug (http://gitlab.freedesktop.org/poppler/poppler/-/issues/776) but doesn't seem universally regarded as such by the

Re: One Page Dungeon Layout in groff?

Hi Deri, > It starts a hash with "<<" but fails to close it with ">>". Each hash > entry is a key/value pair where the key is preceded by a "\". The > endstream should follow after a stream but that is missing. Thanks for digging deeper. > Interestingly if you use the command "convert file.png