[bug #52433] Commit [09040dbf] is wrong

URL: Summary: Commit [09040dbf] is wrong Project: GNU troff Submitted by: None Submitted on: Fri 17 Nov 2017 06:51:01 PM UTC Category: None Severity: 3 - Normal

[bug #43541] FILE* encapsulation via class; compression support for input files

Follow-up Comment #1, bug #43541 (project groff): Actually this missed a usage of plain FILE* in lib-driver/input.xx. But adding this is straightforward. Christians a merry christmas. ___ Reply to this item at:

[bug #52865] lib-driver, input: Df broken (since 2002)

URL: Summary: lib-driver, input: Df broken (since 2002) Project: GNU troff Submitted by: None Submitted on: Thu 11 Jan 2018 07:49:50 PM UTC Category: None Severity: 3 -

[bug #52865] lib-driver, input: Df broken (since 2002)

Follow-up Comment #3, bug #52865 (project groff): I thought looking at parse_D_command() unveils the obvious. But, to continue the discussion:, what prevented disabling of STUPID_DRAWING_POSITIONING after it has been introduced a few weeks before those bugs sprang into existence (in [ea5a42d0] any

[bug #54213] grodvi: broken ^ and ~

URL: Summary: grodvi: broken ^ and ~ Project: GNU troff Submitted by: None Submitted on: Sat 30 Jun 2018 03:33:14 PM UTC Category: Device - others Severity: 3 - Normal

[bug #54214] grodvi: slanted dollar sign

URL: Summary: grodvi: slanted dollar sign Project: GNU troff Submitted by: None Submitted on: Sat 30 Jun 2018 03:41:18 PM UTC Category: Device - others Severity: 3 - No

[bug #54909] Paragraph indention after heading; extra space between heading and list

URL: Summary: Paragraph indention after heading; extra space between heading and list Project: GNU troff Submitted by: None Submitted on: Mon 29 Oct 2018 02:48:37 AM UTC Category: Mac

[bug #55035] UTF-8 strings not properly preconv'd when defined using -d

URL: Summary: UTF-8 strings not properly preconv'd when defined using -d Project: GNU troff Submitted by: None Submitted on: Fri 16 Nov 2018 12:40:17 PM UTC Category: Preprocessor pre

[bug #55099] undiagnosed error leads to misbehavior

URL: Summary: undiagnosed error leads to misbehavior Project: GNU troff Submitted by: None Submitted on: Mon 26 Nov 2018 02:15:45 AM UTC Category: Macro - ms Severity:

[bug #55868] pdfmark hotspot vertical positioning error

URL: Summary: pdfmark hotspot vertical positioning error Project: GNU troff Submitted by: None Submitted on: Fri 08 Mar 2019 05:27:53 PM UTC Category: Macro - others S

[bug #56221] groffer does not support colon-specific values in MANPATH

URL: Summary: groffer does not support colon-specific values in MANPATH Project: GNU troff Submitted by: None Submitted on: Fri 26 Apr 2019 05:59:17 AM UTC Category: None

[bug #56694] troff mixes malloc / delete[]

URL: Summary: troff mixes malloc / delete[] Project: GNU troff Submitted by: None Submitted on: Mon 29 Jul 2019 09:17:29 PM UTC Category: Core Severity: 3 - Normal

[bug #57667] refer(1) rehab

URL: Summary: refer(1) rehab Project: GNU troff Submitted by: None Submitted on: Sun 26 Jan 2020 02:05:54 AM UTC Category: Macro - others Severity: 3 - Normal

[bug #57747] Malfunctioning romanian special characters

URL: Summary: Malfunctioning romanian special characters Project: GNU troff Submitted by: None Submitted on: Wed 05 Feb 2020 04:04:27 PM UTC Category: Font - others Se

[bug #57802] groff_mmse.7 wrong path

URL: Summary: groff_mmse.7 wrong path Project: GNU troff Submitted by: None Submitted on: Wed 12 Feb 2020 11:01:09 PM UTC Category: None Severity: 3 - Normal

[bug #57873] grog mangles output

URL: Summary: grog mangles output Project: GNU troff Submitted by: None Submitted on: Fri 21 Feb 2020 03:08:54 PM UTC Category: Core Severity: 3 - Normal

[bug #58077] Outof date information in grops man page

URL: Summary: Outof date information in grops man page Project: GNU troff Submitted by: None Submitted on: Sun 29 Mar 2020 03:51:49 PM UTC Category: Device grops Sever

[bug #58206] [PATCH] fix PDFPIC issue with determining size of pdfs containing images

URL: Summary: [PATCH] fix PDFPIC issue with determining size of pdfs containing images Project: GNU troff Submitted by: None Submitted on: Sun 19 Apr 2020 06:53:50 PM UTC Category: De

[bug #58206] [PATCH] fix PDFPIC issue with determining size of pdfs containing images

Additional Item Attachment, bug #58206 (project groff): File name: angular-1280-800.pdf Size:279 KB ___ Reply to this item at:

[bug #58206] [PATCH] fix PDFPIC issue with determining size of pdfs containing images

Follow-up Comment #3, bug #58206 (project groff): I just attached the pdf i was trying to embed. This was mostly just to see if pdfpic was working. ___ Reply to this item at: __

[bug #58206] [PATCH] fix PDFPIC issue with determining size of pdfs containing images

Follow-up Comment #4, bug #58206 (project groff): Ok so a work around I used was to use tr's -d flag to remove the NULL sections from the output from pdfinfo. As far as I know this should be available to all systems. Another option is to use cat -v but I don't think that is POSIX complaint. Here

[bug #58206] [PATCH] fix PDFPIC issue with determining size of pdfs containing images

Follow-up Comment #6, bug #58206 (project groff): I found a similar issue in the their issue tracker sadly it is still unresolved. https://gitlab.freedesktop.org/poppler/poppler/-/issues/776 The argument for supporting PDFPIC is to allow files contain pdfmark's pdfhref feature can also contain p

[bug #58949] adapt -mdoc to use the facilities of pdfmark

URL: Summary: adapt -mdoc to use the facilities of pdfmark Project: GNU troff Submitted by: None Submitted on: Thu 13 Aug 2020 10:35:34 PM UTC Category: Macro - mdoc S

[bug #58947] adapt -mm to use the facilities of pdfmark

URL: Summary: adapt -mm to use the facilities of pdfmark Project: GNU troff Submitted by: None Submitted on: Thu 13 Aug 2020 10:31:36 PM UTC Category: Macro - mm Sever

[bug #58948] adapt -me to use the facilities of pdfmark

URL: Summary: adapt -me to use the facilities of pdfmark Project: GNU troff Submitted by: None Submitted on: Thu 13 Aug 2020 10:33:49 PM UTC Category: Macro - me Sever

[bug #58946] adapt -ms to use the facilities of pdfmark

URL: Summary: adapt -ms to use the facilities of pdfmark Project: GNU troff Submitted by: None Submitted on: Thu 13 Aug 2020 10:28:08 PM UTC Category: Macro - ms Sever

[bug #58950] adapt -man to use the facilities of pdfmark

URL: Summary: adapt -man to use the facilities of pdfmark Project: GNU troff Submitted by: None Submitted on: Thu 13 Aug 2020 10:37:15 PM UTC Category: Macro - man Sev

[bug #58969] Request gropdf's foundry concept be integrated into groff

URL: Summary: Request gropdf's foundry concept be integrated into groff Project: GNU troff Submitted by: None Submitted on: Mon 17 Aug 2020 05:47:16 AM UTC Category: Font - others

[bug #59186] Compilation Break due to commit: 2c9484fc9957cfe531fdbbe9d6b1fc3561baede5

URL: Summary: Compilation Break due to commit: 2c9484fc9957cfe531fdbbe9d6b1fc3561baede5 Project: GNU troff Submitted by: None Submitted on: Sat 26 Sep 2020 04:21:53 PM UTC Cat

[bug #42233] [PATCH] wcwidth(3) used on UCS4/UTF-32 codepoints

Follow-up Comment #4, bug #42233 (project groff): |>> Steffen has withdrawn most/all of his other patches and even after |>> reading |> |> I do not know what this has to do with this bug. | |As I recall (dimly), you said something at some point that I perhaps |misinterpreted--that you were

[bug #59835] add support for strsignal

URL: Summary: add support for strsignal Project: GNU troff Submitted by: None Submitted on: Wed 06 Jan 2021 04:19:57 PM UTC Category: None Severity: 3 - Normal

[bug #59933] Curly brackets displayed correctly in ps, but not in pdf

URL: Summary: Curly brackets displayed correctly in ps, but not in pdf Project: GNU troff Submitted by: None Submitted on: Sat 23 Jan 2021 07:37:36 PM UTC Category: Font devpdf

[bug #59958] race in Makefile at generation of e.tmac and doc.tmac with bigger than -j1 eg. -j4

URL: Summary: race in Makefile at generation of e.tmac and doc.tmac with bigger than -j1 eg. -j4 Project: GNU troff Submitted by: None Submitted on: Thu 28 Jan 2021 03:48:55 AM UTC Ca

[bug #59958] race in Makefile at generation of e.tmac and doc.tmac with bigger than -j1 eg. -j4

Follow-up Comment #1, bug #59958 (project groff): Ignore what was said and just look at the patch, you'll see it makes sense :) The race is thus unnecessary(even if it doesn't really affect anyone) and thus patch could be applied to get rid of it. _

[bug #59958] race in Makefile at generation of e.tmac and doc.tmac with bigger than -j1 eg. -j4

Follow-up Comment #2, bug #59958 (project groff): Perhaps I should've mentioned the version: sys-apps/groff-1.22.4::gentoo because I look at git groff and don't see where to apply patch, maybe things already changed a lot in git version so this doesn't apply anymore. Sorry for the noise. ___

[bug #59958] race in Makefile at generation of e.tmac and doc.tmac with bigger than -j1 eg. -j4

Follow-up Comment #3, bug #59958 (project groff): oh the race code is in tmac/tmac.am in git groff looks like this: $(TMACSTRIPFILES): $(TMACUNSTRIPFILES) for f in $(TMACSTRIPFILES); do \

[bug #60052] tbl: output HTML

URL: Summary: tbl: output HTML Project: GNU troff Submitted by: None Submitted on: Sun 14 Feb 2021 05:57:32 AM UTC Category: Preprocessor tbl Severity: 3 - Normal

[bug #60060] support other printing directions (right to left, top to bottom)

URL: Summary: support other printing directions (right to left, top to bottom) Project: GNU troff Submitted by: None Submitted on: Mon 15 Feb 2021 12:10:58 AM UTC Category: Core

[bug #60260] Incorrect warnings of dangling .el with bracket-less nesting

URL: Summary: Incorrect warnings of dangling .el with bracket-less nesting Project: GNU troff Submitted by: None Submitted on: Fri 19 Mar 2021 04:00:48 PM UTC Category: None

[bug #60421] grog fails to infer -s and -t options

URL: Summary: grog fails to infer -s and -t options Project: GNU troff Submitted by: None Submitted on: Tue 20 Apr 2021 05:24:05 AM UTC Category: Core Severity: 3 - No

[bug #60604] m4/groff.m4: GROFF_URW_FONTS_CHECK: stale URL

URL: Summary: m4/groff.m4: GROFF_URW_FONTS_CHECK: stale URL Project: GNU troff Submitted by: None Submitted on: Fri 14 May 2021 07:02:22 AM UTC Category: Font devpdf S

[bug #45034] [PATCH] mdoc(7): add support for the mdocmx(7) reference extension

Follow-up Comment #16, bug #45034 (project groff): In the meantime less got support for OSC 8 "hyperlinks in terminal", and i changed the three lines in mdocmx to create \X'tty: osc8 ...' for the TTY output device instead. Please find attached a patch for grotty that implements \X'tty: osc8' sequ

[bug #60666] [grotty] add OSC 8 support for hyperlinks

Follow-up Comment #1, bug #60666 (project groff): Great! Let me attach my final patches to grotty and less (your linked one does not yet securely quote content). It would be great to see OSC 8 addition to grotty, not unlikely converters like docbook etc. would start using it. (I am not subscribed.

[bug #60666] [grotty] add OSC 8 support for hyperlinks

Follow-up Comment #5, bug #60666 (project groff): Hello Branden. Well, sure. I saw your SGR thing already by then. I do not like introducing more and more environment variables for each and every thing myself. However, .. end-users can only control via that. More or less. There should be a well-k

[bug #60802] Make .substring handle an empty result

URL: Summary: Make .substring handle an empty result Project: GNU troff Submitted by: None Submitted on: Sun 20 Jun 2021 03:01:26 AM UTC Category: Core Severity: 3 - N

[bug #61104] .At 32v should say "[Version 7] AT&T UNIX/32V", not "Version 32V AT&T UNIX"

URL: Summary: .At 32v should say "[Version 7] AT&T UNIX/32V", not "Version 32V AT&T UNIX" Project: GNU troff Submitted by: None Submitted on: Wed 01 Sep 2021 04:53:52 PM UTC Category:

[bug #61193] failure to instal refer pre-processor

URL: Summary: failure to instal refer pre-processor Project: GNU troff Submitted by: None Submitted on: Tue 21 Sep 2021 10:03:30 AM UTC Category: None Severity: 3 - No

[bug #61276] .Ql macro in troff-mode does not put text in single quotes

URL: Summary: .Ql macro in troff-mode does not put text in single quotes Project: GNU troff Submitted by: None Submitted on: Mon 04 Oct 2021 11:27:28 AM UTC Category: Macro - mdoc

[bug #61407] Remove spurious error messages generated by pdf.tmac

Follow-up Comment #7, bug #61407 (project groff): As discussed in the mailinglist (https://lists.gnu.org/archive/html/groff/2021-12/msg0.html) hereby the patch I used to get pdfpic.tmac to work. (file #52513) ___ Additional Item Attac

[bug #61886] grotty: OSC-8 support does not offer IDs aka id=, only link

URL: Summary: grotty: OSC-8 support does not offer IDs aka id=, only link Project: GNU troff Submitted by: None Submitted on: Fri 21 Jan 2022 12:26:14 AM UTC Category: Device - others

[bug #61886] grotty: OSC-8 support does not offer IDs aka id=, only link

Follow-up Comment #1, bug #61886 (project groff): P.S.: i am not subscribed to bugs. Just ask me on the normal list or in private, i would be willing to write the patch, too! ___ Reply to this item at:

[bug #61886] [grotty] want anchor support to complement OSC 8 hyperlinks

Follow-up Comment #3, bug #61886 (project groff): Hm. There is the OSC-8 thing which offers id= fields. Anything up to the separating semicolon ; is the ID, right? ___ Reply to this item at: _

[bug #61914] grohtml does not track man(7) relative insets accurately

URL: Summary: grohtml does not track man(7) relative insets accurately Project: GNU troff Submitted by: None Submitted on: Tue 25 Jan 2022 12:05:10 PM UTC Category: Preprocessor html

[bug #61915] grohtml: .EX/.EE is not monospaced

URL: Summary: grohtml: .EX/.EE is not monospaced Project: GNU troff Submitted by: None Submitted on: Tue 25 Jan 2022 12:10:45 PM UTC Category: Preprocessor html Severi

[bug #61917] grohtml: \- mapped to something different than ASCII 45 (Latin hyphen-minus)

URL: Summary: grohtml: \- mapped to something different than ASCII 45 (Latin hyphen-minus) Project: GNU troff Submitted by: None Submitted on: Tue 25 Jan 2022 12:28:15 PM UTC Category

[bug #61886] [grotty] want anchor support to complement OSC 8 hyperlinks

Follow-up Comment #4, bug #61886 (project groff): I hope he takes it, maybe after tweaks of course. . ^O^I text - search id= "text" . ^O^N - search next OSC 8 link aka _URI_ . ^O^P - search previous OSC 8 link aka _URI_ . ^O^O - open current OSC 8 link aka _URI_ with LE

[bug #62825] Incorrect section number using \*($n in a header

: None ___ Follow-up Comments: --- Date: Wed 27 Jul 2022 08:18:06 PM UTC By: Anonymous When re-defining the $h macro for a custom header when using -me, putting the section number in the header with \*($n results in the number being

[bug #62825] Incorrect section number using \*($n in a header

Follow-up Comment #3, bug #62825 (project groff): This seems to be about how and when groff prints the headers on each page. Notice that the only thing that's correct on each page of the output is the page number. After page 1 the chapter number in the header is then correct as well. However, at t

[bug #62825] Incorrect section number using \*($n in a header

Follow-up Comment #5, bug #62825 (project groff): [comment #4 comment #4:] > Consider a page where the top half wraps up section 1.4, then section 2.1 begins, and has a paragraph or two on the lower half of the page. Here you want your page header to indicate section 1.4, since that's the section

[bug #62825] page header info should correspond to last section on the page

Follow-up Comment #10, bug #62825 (project groff): [comment #7 comment #7:] > It sounds to me like this was just a straight-up bug. My guess is that people simply haven't been putting section information in their headers because of this behavior, they worked around it, or they got lucky. I think

[bug #62909] Preprocessror problem - Groff with dformat and chem

: None ___ Follow-up Comments: --- Date: Thu 18 Aug 2022 04:07:00 AM UTC By: Anonymous Hello, I am having trouble with chem and dformat preprocessors. I have downloaded dfromat from (https://github.com/arnoldrobbins/dforma

[bug #62921] [Request] Add another monospaced font to the default fonts

: None ___ Follow-up Comments: --- Date: Fri 19 Aug 2022 04:02:39 PM UTC By: Anonymous By default groff comes with 6 proportional fonts (Avant Garde, Bookman, Helvetica, New Century Schoolbook, Palatino, Times New

[bug #62923] Broken aliases in PDF font description file

: None ___ Follow-up Comments: --- Date: Fri 19 Aug 2022 10:15:22 PM UTC By: Anonymous GROFF VERSION: 1.23.0.rc1.2845-342a1-dirty OS: GNU/Linux COMPILER: clang COMMAND LINE: groff -e file.troff -Tpdf > file.pdf DESCRIPTION OF INCORRECT BEHAVIOUR

[bug #62923] Broken aliases in PDF font description file

Follow-up Comment #2, bug #62923 (project groff): Thank you for fixing it! I applied the fix you provided and it works but I noticed that one thing is still broken: if you add an alias with name radicalex to sqrtex in XITSMR, the radicalex is rendered on the same position as sqrt (in groff_out the

[bug #62921] want another monospaced font in the default set

Follow-up Comment #2, bug #62921 (project groff): I concur that this (an nice monospaced font) would be desirable. begin-off-topic: PTMono is a _very_ nice free monspaced font. extremely readable on screen. use it as my standard font in the terminal. PTSerif and PTsans are also very decent (and I

[bug #62921] want another monospaced font in the default set

Follow-up Comment #4, bug #62921 (project groff): [comment #1 comment #1:] > The main practical problem here is that while we could certainly generate _groff_ font descriptions file for some or all of those, and ship them, users _still_ won't get those fonts in the output they generate unless the

[bug #63042] Enhancement: mdocmx(7) extension to mdoc(7)

Follow-up Comment #3, bug #63042 (project groff): ..but feel free to simply take it and integrate as a regular groff thing! It was just that the 2014/5 patch i think never was integrated in a build system, and this thing now just integrates into the groff build system. Ciao. __

[bug #63289] .Bd -unfilled lines run together when .Sm and .No are both also in effect

: None ___ Follow-up Comments: --- Date: Sat 29 Oct 2022 06:31:13 PM UTC By: Anonymous I noticed incorrect formatting of the URL examples in OpenBSD autoinstall(8) man page when rendered with GNU man /

[bug #63727] contrib/gdiffmk/tests/gdiffmk_tests.sh test fails with diffutils-3.9 (was ok with 3.8)

: None ___ Follow-up Comments: --- Date: Sun 29 Jan 2023 07:44:37 PM UTC By: Anonymous I tried to update diffutils to 3.9 in nixpkgs ( https://github.com/NixOS/nixpkgs/pull/213421) and discovered a regression in

[bug #63831] src/libs/libxutil/XFontName.c(utoa) conflicts with stdlib.h utoa in non-GNU libc

: None ___ Follow-up Comments: --- Date: Thu 23 Feb 2023 04:56:22 PM UTC By: Anonymous non-GNU libc newlib (also IBM, QNX, and others) define extern function utoa (also itao, ltoa, ftoa, ultoa, possibly

[bug #63978] Found a type for groff_man(7).

Follow-up Comments: --- Date: Thu 30 Mar 2023 09:16:53 AM UTC By: Anonymous In DESCRIPTION section. In first table. Meaning of Macro .SS says it is Subection heading; it should say Subsection h

[bug #55299] [PATCH] "groff -v -e -s -t" produces garbled output on MS-Windows

Follow-up Comment #4, bug #55299 (project groff): I maintain help2man and man-pages-{linux,posix} and some other stuff, Achim Gratz maintains groff, man-db, autotools, binutils, libtool, pkgconf, compressors, archivers, most perl..., and lots of good stuff! No Cygwin problems with latest groff 1.2

[bug #55335] [PATCH] preconv produces CR CR LF end-of-line on MS-Windows

Follow-up Comment #5, bug #55335 (project groff): Cygwin opted for POSIX/Linux/etc. compatibility a few years ago in 2017, and dropped all text mode open patches to utilities including coreutils, gawk, grep, sed, etc. causing some consternation, and much rejoicing amongst those who use it and newl

[bug #55695] [PATCH] Troff outputs garbled file names on MS-Windows

Follow-up Comment #3, bug #55695 (project groff): Most Cygwin packages and GNUtilities no longer support native Windows paths, unless they happen to pass them verbatim down to open, where the file handler may recognize the format and bypass POSIX to Windows path mapping. This is used to provide

[bug #55299] [PATCH] "groff -v -e -s -t" produces garbled output on MS-Windows

Follow-up Comment #5, bug #55299 (project groff): Cygwin works as expected: $ groff -v -e -s -t GNU groff version 1.22.4 Copyright (C) 2018 Free Software Foundation, Inc. GNU groff comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of groff and its subprograms under the terms of the G

[bug #64029] tbl: page break handling probably introduced another problem

: None ___ Follow-up Comments: --- Date: Tue 11 Apr 2023 09:03:01 PM UTC By: Anonymous groff-1.22.4 had a problem with tbl inserting empty lines at page breaks even for unlimited page sizes. groff-1.23.0_rc3 fixe

[bug #64032] typos in ms documentation

low-up Comments: --- Date: Wed 12 Apr 2023 02:35:16 AM UTC By: Anonymous hi! running the following on groff's base directory: $ grep -r breakb . results in the same typo in two documentation files: --- ./doc/ms.ms:Insert an unbreakble space of

[bug #64043] regression introduced with bug #62688: [ms] inter-display distance accumulates with other vertical space--it should not

k: Any Planned Release: None ___ Follow-up Comments: --- Date: Thu 13 Apr 2023 07:11:15 PM UTC By: Anonymous As has been shown in https://lists.gnu.org/archive/html/groff/2023-04/msg0009

[bug #64043] mixing formatting requests with macro calls produces different unspecified behavior with groff than with AT&T troff

Follow-up Comment #2, bug #64043 (project groff): In your screenshots I see 13 pixels vs. 26 pixels of vertical space before "Rule: Braces can always be..." - this seems significant to me (and I thought that difference was obvious enough). I fail to see the relevance of "the equation at lines 4

[bug #64043] mixing formatting requests with macro calls produces different unspecified behavior with groff than with AT&T troff

Follow-up Comment #3, bug #64043 (project groff): Attached screenshots ms-1.png and ms-2.png show vertical space of 25 pixels vs 12 pixels - also seems significant and quite obvious to see. (file #54622, file #54623) ___ Additional Item At

[bug #64043] mixing formatting requests with macro calls produces different unspecified behavior with groff than with AT&T troff

Follow-up Comment #4, bug #64043 (project groff): Also failing to see where that's mixing formatting requests with macro calls... .nr PS 1v .nr DD 0v .LP 1 .NH 2 .EQ 3 .EN .NH 4 .LP 5 .DS 6 .DE .NH 7 .LP 8 ___ Reply to this item at:

[bug #64043] mixing formatting requests with macro calls produces different unspecified behavior with groff than with AT&T troff

Follow-up Comment #8, bug #64043 (project groff): So, are we talking about vertical space inside section 8, or vertical space right before section 11? Your screenshots showed the spacing difference for section 8, my screenshots showed the spacing difference right before section 11. In both cas

[bug #64059] 'make install' fails when you build on a different directory

ed Release: None ___ Follow-up Comments: --- Date: Mon 17 Apr 2023 04:39:45 AM UTC By: Anonymous Hi. I tried building groff from source and failed at the make install step. what i did was: $ ./bootstrap #works fine $ mkdir b

[bug #64370] Matrix Column Vertical Space is Sub Optimal

: None ___ Follow-up Comments: --- Date: Fri 30 Jun 2023 06:54:28 AM UTC By: Anonymous See the attached. When I have two entries in the same row, one 0 and the other a term like { partial x } over { partial r } which have

[bug #64421] The word "black" appears in output

ed Release: None ___ Follow-up Comments: --- Date: Wed 12 Jul 2023 07:24:00 PM UTC By: Anonymous When using the Mom macro package, I'm seeing the literal color name "black" rendered above a horizontal rule. Reproduced with the quit

[bug #64421] The word "black" appears in output

Follow-up Comment #1, bug #64421 (project groff): This affects my mail printing tool "mailprint" (https://gnoack.github.io/mailprint/) - the word "black" appears at the top above the horizontal rule. My groff-fu is unfortunately too weak to understand how to fix this :) but I do suspect that this

[bug #64421] [mom] the word "black" appears in output

Follow-up Comment #5, bug #64421 (project groff): Hi! The om.tmac files which I obtained from the Arch package, from git, from http://ftp.gnu.org/gnu/groff/groff-1.23.0.tar.gz and from https://www.schaffter.ca/mom/mom-2.5_d.tar.gz are all the same: gnoack:~$ sha256sum Downloads/groff-1.23.0/cont

[bug #64421] [mom] the word "black" appears in output

Follow-up Comment #6, bug #64421 (project groff): Regarding Arch differences: You can see the Arch package definition at https://gitlab.archlinux.org/archlinux/packaging/packages/groff/-/tree/main/. The two differences I can see are (1) a patch for date formatting (probably irrelevant here) and (

[bug #64421] [mom] the word "black" appears in output

Follow-up Comment #7, bug #64421 (project groff): I also tried it out with the three groff versions which I still found in my package cache. Package version 1.22.4-10 does *not* have the bug: pacman -U /var/cache/pacman/pkg/groff-1.22.4-10-x86_64.pkg.t ar.zst # does NOT have the bug pacman -U /

[bug #64421] [mom] the word "black" spuriously appears in output

Follow-up Comment #12, bug #64421 (project groff): I recreated the PDF file with Arch Linux's groff-1.23.0-3-x86_64.pkg.tar.zst and groff-1.22.4-10-x86_64.pkg.tar.zst packages, using the -P-d flag, as follows. I reinstalled the old package version from a separate terminal in between running these.

[bug #64421] [mom] the word "black" spuriously appears in output

Follow-up Comment #14, bug #64421 (project groff): I attached the .grout files using groff packages 1.22.4 and 1.23.0. The script I used to produce them is: #!/bin/sh cat File name: groff-1.23.0.grout Size:2 KB

[bug #64421] [mom] the word "black" spuriously appears in output

Follow-up Comment #15, bug #64421 (project groff): [comment #13 comment #13:] > To clarify, you're saying that the problem reproduces regardless of output driver, and that the word "black" spuriously appears in PostScript output as well as PDF. > > I think it unlikely that output driver behavior

[bug #64459] Subscripting does not work.

Follow-up Comment #1, bug #64459 (project groff): Section 4.6 and its subsections only apply to the "ms" macro package. Are you using that in your document? --Günther ___ Reply to this item at: _

[bug #64421] [mom] the word "black" spuriously appears in output

Follow-up Comment #16, bug #64421 (project groff): FYI, this is also relatively easy to reproduce from the Arch Linux installation medium. It is not graphical but it can be done with pdftotext. The "gnome-boxes" program make it straightforward to boot up a qemu instance with it. Once you are in t

[bug #64478] want mechanism to clear hyphenation patterns defined with .hw

: None ___ Follow-up Comments: --- Date: Thu 27 Jul 2023 04:29:04 AM UTC By: Anonymous [Quoting Branden in http://lists.gnu.org/r/groff/2023-03/msg00108.html] One of the themes of my suggested revisions to GNU troff has been to p

[bug #64502] [mdoc] inhibit word breaking in all requests where it makes sense

: None ___ Follow-up Comments: --- Date: Tue 01 Aug 2023 06:07:08 PM UTC By: Anonymous Opened at Branden's invitation (albeit an invitation to Alex that he seemingly never took up): http://lists.gnu.org/r/gr

[bug #64454] [tbl] 'u' column modifier ("stagger") does not affect text block

Follow-up Comment #2, bug #64454 (project groff): Applied to Debian 1.23.0-2, ./debian/build/tbl tblest | groff over the block below gets me what I wanted to do in Debian#1038391 (half-line spacing between the rows), and appears to work just as well when B is long. .TS l l l lu lu lu lu lu lu

[bug #64454] [tbl] 'u' column modifier ("stagger") does not affect text block

Follow-up Comment #6, bug #64454 (project groff): Okay, I re-ran this against my original table – base64, sorry: LlRTCmwyIGwyYiBsYgpsICBseCAgbHgKbHUgbHV4IGx1eApsdSBsdXggbHV4CmwgIGx4ICBseCAuCgl0aGVyZQloZXJlCj0KZGVhbGluZyB3aXRoIHBpcGVzCVR7CnNpemUgaXMgc29tZWhvdyB0aGUgc2l6ZSBvZiB0aGUgZGF0YSBpbiB0aGUgZ

[bug #64454] [tbl] 'u' column modifier ("stagger") does not affect text block

Follow-up Comment #8, bug #64454 (project groff): I think this is because it may be folding differently for you – if I shorten it to end at "defined" it's also aligned properly for me. If I make it very long, it's /also/ at the right vertical height I naively want to say that this happens due to

[bug #64454] [tbl] 'u' column modifier ("stagger") does not affect text block

Follow-up Comment #10, bug #64454 (project groff): Renders sanely for me (and explains why the spacing yesterday looked so weirdly large – it was). ___ Reply to this item at: _

  1   2   3   >