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

2024-07-17 Thread Deri James
Follow-up Comment #33, bug #63018 (group groff): Hi Dave, This started off as a simple request to give access to Dingbats glyphs via their \[u] names... and then wandered! The main wandering was the desire to make the grops fonts to be generated during a groff build, and I have given up on

[bug #65910] [pic] some dashed ellipse sizes produce irregular dashes

2024-07-10 Thread Deri James
Follow-up Comment #9, bug #65910 (group groff): In some cases pic can't draw an arc of the desired length in one go, it has to break it down into multiple pieces. If you imagine a very flat ellipse and a dash length which wraps around the foci there is no one circlar arc which can draw the line,

[bug #65910] [pic] some dashed ellipse sizes produce irregular dashes

2024-06-26 Thread Deri James
Follow-up Comment #2, bug #65910 (group groff): I've spent some time on this but I don't think I have got very far. I have written some debug code in gropdf to try and show what is happening. Attached are examples. I hope the patterns may mean something to someone more mathematical than I.

[bug #65901] [gropdf] unable to render ellipse with dashed/dotted atribute

2024-06-22 Thread Deri James
Follow-up Comment #5, bug #65901 (group groff): I don't think bug #44530 is related, that seems to be a misunderstanding what ".PS 1i" does to picture. You may have specified a certain space/dashwid but the inclusion of .PS 1i has the effect of scaling the whole picture down to 1 inch so

[bug #65910] Some dashed ellipse sizes produce irregular dashes

2024-06-22 Thread Deri James
URL: <https://savannah.gnu.org/bugs/?65910> Summary: Some dashed ellipse sizes produce irregular dashes Group: GNU roff Submitter: deri Submitted: Sat 22 Jun 2024 07:52:18 PM UTC Category: Preprocess

[bug #65901] [gropdf] unable to render ellipse with dashed/dotted atribute

2024-06-22 Thread Deri James
fixed now:- commit dd63af83c106a6a44dbb15ab36d5f3e211515ca5 Author: Deri James Date: Sat Jun 22 18:33:49 2024 +0100 Fix invalid pdf when using certain sizes of dashed ellipse in pic. * src/devices/gropdf/gropdf.pl: For short dashes on flat part of ellipse some v. small n

[groff] 01/01: [gropdf] I left a line of debug code

2024-06-22 Thread Deri James
deri pushed a commit to branch master in repository groff. commit 5a68413f9458f0b27522019915ed8f0b7ec1b09e Author: Deri James AuthorDate: Sat Jun 22 18:40:39 2024 +0100 [gropdf] I left a line of debug code * src/devices/gropdf/gropdf.pl: Remove it. --- src/devices/gropdf/gropdf.pl

[groff] 01/01: Fix invalid pdf when using certain sizes of dashed ellipse in pic.

2024-06-22 Thread Deri James
deri pushed a commit to branch master in repository groff. commit dd63af83c106a6a44dbb15ab36d5f3e211515ca5 Author: Deri James AuthorDate: Sat Jun 22 18:33:49 2024 +0100 Fix invalid pdf when using certain sizes of dashed ellipse in pic. * src/devices/gropdf/gropdf.pl: For short

[bug #65901] [gropdf] unable to render ellipse with dashed/dotted atribute

2024-06-20 Thread Deri James
Follow-up Comment #2, bug #65901 (group groff): Morton wrote on the bug list:- > Odd. The pdf on my end is simply broken. It doesn't show in > mupdf either. Please could you run the dotted ellipse example again but adding this flag "-P-d", and post the resulting pdf. This adds some debug data

[bug #65901] [gropdf] unable to render ellipse with dashed/dotted atribute

2024-06-20 Thread Deri James
Follow-up Comment #1, bug #65901 (group groff): After changing elipse to ellipse in the two code examples, I can't recreate the first problem. The dots are visible in zathura. The issue with dashed is real and is down to my appalling ability with maths. For dashed ellipse/circles groff outputs

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

2024-06-06 Thread Deri James
Follow-up Comment #8, bug #65619 (group groff): [comment #7 comment #7:] > As a refresher, I'm wondering what should be done about some of the space glyphs identified in comment #5. > So, check for "space", "uni0020", and "uni00A0" in that order? Yes. > sterlingmonospace;FFE1 This is not a

[bug #64005] [ms] fix for Savannah #62688 suppresses page breaks between displays

2024-05-29 Thread Deri James
Update of bug #64005 (group groff): Status: Fixed => Need Info Open/Closed: Closed => Open ___ Follow-up Comment #7: I think there may be a

[groff] 01/01: [gropdf] Deal better with invalid destination names.

2024-05-25 Thread Deri James
deri pushed a commit to branch master in repository groff. commit b8038971a3cc51cd3981af49092dbdb493f76c06 Author: Deri James AuthorDate: Sat May 25 13:40:21 2024 +0100 [gropdf] Deal better with invalid destination names. Bookmark destinations (supplied by -T to .pdfbookmark

[bug #65788] gropdf: warning: PDF Dict Key 'User' does not start with '/'

2024-05-25 Thread Deri James
Update of bug #65788 (group groff): Status:None => Fixed Assigned to:None => deri ___ Follow-up Comment #1:

[groff] 01/01: [gropdf] Problem if mixed fonts have different lenIV.

2024-05-17 Thread Deri James
deri pushed a commit to branch master in repository groff. commit 4c62e07f364957be83fe9fe46151a9edb544a34c Author: Deri James AuthorDate: Fri May 17 17:48:55 2024 +0100 [gropdf] Problem if mixed fonts have different lenIV. * src/devices/gropdf/gropdf: Restore default value (4

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

2024-05-14 Thread Deri James
Follow-up Comment #31, bug #63018 (group groff): I have been investigating the AFMs Branden found with a view to using them as a way to recreate the grops fonts, particularly in situations where there have been changes to the maps, encoding files and afmtodit itself. Since the last release

[groff] 01/03: [gropdf] Passing just "\" as a bookmark problem.

2024-05-14 Thread Deri James
deri pushed a commit to branch master in repository groff. commit 2cf8f41d3f9985da0670ddd2cbc07837d5433299 Author: Deri James AuthorDate: Wed May 8 18:39:30 2024 +0100 [gropdf] Passing just "\" as a bookmark problem. * src/devices/gropdf/gropdf: it ends up as a

[groff] 03/03: Forgot to push last two fixes.

2024-05-14 Thread Deri James
deri pushed a commit to branch master in repository groff. commit d998339bef8af990cca00b2b0a9939cc9fc2e7cf Author: Deri James AuthorDate: Tue May 14 15:43:44 2024 +0100 Forgot to push last two fixes. --- ChangeLog | 19 +++ 1 file changed, 19 insertions(+) diff --git

[groff] 02/03: [gropdf] \X'pdf: xrev' has issues.

2024-05-14 Thread Deri James
deri pushed a commit to branch master in repository groff. commit 4886b57816841de32c51b88ccffc9580b07bb535 Author: Deri James AuthorDate: Wed May 8 22:23:28 2024 +0100 [gropdf] \X'pdf: xrev' has issues. * src/devices/gropdf/gropdf: Fails if point size not = 10, in a number

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

2024-05-12 Thread Deri James
Follow-up Comment #29, bug #63018 (group groff): Dave. I think the implied question is: When it is a separate make target (bug #65698), if we wish to retain the epsilon kerns the make target must either re-apply the shell script after the font generation, or these "gold" AFMs should have the

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

2024-05-12 Thread Deri James
Follow-up Comment #26, bug #63018 (group groff): I have been investigating the AFMs contained in the tar files Branden referenced in comment #15. Using the 229 versions it is possible to generate the 35 fonts for grops. The only difference is that our fonts include kerning data for the ellipsis

[bug #65716] We don't seem to be using the "latest" glyphlist.txt to generate the tables for afmtodit.

2024-05-08 Thread Deri James
URL: <https://savannah.gnu.org/bugs/?65716> Summary: We don't seem to be using the "latest" glyphlist.txt to generate the tables for afmtodit. Group: GNU roff Submitter: deri Submitted: Wed 08 May 2024

[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

[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-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 #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
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] 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 #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 #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 #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 ->

[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 #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

[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] 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

[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 #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 #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.

[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

[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] 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/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

[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

[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

[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

[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] 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

Re: Milestone reached: hyperlinked mdoc(7) documents in PDF

2024-03-22 Thread Deri
On Friday, 22 March 2024 16:59:14 GMT Alejandro Colomar wrote: > ow, how am I supposed to > get that patch without anyone tampering it during its trip to my > computer? :( derij@ws:~$ md5sum /var/www/chinese.patch.gz 109e2681b7402ca55118226aa575b6d3 /var/www/chinese.patch.gz

Tears in my eyes, joy in my heart (was: gropdf-ng merge status (was: PDF outline not capturing Cyrillic text))

2024-02-07 Thread Deri
nd I say farewell to the lovely people on the list, I shall be clocking off the list probably tomorrow, I can't say I won't be back at some point, but I definitely need a good 6 months at least. You have warn me out Branden, you should have agreed to video calls when I suggested it. :-) Cheers Deri x

Re: PDF outline not capturing Cyrillic text

2024-02-07 Thread Deri
e some sad news later. :- ( I wonder if you could send me a small example of .pdfhref L missing letters and the command you are using, I don't need the whole thesis, I would not understand it. Cheers Deri

Re: gropdf-ng merge status (was: PDF outline not capturing Cyrillic text)

2024-02-06 Thread Deri
On Tuesday, 6 February 2024 14:45:59 GMT G. Branden Robinson wrote: > Hi Deri, > > Now _does_ seem to be a good time to catch up on gropdf-ng merge status. > There were two things I knew were still unmerged: the slanted symbol > (SS) font support and the stringhex business, w

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

2024-02-06 Thread Deri James
Update of bug#64155 (group groff): Assigned to:deri => gbranden ___ Follow-up Comment #21: Hi Branden, I've worked it out. This is the problem, I had a corrupt copy of U-TR in my bu

[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,

Re: Configuring groff 1.23.0 on Fedora 39 fails to find the URW base 35 fonts

2024-02-05 Thread Deri
gt; > /usr/local/share/fonts/ghostscript/" > > No, none of those directories exist. > > However, /usr/share/fonts/urw-base35 does exist and does contain .afm files. Hi, Have you tried running configure with the flag:- --with-urw-fonts-dir=/usr/share/fonts/urw-base35 Cheers Deri

[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

[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

Re: Ornamented Page Borders

2024-02-02 Thread Deri
ge documents, possibly hooking in to NEWPAGE as well. You can run the example like this:- groff -Tpdf -mom -k -P-pa4 ornmom.tr /usr/share/doc/groff-1.23.0/examples/mom/ letter.mom > letter.pdf The document, including the letter, is now 6.3kb. Cheers Deri .ig groff -Tpdf -p ornsingle.tr -P-p.

[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

Re: Milestone reached: hyperlinked man(7) documents in PDF

2024-02-01 Thread Deri
On Thursday, 1 February 2024 20:58:09 GMT G. Branden Robinson wrote: > At 2024-01-31T13:19:18+0000, Deri wrote: > > Oops, did not mean to send that, although it does show okular working > > properly with an .MT link. > > I concur. It seems to only go wrong if the hotsp

Re: Milestone reached: hyperlinked man(7) documents in PDF

2024-01-31 Thread Deri
On Wednesday, 31 January 2024 13:02:57 GMT Deri wrote: > On Wednesday, 31 January 2024 05:10:21 GMT G. Branden Robinson wrote: > > Hi folks, > > > > In a frenzy of activity over the past few days Deri and I have landed > > everything necessary to bring full hyperlink

[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

[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] 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] 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] 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

[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

Re: [groff] 02/14: [man]: Warn on bad MT/ME/UR/UE nesting.

2024-01-30 Thread Deri
Seems to work, in this instance, but perhaps there is a better way. Cheers Deri

Re: [groff] 02/14: [man]: Warn on bad MT/ME/UR/UE nesting.

2024-01-30 Thread Deri
Seems to work, in this instance, but perhaps there is a better way. Cheers Deri ___ Groff-commit mailing list Groff-commit@gnu.org https://lists.gnu.org/mailman/listinfo/groff-commit

[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 #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

Re: Proposed: make \X read its argument in copy mode

2024-01-23 Thread Deri
oblem is of greater interest to practical users: > _embedding_ newlines inside device control commands. \X didn't > support that anyway, neither in DWB troff nor groff.[2] Hi Branden, Just to be sure, can you confirm your intention is to return .device to its 1.23.0 state, and mirror that behaviour for \X, so we will have no more red seepage. Cheers Deri

Re: Tibetan fonts

2024-01-21 Thread Deri
; > Regards, > > Tom > Hi Tom, Using the font suggested by Oliver (after installing it with Peter Schafter's install-font.sh script) and using the latest unicode aware pdf generation version of groff (awaiting release by Branden), with this script:- .ft TibetanR \" What I called

Re: Proposed: make \X read its argument in copy mode

2024-01-20 Thread Deri
On Saturday, 20 January 2024 00:56:34 GMT G. Branden Robinson wrote: > Hi Deri, > > At 2024-01-20T00:07:21+0000, Deri wrote: > > On Friday, 19 January 2024 21:39:57 GMT G. Branden Robinson wrote: > > > Right. Before I craft a lengthy response to this--did you see the >

Re: Proposed: make \X read its argument in copy mode

2024-01-20 Thread Deri
ax, I think.) > > ...and it getting called by some other macro encoding the argument... > > .de pdflink > . ds pdf*input \\$*\" > . encode pdf*input \" performs magic transformation, like "stringhex" > . pdfmark2 \\*[pdf*input] > .. > > ...

Re: Proposed: make \X read its argument in copy mode

2024-01-19 Thread Deri
On Friday, 19 January 2024 21:39:57 GMT G. Branden Robinson wrote: > Hi Deri, > > At 2024-01-19T21:16:54+0000, Deri wrote: > > On Tuesday, 16 January 2024 19:22:48 GMT G. Branden Robinson wrote: > > > Or: Should device control commands affect the environment? > >

Re: Proposed: make \X read its argument in copy mode

2024-01-19 Thread Deri
he necessity of having the ability to pass all unicode and other characters to postprocessors and are aware that .device was already capable of doing that, I have no objection to you extending this capability to \X if that is your wont, but the current state of master is the opposite. Cheers Deri

[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

[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-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

[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

Re: the 'SS' (slanted symbol) font (was: Original print of V7 manual? / My own version of troff)

2024-01-12 Thread Deri
ace looks very nice. > > I did the color coding by inserting color commands into > the intermediate output wherever a font change occurred. Brilliant, I wish I had thought of doing that, much easier after I wrote a little perl script. I ran it again with your suggestion, setting

[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

Re: the 'SS' (slanted symbol) font (was: Original print of V7 manual? / My own version of troff)

2024-01-10 Thread Deri
aced) > > > 6-9: SS, S, ZD, ZDR (special) > > > > Heavens no! "CW" is a System-V-ism. We have CR, CI, CB, and CBI. > > Yes, but it explains why there are 5 empty positions in the > "fonts" declaration before SS, S, ZD, and ZDR. :-) Hi Tadziu, For people producing greek documents who wish to use eqn, I did some testing, using the Tinos family of fonts (R, I, B, BI) which include greek glyphs and SS font for gropdf. The attached pdf shows the results with the different fonts colour coded. If you want to see the slanted versions for alpha and beta, it is best to set the family to T and select TinosR as the main font. Cheers Deri eqn.pdf Description: Adobe PDF document

[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

Re: [groff] 04/08: ChangeLog: Add entries for Deri's recent changes.

2024-01-08 Thread Deri
On Monday, 8 January 2024 02:16:40 GMT G. Branden Robinson wrote: > gbranden pushed a commit to branch master > in repository groff. Thank you. ___ Groff-commit mailing list Groff-commit@gnu.org https://lists.gnu.org/mailman/listinfo/groff-commit

Re: [groff] 04/08: ChangeLog: Add entries for Deri's recent changes.

2024-01-08 Thread Deri
On Monday, 8 January 2024 02:16:40 GMT G. Branden Robinson wrote: > gbranden pushed a commit to branch master > in repository groff. Thank you.

Re: deri-gropdf-ng branch dependency graph

2024-01-08 Thread Deri
On Monday, 8 January 2024 03:29:26 GMT G. Branden Robinson wrote: > At 2024-01-07T10:13:44+0000, Deri wrote: > > Now that Branden has started to incorporate the new gropdf, I > > thought it may help to try to document the dependencies between > > the different f

[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

deri-gropdf-ng branch dependency graph

2024-01-07 Thread Deri
from an "in memory" database I wrote once, very micky mouse, but useful for displaying relationship in a small data set. Cheers Deri Features.pdf Description: Adobe PDF document

Re: Auto-relocated TOC in wrong place in pdf outlines

2024-01-06 Thread Deri
$curoutlevno--; } } } Cheers Deri

[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 =

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

2024-01-04 Thread Deri James
Follow-up Comment #4, bug#65115 (group groff): > I can push this fix with others later today if Deri doesn't beat me to it. I'm unlikely to win that race. I did take part in the UK National Spastic Games, in my youth, representing the South-East region. Well before paralympics. Won 3 go

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

2024-01-04 Thread Deri James
Update of bug#65112 (group groff): Status:None => In Progress Assigned to:None => gbranden ___ Follow-up Comment #10: No, it was not

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

2024-01-04 Thread Deri James
Update of bug#65112 (group groff): Status: In Progress => None Assigned to:gbranden => None ___ Follow-up Comment #8: On Bookworm I did

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

2024-01-04 Thread Deri James
Update of bug#65115 (group groff): Status:None => Fixed Summary: U-BMI and U-BMR show switched font names in fonts_{n,x}.pdf => BMI and BMR definitions are switched in Foundry.in for the U foundry

  1   2   3   4   5   6   7   8   >