[bug #65112] [gropdf] glyphs missing from groff_char(7) but not warned about

2024-01-03 Thread Deri James
Follow-up Comment #3, bug#65112 (group groff): Ooh, a proper bug. Please can you look in font/devpdf/download file and send me whichever file is assigned to the Symbol font. I can't duplicate the problem with three different versions of the Symbol font file but you may have a fourth. I have a

[bug #65115] [PATCH] BMI and BMR definitions are switched in Foundry.in for the U foundry

2024-01-06 Thread Deri James
Update of bug#65115 (group groff): Status: Fixed => Need Info Assigned to: deri => gbranden Open/Closed: Closed =

[groff] 01/01: Retain plain ascii labels when possible.

2024-01-14 Thread Deri James
deri pushed a commit to branch master in repository groff. commit e62b188aacb0669bf45628796dd543992e440047 Author: Deri James AuthorDate: Sun Jan 14 13:57:30 2024 + Retain plain ascii labels when possible. * src/devices/gropdf/gropdf.pl: Do not use hexed label unless

[bug #63074] [troff] support construction of arbitrary byte sequences in device control commands

2024-01-14 Thread Deri James
Follow-up Comment #24, bug#63074 (group groff): Bug #64484 is marked as fixed. I already have a reliable way to pass byte sequences in device control commands, .stringhex. This bug was previously named "warning messages when using special characters in TITLE or AUTHOR" and the attached

[bug #64285] [troff] \D't' (set line thickness) drawing command alters drawing position

2024-01-14 Thread Deri James
Follow-up Comment #12, bug#64285 (group groff): [comment #10 comment #10:] > I see very little difference between PS and PDF output for your input exhibit in comment #9, using bleeding-edge _groff_. I agree. > Regarding the topic at issue, I propose that the first and second paragraphs should

[bug #63074] [troff] support construction of arbitrary byte sequences in device control commands

2024-01-15 Thread Deri James
ces.) The pdfmark API was around well before I wrote gropdf, so I just had to support it. What about embedded calls to macros (i.e. \*[macro arg]) I deal with that as well. Here's an example from mom-pdf.mom again:- .AUTHOR "Deri James" "\*[UP .5p]and" "Peter Schaffter&quo

[groff] 02/02: Misplaced TOC in mom.

2024-01-07 Thread Deri James
deri pushed a commit to branch master in repository groff. commit d27c4644a098855051322a073a313fda165d4eaf Author: Deri James AuthorDate: Sun Jan 7 20:14:34 2024 + Misplaced TOC in mom. See https://lists.gnu.org/archive/html/groff/2024-01/msg00015.html * src/devices

[groff] 01/02: Fix for including pdf v1.7 files.

2024-01-07 Thread Deri James
deri pushed a commit to branch master in repository groff. commit 7c0358816253817a3594be6402c4b9b7e68db01d Author: Deri James AuthorDate: Sun Jan 7 19:51:35 2024 + Fix for including pdf v1.7 files. PDF 1.5 introduced object type ObjStm which can contain a bunch

[bug #63074] [troff] support construction of arbitrary byte sequences in device control commands

2024-01-09 Thread Deri James
Follow-up Comment #22, bug#63074 (group groff): Whew, rather a lot to cover! First the original "bug" was "fixed" by including -f U-T in the command. Next it became a wish to include non-latin character in the bookmarks. This is now working on my branch, waiting for Branden's integration. Then

[bug #65112] [gropdf] glyphs missing from groff_char(7) but not warned about

2024-01-03 Thread Deri James
Follow-up Comment #5, bug#65112 (group groff): Try this. diff --git a/src/devices/gropdf/gropdf.pl b/src/devices/gropdf/gropdf.pl index e26bc6b43..d55bc1e00 100644 --- a/src/devices/gropdf/gropdf.pl +++ b/src/devices/gropdf/gropdf.pl @@ -4733,7 +4733,11 @@ sub subs_call my

[bug #65097] gropdf: one 'ps:' tag is now not processed

2024-01-11 Thread Deri James
Update of bug#65097 (group groff): Status: Need Info => Invalid Open/Closed:Open => Closed ___ Follow-up Comment #4: Yes. Bjarni's else

[bug #65215] .MT/.ME and .UR/.UE should result in hyperlink for pdf output

2024-01-26 Thread Deri James
Update of bug#65215 (group groff): Status: In Progress => Fixed ___ Follow-up Comment #1: Fixes committed. commit d71f9264f8c187aee1161f27cda7d42c4ad7065e Author: Deri James AuthorD

[groff] 01/01: .MT/.ME and .UR/.UE hyperlinking for pdf output

2024-01-26 Thread Deri James
deri pushed a commit to branch master in repository groff. commit d71f9264f8c187aee1161f27cda7d42c4ad7065e Author: Deri James AuthorDate: Fri Jan 26 15:47:28 2024 + .MT/.ME and .UR/.UE hyperlinking for pdf output Our documentation groff_man.7 documents that these requests

[bug #61434] [man] want support for hyperlinked paragraph tags

2024-02-02 Thread Deri James
Follow-up Comment #4, bug#61434 (group groff): [comment #3 comment #3:] > This was an important follow-up commit. > commit 52a5a89c0da9f90c83441b8eb8020344a8468686 > Author: G. Branden Robinson > Date: Thu Feb 1 23:23:45 2024 -0600 > ... > Unfortunately, "pdf.tmac" doesn't > expose a

[bug #64155] specifying -fZD on command line generates warnings

2024-02-05 Thread Deri James
Follow-up Comment #19, bug#64155 (group groff): Further testing shows that test-groff works but after a make install it fails!! test-groff [pid 3056312] openat(AT_FDCWD, "/home/derij/groff-git/groff/build/font/devpdf/U-TR", O_RDONLY) = 3 [pid 3056312] newfstatat(3, "", {st_mode=S_IFREG|0644,

[bug #64155] specifying -fZD on command line generates warnings

2024-02-05 Thread Deri James
> Open ___ Follow-up Comment #18: Why is this happening? [derij@pip Russian]$ echo "Deri" | groff -Tpdf -fU-T -z troff: fatal error: 'U-T' is not a valid font family [derij@pip Russian]$ ls /usr/share/groff/1.23.0/font/devpdf/U-T* /usr/share/groff/1.23.0/font

[groff] 03/05: Changes to satisfy bug #65231.

2024-01-30 Thread Deri James
deri pushed a commit to branch master in repository groff. commit 3e5f09d1b3a9df072cd2a67b648925049a655e82 Author: Deri James AuthorDate: Tue Jan 30 17:14:08 2024 + Changes to satisfy bug #65231. Alter build of groff-man-pages.pdf to use the new pdfmom, so that all forward

[groff] 02/05: New pdfmom, can now be used with all macros.

2024-01-30 Thread Deri James
deri pushed a commit to branch master in repository groff. commit df1d447c99b984f9fd82f46cfc2becb2475b6d6e Author: Deri James AuthorDate: Tue Jan 30 17:05:00 2024 + New pdfmom, can now be used with all macros. Previously only useful for producing documents with mom

[groff] 04/05: Remove artifacts from using stringhex.

2024-01-30 Thread Deri James
deri pushed a commit to branch master in repository groff. commit 9b8b3e2a508d7df0b661c9042b5f5d5e7a0688da Author: Deri James AuthorDate: Tue Jan 30 18:02:13 2024 + Remove artifacts from using stringhex. Introduced in commit #e62b188aacb, betraying its origin from my deri

[groff] 01/05: Front Cover for groff-man-pages.pdf

2024-01-30 Thread Deri James
deri pushed a commit to branch master in repository groff. commit f619fee72005fba6fc10e5dc22b3df4ffb1372de Author: Deri James AuthorDate: Tue Jan 30 16:55:43 2024 + Front Cover for groff-man-pages.pdf Feel free to alter "artwork" at will (perhaps add maintainer i

[groff] 05/05: Update ChangeLog

2024-01-30 Thread Deri James
deri pushed a commit to branch master in repository groff. commit 3fe0a227e1533f8cc6ff56b890e70c79712a73de Author: Deri James AuthorDate: Tue Jan 30 18:16:11 2024 + Update ChangeLog --- ChangeLog | 37 + 1 file changed, 37 insertions(+) diff --git

[bug #65231] Improve our groff-man-pages.pdf

2024-01-30 Thread Deri James
URL: <https://savannah.gnu.org/bugs/?65231> Summary: Improve our groff-man-pages.pdf Group: GNU roff Submitter: deri Submitted: Tue 30 Jan 2024 04:54:29 PM UTC Category: General Severity: 1

[bug #65215] .MT/.ME and .UR/.UE should result in hyperlink for pdf output

2024-01-26 Thread Deri James
URL: <https://savannah.gnu.org/bugs/?65215> Summary: .MT/.ME and .UR/.UE should result in hyperlink for pdf output Group: GNU roff Submitter: deri Submitted: Fri 26 Jan 2024 01:27:39 PM UTC Category: Mac

[bug #65246] grops download file does not handle .pfa filenames which contain spaces

2024-02-03 Thread Deri James
URL: <https://savannah.gnu.org/bugs/?65246> Summary: grops download file does not handle .pfa filenames which contain spaces Group: GNU roff Submitter: deri Submitted: Sat 03 Feb 2024 01:39:01 PM UTC Ca

[bug #64592] [troff] registers .m and .M contain no initial value

2023-11-18 Thread Deri James
Follow-up Comment #11, bug #64592 (project groff): After the change I ran the code in comment #1 and now the second line works fine (the first line will never work properly because we don't stack colour changes). Interestingly the call to \m[\*[curcol]] where curcol contains the word "default",

[bug #64592] [troff] registers .m and .M contain no initial value

2023-11-16 Thread Deri James
Follow-up Comment #6, bug #64592 (project groff): [comment #5 comment #5:] > Is the problem that registers .m and .M don't behave like other registers (containing the default values), or that the roff language offers no way to retrieve these defaults? See comment #3 which mentions two registers

[bug #64592] [troff] registers .m and .M contain no initial value

2023-11-17 Thread Deri James
Follow-up Comment #8, bug #64592 (project groff): Sorry, my fault, I was not clear. My reference to the registers in comment #3 was intended to show that your statement "registers .m and .M don't behave like other registers (containing the default values)" was the problem. I'm not sure (2) can be

[groff] 01/01: Improve font parsing.

2024-04-17 Thread Deri James
deri pushed a commit to branch master in repository groff. commit 5589bcd18776c6d236c53226a0ee30506180e6b6 Author: Deri James AuthorDate: Wed Apr 17 19:25:03 2024 +0100 Improve font parsing. The usual (for fontforge converted ttf fonts) is to use the RD, ND and NP operators

[groff] 01/01: [gropdf] Handle both types in one document.

2024-04-17 Thread Deri James
deri pushed a commit to branch master in repository groff. commit 0f96f3a281d82bb0c1a59e5e819d2a22bede6c5d Author: Deri James AuthorDate: Thu Apr 18 01:17:22 2024 +0100 [gropdf] Handle both types in one document. The different format of font described in previous commit fails

[bug #65601] Bogus 'bogus composite' errors introduced by commit 6008b6b7aa

2024-04-22 Thread Deri James
Update of bug #65601 (group groff): Assigned to:None => gbranden ___ Follow-up Comment #1: Assigning to Branden as the expert on this, since it seems to be his new code causing the issue.

[bug #65585] [gropdf] problems introduced by commit cd9fde325f

2024-04-14 Thread Deri James
Follow-up Comment #5, bug #65585 (group groff): I am getting this with 'shadow':- derij@raspberrypi5:~/linuxman/man-pages $ make -B build-book MANDIR=../build/man make: *** No rule to make target 'build-book'. Stop. Which used to work before git pull --rebase. So I can't reproduce your page

[bug #65601] Bogus 'bogus composite' errors introduced by commit 6008b6b7aa

2024-04-16 Thread Deri James
URL: <https://savannah.gnu.org/bugs/?65601> Summary: Bogus 'bogus composite' errors introduced by commit 6008b6b7aa Group: GNU roff Submitter: deri Submitted: Tue 16 Apr 2024 11:21:28 AM UTC Category

[groff] 02/02: Correct linear search introduced in commit cd9fde325f

2024-04-12 Thread Deri James
deri pushed a commit to branch master in repository groff. commit 2387949ffc11b753dd91480dcb85be6c22819790 Author: Deri James AuthorDate: Fri Apr 12 17:10:49 2024 +0100 Correct linear search introduced in commit cd9fde325f * tmac/pdf.tmac: Various problems have been rectified

[bug #65585] Problems introduced by commit cd9fde325f

2024-04-12 Thread Deri James
URL: <https://savannah.gnu.org/bugs/?65585> Summary: Problems introduced by commit cd9fde325f Group: GNU roff Submitter: deri Submitted: Fri 12 Apr 2024 03:51:08 PM UTC Category: Driver

[bug #65619] Provide a default value for afmtodit(1) -w, when unspecified

2024-04-24 Thread Deri James
Follow-up Comment #1, bug #65619 (group groff): If no -w is given afmtodit uses the width of the space glyph as the value. This is ideal since this is the value which the font designer has chosen as most appropriate for particular font. The various values for the URW fonts are:-

[bug #62300] [preconv] does not handle U+00A0 (NBSP) as it should

2024-04-27 Thread Deri James
Follow-up Comment #6, bug #62300 (group groff): \[u00A0] is meaningful if you are using a font which defines the glyph. (I appear to have about 67 fonts which define the glyph, some even define kern pairs for the glyph, and one tibetan font defines composites using it). Groff does not convert it

[bug #65585] [gropdf] problems introduced by commit cd9fde325f

2024-04-12 Thread Deri James
which produces "more perfect" typeset equations. For the NEWS file perhaps you can use some of the information in the attached pdf. My condolences for your bereavement. Regards Deri (file #55939) ___ Additional Item Attachm

[groff] 01/01: 4 missing fonts from commit 98b0c1db476

2024-04-12 Thread Deri James
deri pushed a commit to branch master in repository groff. commit cbe5a7802df5ff3a9f84a42e277cf3925a1eb303 Author: Deri James AuthorDate: Fri Apr 12 23:48:10 2024 +0100 4 missing fonts from commit 98b0c1db476 * font/devps: Include CR, CI, CB and CBI with UTF-16 code

[groff] 01/03: Another font with UTF-16 added to comment

2024-04-16 Thread Deri James
deri pushed a commit to branch master in repository groff. commit 3cb502448b1de76036af7c143230ac11f7410bee Author: Deri James AuthorDate: Tue Apr 16 15:28:41 2024 +0100 Another font with UTF-16 added to comment * font/devps/S --- font/devps/S | 316

[groff] 03/03: ... and the ChangeLog

2024-04-16 Thread Deri James
deri pushed a commit to branch master in repository groff. commit 1cd6ed080ff026f0df1e213f4f93523120d54e94 Author: Deri James AuthorDate: Tue Apr 16 17:46:15 2024 +0100 ... and the ChangeLog --- ChangeLog | 24 1 file changed, 24 insertions(+) diff --git

[groff] 02/03: Problem with '(' and '\' (\[rs])

2024-04-16 Thread Deri James
deri pushed a commit to branch master in repository groff. commit f336f8244b09191b16722984c33fc5addcc4a284 Author: Deri James AuthorDate: Tue Apr 16 17:34:59 2024 +0100 Problem with '(' and '\' (\[rs]) Bpth these tokens have meaning for roff AND pdf strings. In pdfs unbalanced

[groff] 01/01: [gropdf] use nospace mode if font does not contain /space glyph.

2024-04-28 Thread Deri James
deri pushed a commit to branch master in repository groff. commit 9e0a3316c7b1f33f22d3b314456b2415cc9856eb Author: Deri James AuthorDate: Sun Apr 28 14:59:05 2024 +0100 [gropdf] use nospace mode if font does not contain /space glyph. Gropdf always had two modes, depending

[groff] 01/01: [gropdf] Can't handle DecodeParams in Deflate filter.

2024-04-28 Thread Deri James
deri pushed a commit to branch master in repository groff. commit 14563f831454bd879f465ac4738624c5e3f380ed Author: Deri James AuthorDate: Sun Apr 28 13:36:31 2024 +0100 [gropdf] Can't handle DecodeParams in Deflate filter. If gropdf called with -d (debug) the pdf is produced

[groff] 01/01: [gropdf] ignore 'Cspace' as input

2024-04-28 Thread Deri James
deri pushed a commit to branch master in repository groff. commit 1ab868c5c84a02f32ab2c385066215d2aa7d650b Author: Deri James AuthorDate: Sun Apr 28 18:03:59 2024 +0100 [gropdf] ignore 'Cspace' as input * src/devices/gropdf/gropdf.pl: As grops does. --- ChangeLog

[groff] 01/01: [gropdf] Re-arrange pattern matches.

2024-04-30 Thread Deri James
deri pushed a commit to branch master in repository groff. commit a951b44fd9d2acf060067b24c994604351a27888 Author: Deri James AuthorDate: Tue Apr 30 15:25:49 2024 +0100 [gropdf] Re-arrange pattern matches. * src/devices/gropdf/gropdf.pl: Correct order of pattern match

[bug #64155] specifying -fZD on command line generates warnings

2024-05-02 Thread Deri James
Follow-up Comment #29, bug #64155 (group groff): > Well, when you're prepared to discuss it, it would be good to know if/how Dave's original report in comment #0 was invalid I think I can answer this - it is certainly not invalid, it just has nothing to do with ZD not being a "proper" family

[bug #63018] font/devps/ZD: make glyphs accessible via their Unicode spellings

2024-04-29 Thread Deri James
Follow-up Comment #5, bug #63018 (group groff): Probably the best way of doing this is by adding to dingbats.map, a suitable one is attached (to replace the one in font/devps/generate). Also attached is a replacement ZD file to be placed in fonts/devps. Doing make will propagate the changes to

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

2024-05-03 Thread Deri James
t; > but that the line claims afmtodit generated it at all: once Deri's ZD is committed, precious little of its content will be from afmtodit. > > I understood Deri as proposing to update "dingbats.map" _and_ regenerating the ZD file using _afmtodit_ with it... > > [com

[bug #64155] [troff] specifying -fZD on command line generates warnings

2024-05-03 Thread Deri James
Follow-up Comment #35, bug #64155 (group groff): [comment #34 comment #34:] > > > Well, when you're prepared to discuss it, it would be good to know if/how Dave's original report in comment #0 was invalid > > > > I think I can answer this - it is certainly not invalid, it just has nothing to do

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

2024-05-03 Thread Deri James
Follow-up Comment #17, bug #63018 (group groff): It is a bit moot now. If Branden does have the original afms for the grops fonts, which produce identical meta-data as currently, then much better to run afmtodit on all of them as a refresh.

[bug #65601] [troff] bogus 'bogus composite' errors introduced by commit 6008b6b7aa

2024-05-01 Thread Deri James
Update of bug #65601 (group groff): Status: Need Info => Confirmed ___ Follow-up Comment #3: It is very simple! [derij@pip build (master)]$ echo "This is the arabic alef with a madda above ->

[bug #65601] [troff] bogus 'bogus composite' errors introduced by commit 6008b6b7aa

2024-05-02 Thread Deri James
her than something like "I agree with Deri" or "Deri is correct", we see "Looks like Deri is right", which could be construed as adding an element of surprise! And, I agree, I am skating on thin ice here, because we are considering autocratic behaviour, and mere words

[bug #65619] [afmtodit] want a default value for space width if unspecified

2024-05-02 Thread Deri James
Follow-up Comment #3, bug #65619 (group groff): Afmtodit has always used the width of the space glyph (if defined in the font), what your change did was enable this to be overridden on the command line, which is probably wrong. If the intention was to provide a fallback value when a spacewidth

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

2024-05-06 Thread Deri James
Follow-up Comment #20, bug #63018 (group groff): This might be a bit previous! Whether we should regenerate the grops font files is rather dependent on whether Branden is successful in locating afm files of a suitable vintage so that running current afmtodit will generate fonts with compatible

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

2024-05-06 Thread Deri James
Follow-up Comment #22, bug #63018 (group groff): Speaking about afmtodit only. If vintage afm files are not forthcoming, then (2 - makefile target) is moot. Only (1) is not dependent and that will be done when I rejig afmtodit to:- Look for different 'spaces' to set 'spacewidth'. Implement -ww

<    3   4   5   6   7   8