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
: None
___
Follow-up Comments:
---
Date: Sat 22 Jun 2024 07:52:18 PM UTC By: Deri James
The attached two pdfs are for an 8x3 inch and a 4x1.5 dashed ellipses, i.e.
one is half the size of the other. One looks lovely and one
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
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
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
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
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
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
Update of bug #64005 (group groff):
Status: Fixed => Need Info
Open/Closed: Closed => Open
___
Follow-up Comment #7:
I think there may be a
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
commit b8038971a3cc51cd3981af49092dbdb493f76c06 (HEAD -> master)
Author: Deri James
Date: Sat May 25 13:40:21 2024 +0100
[gropdf] Deal better with invalid destination names.
Bookmark destinations (supplied by -T to .pdfbookmark)
are "Name Objects" in pdf terms, as su
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
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
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
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
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
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
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
ed Release: None
___
Follow-up Comments:
---
Date: Wed 08 May 2024 11:47:44 PM UTC By: Deri James
As an example current glyphlist.txt has:-
bqsquare;33C3
braceex;F8F4
braceleft;007B
but our
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
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
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.
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
Follow-up Comment #14, bug #63018 (group groff):
[comment #9 comment #9:]
> Hi Dave,
>
> [comment #8 comment #8:]
> > To clarify: my objection isn't the stale afmtodit version
>
> It is nevertheless a legitimate one. We should be dogfooding the font
description files that _afmtodit_
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
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
Follow-up Comment #5, bug #65601 (group groff):
> It would help if you didn't assume autocratic motives behind my code
changes.
But I'm unsure how to achieve that. By autocratic I am simply meaning that you
seem to assume that your ideas are automatically better than your inferiors.
In this bug
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
->
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
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
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
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
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
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
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:-
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.
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
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
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
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
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
: None
___
Follow-up Comments:
---
Date: Tue 16 Apr 2024 11:21:28 AM UTC By: Deri James
If preconv produces a valid composite character groff should not reject it. Of
course if the composite is not available in any availabl
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
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
Follow-up Comment #2, bug #65585 (group groff):
Hi Branden,
All the issues raised in this bug have now been fixed in the release I've just
done, one regression is outstanding, can't convert "rs" to unicode, but I will
fix that.
Alex is not screaming because the "special sauce" I gave him to
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
: None
___
Follow-up Comments:
---
Date: Fri 12 Apr 2024 03:51:08 PM UTC By: Deri James
I have been looking at the current state of pdf.tmac and have found a few
issues. The changes which have been committed are:-
Introduction of
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
build
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,
Update of bug#64155 (group groff):
Severity: 2 - Minor => 3 - Normal
Status: Fixed => Need Info
Open/Closed: Closed => Open
: None
___
Follow-up Comments:
---
Date: Sat 03 Feb 2024 01:39:01 PM UTC By: Deri James
Truncates name.
___
Reply to this item at:
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
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
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
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
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
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
: None
___
Follow-up Comments:
---
Date: Tue 30 Jan 2024 04:54:29 PM UTC By: Deri James
To bring it more into line with the LinuxManBook.pdf add clickable links to
navigate between separate man entries in the volume, and add a front cover
Update of bug#65215 (group groff):
Status: In Progress => Fixed
___
Follow-up Comment #1:
Fixes committed.
commit d71f9264f8c187aee1161f27cda7d42c4ad7065e
Author: Deri James
AuthorD
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
: None
___
Follow-up Comments:
---
Date: Fri 26 Jan 2024 01:27:39 PM UTC By: Deri James
These macros are meant to produce hyperlinks (according to groff
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
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
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
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
Update of bug#65097 (group groff):
Status: Need Info => Invalid
Open/Closed:Open => Closed
___
Follow-up Comment #4:
Yes. Bjarni's else
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
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
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
Update of bug#65115 (group groff):
Status: Fixed => Need Info
Assigned to:deri => gbranden
Open/Closed: Closed => Open
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 golds and
Update of bug#65112 (group groff):
Status:None => In Progress
Assigned to:None => gbranden
___
Follow-up Comment #10:
No, it was not
Update of bug#65112 (group groff):
Status: In Progress => None
Assigned to:gbranden => None
___
Follow-up Comment #8:
On Bookworm I did
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
Follow-up Comment #6, bug#65112 (group groff):
Apologies for the brevity, it was one of those "go to bed and wake up bolt
upright with the answer", just wanted you to confirm the fix was good. Now the
explanation:-
Type 1 fonts have a section of numbered subroutines which can be called from
the
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
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
Follow-up Comment #1, bug#65112 (group groff):
Please can you attach the pdf produced, but first could you try the run with
-P-e. Without this, all the fonts used (except symbol slanted) are base fonts
so no fonts are embedded (so no subsetting either), and its pot luck if your
pdf viewer picks a
Follow-up Comment #1, bug#65111 (group groff):
As I have documented elsewhere gropdf has to behave a little differently if a
particular font does not define a space glyph. This is because it can use a
slightly more compact format if the font defines "space" or "u0020" as a
glyph. In a "Hello
Follow-up Comment #4, bug#65098 (group groff):
Red Tree
I assume you have built my branch at some point, any Titian hues?
Special Pleading (MR)
=
You were correct I was bending a general case to try to fit a special case.
For Iterator
I can see many
Follow-up Comment #2, bug#65098 (group groff):
Dealing with gropdf.pl separately, I have cobbled together a document which
may help you in the task. It is a list of all the diffs with a following
comment which describes what the changes accomplish. One way of handling this
is to introduce each
Update of bug#65095 (group groff):
Status:None => Invalid
Assigned to:None => deri
Open/Closed:Open => Closed
: None
___
Follow-up Comments:
---
Date: Sat 30 Dec 2023 11:01:14 PM UTC By: Deri James
I thought it might be helpful to have a place where we can see progress on
this.
I have noticed some cherry picking from the branch happening so I'm h
Follow-up Comment #1, bug#65097 (group groff):
If I look at the output produced by:-
pdfmom ../doc/automake.mom -P-d | less
I can see:-
% x X ps: exec 0 setlinejoin
%% V12000
0 j
% V12000
% H72000
% x X ps: exec 0 setlinecap
%% wh2500
0 J
So the "0 j" has been emitted in response to the 0
Follow-up Comment #1, bug#65094 (group groff):
EPS files are not supported in pdf files, and gropdf only supports embedding
pdf files (in the same way as grops only supports embedding eps files). There
is a macro PDFPIC which does a similar job as PSPIC.
I changed the mixed-pickles.roff to this
Follow-up Comment #1, bug#65095 (group groff):
I used this command:-
./test-groff -Tpdf -mhdtbl -U -dfontpath=font/ -dsopath=../contrib/hdtbl/
contrib/hdtbl/examples/fonts_x.roff
In the build directory. Seems to work. (I'm using the deri-gropdf-ng branch,
don't know about 1.23.0)
deri pushed a commit to branch deri-gropdf-ng
in repository groff.
commit 2e6d61716710aaca2fff9bf37747a455afff22a5
Author: Deri James
AuthorDate: Fri Dec 29 23:28:11 2023 +
Bug #65092 rounded corners in hdtbl's color_boxes
The \X'ps: exec ...' for setlinejoin and setlinecap
Follow-up Comment #12, bug#62830 (group groff):
Just a note to point out that gropdf (in the deri-gropdf-ng git branch)
already handles CJK documents. The attached pdf is an example, you should see
CJK in the pdf bookmarks as well.
(file #55489)
Follow-up Comment #1, bug#65052 (group groff):
The test you are using is a bit strange. The only proper use for these
commands are to include files which are independently movement agnostic. What
I mean is they contain grout which does something completely independent of
the document which calls
deri pushed a commit to branch deri-gropdf-ng
in repository groff.
commit 7ac813810503f0a012767b38db0b769adeab03a0
Author: Deri James
AuthorDate: Thu Nov 23 00:04:54 2023 +
pdfmarksuspend & pdfmarkresume only if -Tpdf
tmac/an.tmac: Fix for non pdf man use!!
---
tmac/an.
deri pushed a commit to branch deri-gropdf-ng
in repository groff.
commit aa1e2c70eba3fe7adb6cbddbf74764abc21578d1
Author: Deri James
AuthorDate: Fri Nov 24 16:02:00 2023 +
Problem processing concatenated dit files (-Z)
Normally it is safe to pass concatenated dit files
deri pushed a commit to branch deri-gropdf-ng
in repository groff.
commit 5989eda83e6cc399988756ba163ad4c2ad1fc9d9
Author: Deri James
AuthorDate: Sun Dec 10 20:05:43 2023 +
Fix arc drawing when flag -l used.
* src/devices/gropdf/gropdf.pl: When landscape flag (-l) is given
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",
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
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
Follow-up Comment #4, bug #64728 (project groff):
> Heirloom nroff reports the same zero width, so if this is indeed a bug, it's
a widespread one.
If you consider the width of a diversion is the horizontal displacement of the
longest line in the diversion, then the horizontal displacement in
Follow-up Comment #3, bug #64592 (project groff):
Hi Branden,
Just a few thoughts really, I agree the registers are behaving as currently
documented, the question is whether the current behaviour makes sense.
Groff currently has no concept of opacity, gropdf allows pdfs included by
pdfpic to
deri pushed a commit to branch deri-gropdf-ng
in repository groff.
commit a2e72beef12ccc05a933493cfc3a9d6d9dde61c2
Author: Deri James
AuthorDate: Wed Sep 6 22:44:57 2023 +0100
Enable more hyperlinks in groff-man-pages.pdf
---
doc/doc.am | 2 +-
1 file changed, 1 insertion(+), 1 deletion
deri pushed a commit to branch deri-gropdf-ng
in repository groff.
commit 2b3f346ce6ff2e195903cbfb00df66307c65f35a
Author: Deri James
AuthorDate: Fri Sep 1 12:03:52 2023 +0100
Add missing 'tmac' flag
Allows gropdf to know this papersize change came from -dpaper=
---
tmac
deri pushed a commit to branch deri-gropdf-ng
in repository groff.
commit f685c65f2639219103e2c6d15b5f1e4d93344507
Author: Deri James
AuthorDate: Fri Sep 1 12:07:23 2023 +0100
Fixes for .pdfpagenumbering and .pdfswitchtopage
---
src/devices/gropdf/gropdf.pl | 32
1 - 100 of 487 matches
Mail list logo
