On Sunday, 9 March 2025 21:08:58 GMT Nikita Ivanov wrote:
> Hi Deri,
>
> Thank you! Yes, this solution is much easier than having to install
> fonts manually. Some questions and random findings/thoughts:
>
> It seems that it only works for PDF output, is there a similar sim
one
family only). If you include "-fU-T" in the groff command then groff will
replace the whole Times-Roman family with its U- version (until the next .fam
request). I have wished groff had a flag which let you pick the U- foundry for
all fonts, for many years, but alas!
Cheers
Deri
horizontal corner radius, vertical corner radius, and border width. A zero
radius gives square (not rounded) corners. The default is:-
.ds PDFHREF.BORDER 0 0 0
Which produces no border around the hotspot.
==
Cheers
Deri
On Monday, 17 February 2025 22:22:46 GMT G. Branden Robinson wrote:
> [CCing groff@gnu list because some problems arise here that merit being
> findable by search of its list archives]
>
> Hi Deri,
>
> At 2025-02-17T18:52:46+, Deri wrote:
> > > progr
minor
additions to control the page numbering in the overview panel) using this
command:-
pdfmom --roff -ms -M.. -mpdfms -U cover.ms pdfmark2.ms > pdfmark2.pdf
So not using pdfroff and -mspdf just changes to ms contained in pdfms.tmac.
Not perfect, but produces quite acceptable pdfs.
Cheers
Deri
pdfmark2.pdf
Description: Adobe PDF document
On Tuesday, 21 January 2025 05:59:41 GMT G. Branden Robinson wrote:
> Hi onf,
>
[...]
> The good news is, that's sorted out now, and comes with a "NEWS"
> item.[1] Deri was really helpful in sorting out the issues here.
> (As you're aware, there a
meta-data such as Author and Title included
in the pdf.
Cheers
Deri
On Tuesday, 7 January 2025 18:27:56 GMT Francesco Ariis wrote:
> Hello groff users,
>
> how to render clickable links in PDF documents?
>
> I recently discovered `groff`. As an exercises I am typesetting my
> CV in it (`groff -ms`). Say I want to put the link to my personal
> website, what
On Friday, 27 December 2024 14:30:11 GMT Oliver Corff wrote:
> Dear Deri, Dear All,
>
> I just found Deri's wonderfully sober, clean and pleasant presentation
> style and demonstrator which you released back in March 2018:
> https://lists.gnu.org/archive/html/groff/2018-03/
ent"!
> Also, can you tell me what apart from your complaint about performance
> renders my solution substandard? Equivalently, assuming I can make my
> solution performant again, would you regard it as standard? If not,
> why not?
Nothing! If the hash lookup code (which has always been there since Keith
wrote pdfmark.tmac and I used it in pdf.tmac) is considered the "standard",
replacing it with code which can take 39x longer could be considered
substandard. Also there was an error in incrementing the numeric index and a
missed use case (which is why it did not work with mom).
If you can produce code which performs as well (or better) than the code you
replaced, of course it would be welcomed. Remember the purpose of stringhex
was to allow non-ascii to be used in pdf meta-data (e.g. bookmarks).
Cheers
Deri
> Regards,
> Branden
bility of the grout file
important [1], currently lots of \[u] and \(XX are harder to read than
UTF-8. It could be a setting in the DESC file so you don't need to change
output drivers in one go.
I would have hoped that troff would barf at illegal UTF-8 sequences rather
than pass them on th
preted stream
> and nothing else".
Hi Branden,
And here I was thinking 1.25 was putative target for full UTF-8, no more
\[u], sigh.
Cheers
Deri
ot;anything" in copy mode, I would cheer,
since synchronicity would be preserved. After your changes to \X it now
provides curated content to grout, removing "nodes" from the string (except \
[u]), it would be nice to have an in-band "anything" escape.
Cheers
Deri
andard import of images. Typically where you want the
rendered image to be a precise size (i.e. fill to the edges of an A4 page),
ignoring the XY ratio. Also a way of importing an image tile to be used as a
pattern tile as a background to the page, or be used as a fill colour. Neither
purpose is finished.
Cheers
Deri
sort of
road vehicle!) is required, which would sit the image on the baseline as "ps:
import" and leave the Y position well alone!! I would appreciate guidance on
whether this is a good idea or not.
The reason why this behaviour has not been reported sooner is probably because
.PDFPIC includes a break after the image so the grout file includes new H and
V commands which reset the position for gropdf.
Cheers
Deri
fpic GNU-head-small.pdf -L 10p'\h'10p'
A GNU head \[gnu] image.
There may be an argument for adding "pdf: pdfpicup" to gropdf to render
upwards, for this type of situation where the image is intended to sit on the
baseline.
Cheers
Deri
e: transparent_dummy_node, diversion level: 0},
{type: kern_pair_node, diversion level: 0},
{type: glyph_node, character: "r", diversion level: 0},
{type: glyph_node, character: "l", diversion level: 0},
{type: glyph_node, character: "d", diversion level: 0}
x font 5 TR
f5
s1
V12000
H72000
md
DFd
tHelloW
H102860
torld
n12000 0
x trailer
V792000
x stop
Notice that the .output directive never made it to the node list, because it
has been actioned immediately. I hope this model helps you to better
understand how the device control commands work in groff.
Cheers
Deri
on as they are actioned, even if a partial line is being
constructed by groff.
Cheers
Deri
On Sunday, 15 December 2024 20:03:50 GMT G. Branden Robinson wrote:
> At 2024-12-15T16:22:59+0000, Deri wrote:
> > It looks like it is a regression (from 1.23.0) because if I remove the
> > "kludge" and change the GNU png to pdf (so it is compatible with
> > running
wrong in current. I also tested using 1.23.0
groff and run the output through current gropdf and the result was good.
I can not find anything in the NEWS file regarding a change to .char handling
and all the regression tests are passing, so I presume this is an unintended
change of behaviour.
Cheers
Deri
GNU-head-small.pdf
Description: Adobe PDF document
gperl manually
before groff as I don't think there is a flag for groff to call it for you.
Cheers
Deri
sh any partial line (line break) and one is not. It seems
wrong to make a change which would mean that any current document using ".ne"
would have to change to "'ne" to retain the current behaviour, particularly
when it is simply a case of adding a .fl before the .ne to achieve the
behaviour onf prefers.
Cheers
Deri
On Sunday, 17 November 2024 22:17:08 GMT G. Branden Robinson wrote:
> Hi Deri,
>
> At 2024-11-17T20:35:34+0000, Deri wrote:
> > On Sunday, 17 November 2024 04:42:47 GMT G. Branden Robinson wrote:
> > > I have added 3 tickets to the release goals.
> > >
> >
On Sunday, 17 November 2024 04:42:47 GMT G. Branden Robinson wrote:
> At 2024-11-17T00:44:50+0000, Deri wrote:
> > On Saturday, 16 November 2024 15:34:36 GMT G. Branden Robinson wrote:
> > > (Even if the in-band singaling was your invention, I have found that in
> > &g
On Saturday, 16 November 2024 15:34:36 GMT G. Branden Robinson wrote:
> Hi Deri,
>
> At 2024-11-16T13:02:02+0000, Deri wrote:
> > On Thursday, 14 November 2024 17:44:55 GMT G. Branden Robinson wrote:
> > You did commit to adding relevent info from the attached pdf regardin
g filling this gap, or are you
expecting me to write something at extremely short notice?
Cheers
Deri
NewGropdf.pdf
Description: Adobe PDF document
On Saturday, 2 November 2024 17:29:14 GMT Bjarni Ingi Gislason wrote:
> My fix broke down when I used "gnu.xpm" after installing "perlmagick" (tip
> from Deri).
>
> Fixed "tmac/pdfpic.tmac" in my repository, which is now without a warning
> f
;splitpath") via
> package "File::Spec" (Perhaps you forgot to load the package?) at
> /home/bg/git/groff/build/pdfmom line 27.
>
> -.-
>
> The size of created files stays the same.
Hi Bjarni,
Thanks for the report, fixed in commit 357028ed.
Cheers
Deri
nning HEAD of groff
(otherwise you can only use .pdfs) AND have perlmagick (v6 or 7) installed.
Cheers
Deri
ng directory '/home/derij/groff-git/groff/build'
make: *** [Makefile:6521: all] Error 2
The message you quote comes from your perl, however, I altered the PSPIC line
in mixed_plckles.roff to:-
PDFPIC -I -\\n[.l]u ../../doc/gnu.xpm
And ran this command in the contrib/hdtbl directory:-
test-groff -Tpdf -petU -mhdtbl examples/mixed_pickles.roff > mixed_pickles.pdf
Output attached, no messages output, looks Ok.
Cheers
Deri
mixed_pickles.pdf
Description: Adobe PDF document
st-troff). Hanging my head in shame!
Cheers
Deri
You should see a warning for each different obsolete font used,
rather than repeated message each time the font is used.
Anyway, you did ask, I'm sure you could do it better.
Cheers
Deri
en though there would be 1000+ warnings, it would achieve your
desire to drop support for the ancient font names but in a way which did not
affect rendering of the document in the interim.
Cheers
Deri
On Friday, 4 October 2024 20:21:13 BST G. Branden Robinson wrote:
> Hi Deri,
>
Hi Branden,
> At 2024-10-04T16:41:19+0100, Deri wrote:
> >
> > The fix in June did fix the original problem with page breaks in the
> > FBDL document that Michał was working on, but does n
On Friday, 4 October 2024 02:53:02 BST G. Branden Robinson wrote:
> Hi Deri,
>
Hi Branden,
> > The extra blank pages and the erroneous bookmarks are probably linked
> > and seem to be caused by commit
> > 5808f3f4dd8f39341170597363a6aaf7acf921fd, which was a fix to a
&
On Thursday, 3 October 2024 22:18:23 BST G. Branden Robinson wrote:
> At 2024-10-03T20:58:34+0100, Deri wrote:
> > An example is the utp document which a lot of people on this list put
> > together. Neither the original 1.0, producing postscript, nor 1.1,
> > producing a pd
as Times-Roman, pdf bookmarks jumping
to the wrong page, input line numbers appearing in the output (1.0 postscript
only - also affects 1.23.0 - Ok in 1.22.4).
Are all of these changes in behaviour really fixes to bugs in groff?
Cheers
Deri
On Thursday, 5 September 2024 21:33:44 BST Peter Schaffter wrote:
> On Thu, Sep 05, 2024, Deri wrote:
> > I believe the mom macro set has an UNDERLINE macro see:-
> >
> > https://www.schaffter.ca/mom/momdoc/goodies.html#underline
> >
> > Note that it can only be
gt;
> Any tips or alternative solutions?
>
> Thanks and have a great day!
Hi Philippe,
I believe the mom macro set has an UNDERLINE macro see:-
https://www.schaffter.ca/mom/momdoc/goodies.html#underline
Note that it can only be used by -Tps (not -Tpdf). I think it is using a
postscript snippet from Tadziu.
Cheers
Deri
On Thursday, 5 September 2024 04:15:44 BST G. Branden Robinson wrote:
> [fair warning: _gigantic_ message, 5.7k words]
> Hi Deri & Dave,
Hi Branden,
> I'll quote Dave first since his message was brief and permits me to make
> a concession early.
>
> At 2024-09-04
On Sunday, 1 September 2024 06:09:17 BST G. Branden Robinson wrote:
> Hi Deri,
>
> At 2024-08-31T17:07:28+0100, Deri wrote:
> > On Saturday, 31 August 2024 00:07:57 BST G. Branden Robinson wrote:
> [fixing two of my own typos and one wordo in the following]
>
> >
st like you I would like to avoid "round-tripping", utf16 (preconv) ->
decomposed (troff) -> utf16 (gropdf). This does not currently affect grops
which does not support anything beyond 8bit ascii. Do you agree it makes more
sense for \X to pass \[u012F] rather than \[u0069_0328]?
Cheers
Deri
On Friday, 23 August 2024 01:32:39 BST Deri wrote:
> The
> difference is that version 7 returns this layer as all 255, and version 6.9
> returns it as all zeroes. Which means that although the png is embedded you
> still can't see it because the whole image is transparent!
>
e it because the whole image is transparent!
My investigation continues.
Cheers
Deri
On Thursday, 22 August 2024 15:24:17 BST Deri wrote:
> Hi Peter,
I have just discovered that debian have at last (yesterday!) got version 7 of
ImageMagick, but it is currently in the "experimental" repository:-
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929825#46
I'd
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
it, I love her.)), it is now 17:45 and I'm starting to get
excited this is my last monster typing marathon, and 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
ill be 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
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
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
be required for multi-page
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 -T
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 hotspots a
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
Seems to work, in this instance, but perhaps there is a better way.
Cheers
Deri
3. The opposite problem 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
ollow to make it happen.
> >
> >
> > 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),
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
>
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]
> ..
>
> ...and
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?
> > &
sage to device control
commands" shows you understand the 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
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 the greek
(computer/monospaced)
> > > 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
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.
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 file
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
$curoutlevno--;
}
}
}
Cheers
Deri
t way to do this is with the install-font.sh script from Peter
Schaffter's website
for mom. [1].
The attached pdf illustrates a suitably amended version of your unicode.ms file
run
through groff. Note that I am using the git version built from the
deri-gropdf-ng branch,
but this should wo
e good examples
of what can be achieved with groff. Particularly Peter's mom examples which
come with the source code as well.
Cheers
Deri
On Monday, 18 December 2023 21:49:55 GMT Oliver Corff wrote:
> Hi Deri,
>
> Here we go. In the meantime I came to the conclusion that the dpdviewer
> is at fault, or rather the viewer's setup; I forwarded the pdf to a
> different system, and there everything was visible as
und--in a groff build from source on Fedora 39.
>
> So something would appear to be amiss. I'm hoping Deri can help us
> figure it out.
Hi Branden,
Happy to. The two issues are probably not linked, one is a problem with the
configure script not finding the URW font directory, an
tion the problem.
This would appear to be an issue with the part of configure which looks for
the URW fonts, Branden is the expert.
Cheers
Deri
ith the
command:-
groff -T pdf -ms -P-d -k
And attach the download file from the font/devpdf directory along with an "ls"
of that directory.
This will let me start to see what is going on.
You can either send them to me or attach it to a savannah bug report.
Cheers
Deri
On Sunday, 17 December 2023 20:53:52 GMT G. Branden Robinson wrote:
> Hi Deri,
>
> At 2023-12-10T18:43:42+0000, Deri wrote:
> > On Saturday, 9 December 2023 19:25:27 GMT G. Branden Robinson wrote:
> > > When a line of output is "finished" and sent to the device
&
ours use normal groff colour definitions. I'm not too sure why
most of the colours are done as postscript commands, but this sort of
postscript used to be the only way to get colours from groff, before Werner
added the colour commands, so it may be old code.
Cheers
Deri
On Monday, 11 December 2023 14:30:04 GMT Alexis wrote:
> Hi Deri,
>
> thank you for addressing this so quickly. Unfortunately I have yet to
> succeed in building groff from the deri-gropdf-ng branch using nixpgs,
> yet am happy to report back once I do.
>
>
> Best
>
On Sunday, 10 December 2023 15:59:16 GMT Alexis wrote:
> Hi Deri,
>
> thank you for the swift and helpful response.
>
> I'm happy to confirm that using -P-pa4l works for me too
> and am glad that there is more parity between the groff
> and device paper format since
further output,
other than "x trailer", is output. This is an example of troff output:-
x T pdf
x res 72000 1 1
x init
p1
x font 5 TR
f5
s1
V12000
H72000
mr 0 0 0
DFd
tline
n12000 0
V792000
H72000
tline
n12000 0
V792000
p2
x trailer
V792000
x stop
The V792000 and p2 are unnecessary unless there is further output.
Cheers
Deri
"box rad 0.2 ht 2 wid 2"
.PE
EOF
And with the yet to be merged changes (from the deri-gropdf-ng branch)
so does:-
cat < box_rad_devpdf.pdf
.PS
box rad 0.2 ht 2 wid 2 "\*[.T]" "box rad 0.2 ht 2 wid 2"
.PE
EOF
I will investigate the problem with -P-l.
Cheers
Deri
where near the top of hdtbl-issue.ms. The man page says:-
A table which does not fit on a partially filled page is printed
automatically on
the top of the next page if you append the little utility macro t*hm
to the page
header macro of your document’s main macro package. For example, say
.am pg@top
. t*hm
..
if you use the ms macro package.
Cheers
Deri
On Wednesday, 22 November 2023 14:58:56 GMT Alejandro Colomar wrote:
> Hi Deri,
>
> I've optimized from 18.5 s down to 16.3 s the script, by splitting the
> pipeline with this wrapper (and slightly reducing the perl script to
> just print the pages to stdout). BTW, now it
On Wednesday, 22 November 2023 14:58:56 GMT Alejandro Colomar wrote:
> Hi Deri,
>
> I've optimized from 18.5 s down to 16.3 s the script, by splitting the
> pipeline with this wrapper (and slightly reducing the perl script to
> just print the pages to stdout). BTW, now it
above pdf files, to see how
they were constructed.
As regarding identifying if you have made a mistake calling a macro, you could
try calling groff with the -ww flag to enable all warnings.
Cheers
Deri
Laplace.pdf
The result is attached.
If you prefer I can send you the resulting fonts, plus instructions.
Cheers
Deri
Laplace.pdf
Description: Adobe PDF document
On Tuesday, 7 November 2023 19:48:51 GMT G. Branden Robinson wrote:
> Hi Deri,
>
> At 2023-11-07T17:33:06+0000, Deri wrote:
> > On Monday, 6 November 2023 17:47:13 GMT G. Branden Robinson wrote:
> > > Slowly. I landed two small changes this weekend, but they're no
Hi Branden,
I was wondering how the merging of the new gropdf branch was going (I think
you very kindly offered to help merging with master). Recently you have
written on the list:-
"Also, when Deri James's gropdf improvements are merged for groff 1.24, the
file size of groff-man
propriate).
>
> Sorry if I sound harsh, but this change already cost me hours of work
> to fix.
>
> I am on the brink of getting the 1.22 source code and install that over
> the system package of 1.23, which just brings me hate.
I have added this line to the man.local file (/usr/share/groff/site_tmac on my
system) to
restore the asciitilde behaviour.
.tr ~\(ti
Cheers
Deri
different. It can use iconv and
uchardet for this guessing. What does preconv -v tell you, mine says:-
[derij@pip Chats (deri-gropdf-ng)]$ preconv -v
GNU preconv (groff) version 1.23.0.16-a53f5-dirty with iconv support and with
uchardet support
It is the support information which is important, y
.)
A slight change and you can colour the margins with pure troff so it works for
both postscript and pdf:-
groff -Tpdf -P-pa4 -P-e margins.trf > margins.pdf
Cheers
Deri
.\"
.\"
.pl 29.7c
Follow-up Comment #4, bug #64576 (project groff):
Just completed a fix to allow any input to be used as a valid *roff
identifier. This allows all UTF-8 to be used as well. So both "Known Issues"
in my NewGropdf document are now ticked off. :-)
On Saturday, 12 August 2023 07:35:20 BST G. Branden Robinson wrote:
> Hi Deri,
>
> At 2023-06-23T22:40:42+0100, Deri wrote:
> > On Friday, 23 June 2023 19:17:58 BST Robin Haberkorn wrote:
> > > So it seems that the main problem really lies in grops and/or gropdf
> &g
On Saturday, 5 August 2023 15:55:20 BST G. Branden Robinson wrote:
> Deri, I'm happy to apply a corrective documentation change to gropdf(1).
> Is that cool with you? Let me know.
>
> I think it'd be a good idea to explicitly note the order reversal of the
> dimensions
On Saturday, 5 August 2023 15:36:31 BST Alexis wrote:
> Thank you for the helpful context, Deri, much appreciated. I checked
> the sources thoroughly, in order to have a good reasoning, but missed
> to read the grodvi sources :/
>
> Following the same order, i.e. width,height, to
ince this is an older API and I wanted to allow
the same source to run on either dvi or pdf [1]. So it is the documentation in
the gropdf man page which is wrong. I agree it is a little crazy to reverse
the normal groff ordering but I was retaining compatibility with grodvi. I
will fix the man pag
On Friday, 4 August 2023 17:58:13 BST G. Branden Robinson wrote:
> Read Deri's first--it's more interesting. :) Mine is about as
> hair-splitting as any reader of this mailing list would expect.
Hi Branden,
Oh, I don't know, I think yours is better, in a quantative sense. :-)
Cheers
Der
olors for the ps device are also available for
> the pdf device even though pdf.tmac does not define colors.
pdf.tmac includes ps.tmac so colours are defined.
Cheers
Deri
> Hopefully this proves useful to others.
>
>
> Best
> Alexis
https://ubuntu.com/security/CVE-2018-16802
Which also makes it clear that it is crafted postscript which triggered the
bug.
Cheers
Deri
tmp.pdf, the image is not inserted into the pdf. There is only box with the
> image file path (which is correct).
>
> Best regards,
> Michał Kruszewski
>
> Sent with [Proton Mail](https://proton.me/) secure email.
Hi Michal,
Grops supports eps images, for gropdf you need to convert your png to a pdf.
Cheers
Deri
df and passing it to a viewer.
Cheers
Deri
hieve similar in one run by using the \X'papersize='
command within your troff file, which would be useful if you have a wide table
you want presented in landscape, but you have to adjust page length/width
yourself to notify the troff formatter of the changed dimensions.
Cheers
Deri
On Sunday, 9 July 2023 19:26:36 BST Colin Watson wrote:
> On Sun, Jul 09, 2023 at 07:13:54PM +0100, Deri wrote:
> > It looks Ok, not tested. I'm happy for you to apply.
>
> Thanks.
>
> > Once gropdf moves to the font subsetting version it will cause a
> > pro
1 - 100 of 450 matches
Mail list logo
