[bug #64526] Retool example of using newlines as escape delimiters

Update of bug #64526 (group groff): Status:None => Invalid Assigned to:None => barx Open/Closed:Open => Closed __

[bug #62814] [PATCH] consolidate or distinguish tty.tmac and tty-char.tmac

Follow-up Comment #8, bug #62814 (group groff): [http://git.savannah.gnu.org/cgit/groff.git/commit/?id=32393c7e3 Commit 32393c7e3] invalidated this patch. Will post an update in the near future. ___ Reply to this item at:

[bug #66113] [troff] `\B` escape sequences misdescribes mismatched ending delimiter

Update of bug #66113 (group groff): Planned Release:None => 1.24.0 ___ Reply to this item at: ___ Message

[bug #66001] [troff] implement saturating arithmetic

Update of bug #66001 (group groff): Planned Release:None => 1.24.0 ___ Reply to this item at: ___ Message

[bug #65724] drop support for CCSID (code page) 1047 (EBCDIC)

Update of bug #65724 (group groff): Planned Release:None => 1.24.0 ___ Reply to this item at: ___ Message

[bug #64240] [troff] make numeric expression parser more sensitive to nonsense

Update of bug #64240 (group groff): Planned Release:None => 1.24.0 ___ Reply to this item at: ___ Message

[bug #63587] [troff] set .R register to maximum representable integer

Update of bug #63587 (group groff): Planned Release:None => 1.24.0 ___ Reply to this item at: ___ Message

[bug #63202] [troff] missing delimiter diagnostics could say what they were expecting

Update of bug #63202 (group groff): Planned Release:None => 1.24.0 ___ Reply to this item at: ___ Message

[bug #63142] [troff] unsupport newlines as escape argument delimiters

Update of bug #63142 (group groff): Planned Release:None => 1.24.0 ___ Reply to this item at: ___ Message

[bug #66113] [troff] `\B` escape sequence misdescribes mismatched ending delimiter

Update of bug #66113 (group groff): Summary: [troff] `\B` escape sequences misdescribes mismatched ending delimiter => [troff] `\B` escape sequence misdescribes mismatched ending delimiter ___ Reply to this item at:

[bug #66113] [troff] `\B` escape sequence misdescribes mismatched closing delimiter

Update of bug #66113 (group groff): Summary: [troff] `\B` escape sequence misdescribes mismatched ending delimiter => [troff] `\B` escape sequence misdescribes mismatched closing delimiter ___ Reply to this item at:

[bug #66114] Support embedding bit mapped graphics into a pdf.

URL: Summary: Support embedding bit mapped graphics into a pdf. Group: GNU roff Submitter: deri Submitted: Tue 20 Aug 2024 01:48:30 PM UTC Category: Driver gropdf

[bug #66114] Support embedding bit mapped graphics into a pdf.

Follow-up Comment #1, bug #66114 (group groff): This has been implemented in a recent commit and I have attached a pdf which explains the changes further. It would be very helpful if there was some testing of this code since there are a lot of moving parts! (file #56369, file #56370) ___

[bug #66114] Support embedding bit mapped graphics into a pdf.

Follow-up Comment #2, bug #66114 (group groff): [comment #1 comment #1:] > This has been implemented in a recent commit and I have attached a pdf which explains the changes further. It would be very helpful if there was some testing of this code since there are a lot of moving parts! Yes. The `

[bug #66114] [gropdf] support embedding bit-mapped image files into a PDF

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

[bug #66114] [gropdf] support embedding bit-mapped image files into a PDF

Update of bug #66114 (group groff): Item Group:None => Feature change ___ Reply to this item at: ___ Message

[bug #66114] [gropdf] support embedding bit-mapped image files into a PDF

Follow-up Comment #4, bug #66114 (group groff): Didn't take long for my new, more communicative diagnostic messages to pay off! It's almost like you were waiting for them... 😜 troff:src/devices/gropdf/gropdf.1:980: warning: special character 'u2717' not defined troff: backtrace: file 'man/groff

[bug #66114] [gropdf] support embedding bit-mapped image files into a PDF

Follow-up Comment #5, bug #66114 (group groff): The missing u2717 is in the postscript ZD font if you use the version I uploaded to the bug about accessing unicode in the dingbats font (version attached). Please feel free to improve my documentation (and coding style) :-) We need to think about

[bug #66114] [gropdf] support embedding bit-mapped image files into a PDF

Follow-up Comment #6, bug #66114 (group groff): Forgot the font! (file #56371) ___ Additional Item Attachment: File name: ZD Size: 6KiB AGPL NOTIC

[bug #65988] some tmac files are not listed as dependencies for compilations

Update of bug #65988 (group groff): Category:Core => General ___ Reply to this item at: ___ Message

[bug #66114] [gropdf] support embedding bit-mapped image files into a PDF

Follow-up Comment #7, bug #66114 (group groff): [comment #5 comment #5:] > The missing u2717 is in the postscript ZD font if you use the version I uploaded to the bug about accessing unicode in the dingbats font (version attached). I think I hear the sound of bug #63018 knocking. Looping in Da

[bug #66114] [gropdf] support embedding bit-mapped image files into a PDF

Follow-up Comment #8, bug #66114 (group groff): [comment #7 comment #7:] > I think I hear the sound of bug #63018 knocking. I concur. Is there a specific question about it here? Bug #63018, if you ignore all its side trips, seems ready to commit, unless there are any objections to Deri's patche

[bug #63018] [PATCH] make glyphs in ZD font accessible via their Unicode spellings

Follow-up Comment #38, bug #63018 (group groff): The first 6 comments here, summarized in comment #33, seem to contain everything needed to resolve the original bug. All the divergences have been spun off into other tickets. ___ Reply to

[bug #63018] [PATCH] make glyphs in ZD font accessible via their Unicode spellings

Update of bug #63018 (group groff): Status: Confirmed => Need Info Assigned to:None => deri ___ Follow-up Comment #39: Hi Deri, The comment

[bug #63018] [PATCH] make glyphs in ZD font accessible via their Unicode spellings

Follow-up Comment #40, bug #63018 (group groff): [comment #39 comment #39:] > +$space_width = $opt_w if $opt_w; Better: +$space_width = $opt_w if defined $opt_w; > (It's important to me to prove reconstructibility of the font descriptions _grops_ has used for 12 years.) Fourteen years.

[bug #66114] [gropdf] support embedding bit-mapped image files into a PDF

Follow-up Comment #9, bug #66114 (group groff): [comment #5 comment #5:] > Please feel free to improve my documentation (and coding style) :-) Sure thing. Outside of gropdf.pl I strongly prefer to enforce the 72-character line length limit, so some \newlines may be arriving in "pdfpic.tmac" soon