[bug #66344] [grops] support `-y` foundry-selection option as gropdf does

URL: Summary: [grops] support `-y` foundry-selection option as gropdf does Group: GNU roff Submitter: gbranden Submitted: Thu 17 Oct 2024 12:02:37 PM UTC Category: Driver grop

[bug #62951] [grops] internally recognize PostScript Level 2 base 35 fonts

Follow-up Comment #5, bug #62951 (group groff): [comment #3 comment #3:] > The `-e` part of this is split off as... ... bug #66345. This time for sure! ___ Reply to this item at: __

[bug #62951] [grops] internally recognize PostScript Level 2 base 35 fonts

Follow-up Comment #3, bug #62951 (group groff): The `-e` part of this is split off as bug #66342. ___ Reply to this item at: ___ Message sent via Savann

[bug #62951] [grops] internally recognize PostScript Level 2 base 35 fonts

Follow-up Comment #4, bug #62951 (group groff): [comment #3 comment #3:] > The `-e` part of this is split off as bug #66342. Whoops, no it's not. Though it rhymes. ___ Reply to this item at: __

[bug #66345] [grops] support `-e` font-embedding option as gropdf does

URL: Summary: [grops] support `-e` font-embedding option as gropdf does Group: GNU roff Submitter: gbranden Submitted: Thu 17 Oct 2024 12:29:26 PM UTC Category: Driver grops

[bug #66323] [gropdf] rendering differences between PostScript and PDF output?

Follow-up Comment #32, bug #66323 (group groff): At 2024-10-14T16:54:11-0400, Deri James wrote: > Follow-up Comment #18, bug #66323 (group groff): > > > pdfmom -Kutf8 -P-e good-clean.mom > good-clean.pdf > > > along with their respective ps and pdf files. The family > > > is T, not U-T, becaus

[bug #66344] [grops] support `-y` foundry-selection option as gropdf does

Follow-up Comment #1, bug #66344 (group groff): It would make more sense to add this to groff. So that .ft TR resulted in 'x font 5 U-TR' if -yU was passed to groff. This would mean no changes to grops, adding the U- to internalname (by afmtodit), and gropdf dropping the -y flag. This would mean t

[bug #66076] [PATCH] [xditview] unsafe string handling in xditview.c

Update of bug #66076 (group groff): Status:None => In Progress Assigned to:None => gbranden ___ Reply to this item at:

[bug #66350] src/roff/troff/input.cpp: "(or string)" is missing in a warning

Update of bug #66350 (group groff): Severity: 3 - Normal => 2 - Minor Summary: src/roff/troff/inpuc.cpp: "(or string)" is missing in a warning => src/roff/troff/input.cpp: "(or string)" is missing in a warning ___

[bug #66350] src/roff/troff/inpuc.cpp: "(or string)" is missing in a warning

URL: Summary: src/roff/troff/inpuc.cpp: "(or string)" is missing in a warning Group: GNU roff Submitter: bjarniig Submitted: Thu 17 Oct 2024 10:05:01 PM UTC Category: Core

[bug #66078] [PATCH] [refer] Typo in the array elements comparison in src/preproc/refer/ref.cpp

Update of bug #66078 (group groff): Status:None => In Progress Assigned to:None => gbranden ___ Reply to this item at:

[bug #62540] refer/ref.cpp: comparison between two arrays is deprecated in C++20

Update of bug #62540 (group groff): Status: In Progress => None ___ Reply to this item at: ___ Message

[bug #62540] refer/ref.cpp: comparison between two arrays is deprecated in C++20

Update of bug #62540 (group groff): Status:None => In Progress Assigned to:None => gbranden ___ Reply to this item at:

[bug #64469] [troff] `-o` with valid but inapplicable argument provokes incomprehensible output driver diagnostic

Update of bug #64469 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0 __

[bug #66335] [PATCH] doc/pic.ms: include linethick variable in pic.ms reference section #21

Update of bug #66335 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0 __

[bug #66078] [PATCH] [refer] typo in the array element comparison in "ref.cpp"

Update of bug #66078 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0 Summary: [PATC

[bug #66080] [PATCH] [pic] initialize memory in struct members

Update of bug #66080 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0 __

[bug #66076] [PATCH] [xditview] unsafe string handling in xditview.c

Update of bug #66076 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0 __

[bug #62540] refer/ref.cpp: comparison between two arrays is deprecated in C++20

Update of bug #62540 (group groff): Status:None => Duplicate Open/Closed:Open => Closed ___ Follow-up Comment #5: Closing as duplicate of

[bug #64469] [grops] -o with out-of-range number produces incomprehensible error

Follow-up Comment #2, bug #64469 (group groff): [comment #1 comment #1:] > Can reproduce with _groff_ 1.23.0 final. > > This might be a good time to adopt _neatroff_'s `.%` register, which stores the *page sequence number*, introduce this concept to our implementation and documentation, and fast

[bug #66348] [troff] support neatroff's `.%` register for page sequence number

URL: Summary: [troff] support neatroff's `.%` register for page sequence number Group: GNU roff Submitter: gbranden Submitted: Thu 17 Oct 2024 04:15:46 PM UTC Category: Core

[bug #66344] support `-y` foundry-selection option as gropdf does

Update of bug #66344 (group groff): Category:Driver grops => Core Status:None => Duplicate Assigned to:None => gbranden Open/Closed:

[bug #64469] [troff] `-o` with valid but inapplicable argument provokes incomprehensible output driver diagnostic

Update of bug #64469 (group groff): Category:Driver grops => Core Status: Confirmed => In Progress Assigned to:None => gbranden Summary: [grop

[bug #58969] [troff] integrate gropdf's foundry concept

Update of bug #58969 (group groff): Category: Font - others/general => Core Summary: Request gropdf's foundry concept be integrated into groff => [troff] integrate gropdf's foundry concept __

[bug #62951] [grops] internally recognize PostScript Level 2 base 35 fonts

Follow-up Comment #7, bug #62951 (group groff): [comment #6 comment #6:] > Ghostscript now does embed the base35 fonts, you no longer have to request it. I don't think _grops_ relies upon Ghostscript to generate PostScript? I think _grops_ does its own lifting here. We *do* have Autoconf-fu to

[bug #66342] [gropdf] embed all fonts by default, per current PDF standard

Update of bug #66342 (group groff): Severity: 3 - Normal => 1 - Wish ___ Reply to this item at: ___ Message

[bug #66187] [troff] permit control over flushing of output file state

Update of bug #66187 (group groff): Assigned to:gbranden => None ___ Reply to this item at: ___ Message

[bug #66143] build doesn't find Homebrew uchardet on macOS 14.6.1

Update of bug #66143 (group groff): Assigned to:gbranden => None ___ Reply to this item at: ___ Message

[bug #66335] [PATCH] doc/pic.ms: include linethick variable in pic.ms reference section #21

Update of bug #66335 (group groff): Status:None => In Progress Assigned to:None => gbranden ___ Reply to this item at:

[bug #66080] [PATCH] [pic] initialize memory in struct members

Update of bug #66080 (group groff): Status:None => In Progress Assigned to:None => gbranden Summary: [PATCH] [pic] use of unitialized stack variables => [PATCH] [pic] initialize memor

[bug #62951] [grops] internally recognize PostScript Level 2 base 35 fonts

Follow-up Comment #6, bug #62951 (group groff): Ghostscript now does embed the base35 fonts, you no longer have to request it. ___ Reply to this item at: _