Re: PDFPIC misbehaves if called two times in a row

On Sunday, 31 July 2022 19:59:44 BST joerg van den hoff wrote: > On 31.07.22 18:57, Deri wrote: > > On Sunday, 31 July 2022 17:34:19 BST joerg van den hoff wrote: > >> hi deri, > >> > >> thank you for looking into this! > >> > >> question

Re: PDFPIC misbehaves if called two times in a row

On Sunday, 31 July 2022 17:34:19 BST joerg van den hoff wrote: > hi deri, > > thank you for looking into this! > > question: the pdfpic.tmac you've send is supposed to work if I include it at > top of my document (e.g. the fragment tt.trf) so that it overrules the > pd

Re: PDFPIC misbehaves if called two times in a row

... > > best, > joerg Hi Joerg, I think the pdf output works Ok with the current version in git, but the git version had a different problem with the postscript output. I think I have found the fix please can you test with this version, which I will commit soon. Cheer

[groff] 01/01: [gropdf]: slanting lowercase greek characters.

deri pushed a commit to branch master in repository groff. commit d58625a25f2c1732b863d64a259d04a4e61c829d Author: Deri James AuthorDate: Thu Jul 28 13:48:53 2022 +0100 [gropdf]: slanting lowercase greek characters. * tmac/pdf.tmac: to prevent gropdf from slanting all lowercase

Re: eqn formatting issues with grops and gropdf

roman font without greek alphabet, the equation will use the S font and lowercase is slanted. Cheers Deri

Re: eqn formatting issues with grops and gropdf

rather than gropdf.pl. I have attached a new version, please can you test. The change should mean that if the current font contains the greek characters, they are left alone but if groff has to source from a special font, i.e. S, it will apply the slant. Cheers Deri .ig pdf.tmac Copyrig

eqn... the first missing email

a space between the greek glyphs when using the SS font. When eqn runs it is inserting \/ and \, around each of these greek characters which cause italic correction to be applied to each character. If you want slanted glyphs after you have prevented grops from using the SS font you could copy the relevant part from pdf.tmac to your own file. Cheers Deri

Re: eqn formatting issues with grops and gropdf

On Tuesday, 26 July 2022 17:19:04 BST Deri wrote: > On Tuesday, 26 July 2022 09:00:25 BST joerg van den hoff wrote: > > me again with an update/correction to the previous description of the > > issue > > (the described problem remains, though): > > > > 1. &g

[bug #62816] rename the \& escape...again

Follow-up Comment #2, bug #62816 (project groff): Found another use:- .mc to assign a margin character skips blank lines. \& prevents this happening. ___ Reply to this item at:

Re: eqn formatting issues with grops and gropdf

On Tuesday, 26 July 2022 09:00:25 BST joerg van den hoff wrote: > me again with an update/correction to the previous description of the issue > (the described problem remains, though): > > 1. > regarding the symobl fonts used by grops and gropdf I previously stated the > former were using SS

Re: "Writing my PhD using groff"

pertise from PS/PDF gurus is welcome. Hi Branden, The best of both worlds is to produce pdf with groff (hack your script to add -Tpdf -P-e) and run the resultant pdf through ps2pdf.This will ensure all fonts are embedded and that they have been subsetted to save space. Cheers Deri

Re: "Writing my PhD using groff"

tput processor is gropdf. Cheers Deri [1] the definition is in the latest version of the man page, I missed documenting the command in earlier versions.

Re: How groff should locate AFM files for gropdf (was: build system: devpdf/download regression)

On Sunday, 17 July 2022 05:34:27 BST G. Branden Robinson wrote: > Hi Deri, > At 2022-07-16T15:56:28+0100, Deri wrote: > > My understanding is that the selection of paths to search is appended > > to the value of the --with-urw-fonts-dir config variable (if any). > >

Re: tbl(1) minor issues

On Saturday, 23 July 2022 14:47:55 BST G. Branden Robinson wrote: > I > hope to hear back from Deri regarding my recent questions about URW font > detection and foundry-management gymnastics. Sorry, Branden, I must have missed the question. Please point me to it. Cheers Deri

Re: build system: devpdf/download regression

On Saturday, 16 July 2022 12:48:50 BST G. Branden Robinson wrote: > [1] I think this is because it began life as, or Deri had hopes for it > to be, an installable tool. Failing to add gropdf support for some > crazy font that will be used only by the document you're about to &g

Re: build system: devpdf/download regression

On Saturday, 16 July 2022 12:02:29 BST G. Branden Robinson wrote: > Hi Ingo & Deri, > > At 2022-06-26T17:16:44+0100, Deri wrote: > > > In general, i would recommend differentiating configuration variables > > > by functionality. For example, if all you need is one

Re: Using emoji with PDF device

On Thursday, 14 July 2022 18:23:55 BST Andrea D'Amore wrote: > Side question: why `.trf` extension? Its what I call files intended for troff. Cheers Deri

[bug #59545] MORE.STUFF: Add material

Follow-up Comment #7, bug #59545 (project groff): I had forgotten about this! I can confirm all the items found by Peter have been fixed and I will be refreshing the download file soon. I do have a question about what we should do with busgrap, don't answer that, and don't change a single letter

[bug #59545] MORE.STUFF: Add material

Follow-up Comment #5, bug #59545 (project groff): If I remember correctly, I included Ralph's patch. I also added .pdfbackground as part of testing the new gropdf feature. What I need is response from testers, I am pretty sure there are probably lots of bugs in the code, also, I was hoping

Re: PDF reader for Groff output

about the NimbusRoman fonts. So if you use the centos packages to install the fonts, any program which uses fontconfig to locate fonts will be aware of their presence. Gropdf nor grops use fontconfig to find fonts, which is why you can use the -- with-urw-fonts-dir flag for configure. Cheers Deri > Stay safe - Damian

Re: Problem building latest git source

den, Yes, it's a bug introduced when I switched search order to file within path. Please test with fix just posted to git. Cheers Deri

Re: Problem building latest git source

den, Yes, it's a bug introduced when I switched search order to file within path. Please test with fix just posted to git. Cheers Deri

[groff] 01/01: [devpdf]: Restore original path

deri pushed a commit to branch master in repository groff. commit 272aaadb23f3ed44873c6acaaf42f41cdd9a11ba Author: Deri James AuthorDate: Fri Jul 8 14:16:55 2022 +0100 [devpdf]: Restore original path * font/devpdf/util/BuildFoundries.pl: Some systems store .afm files

Re: Problem building latest git source

to open device description file 'DESC' it has come from gropdf. It will help to know which message you are seeing. Cheers Deri

Re: Problem building latest git source

to open device description file 'DESC' it has come from gropdf. It will help to know which message you are seeing. Cheers Deri

Re: Problem building latest git source

d gropdf man pages have examples of all fonts they all need to be specified correctly in the download file for it to succeed. Cheers Deri

Re: Problem building latest git source

> re-run 'configure'. It might help to 'make distclean' first...but I > wouldn't be surprised if you hit the same afmtodit problem I did. I'll > look at BuildFoundries and see if I can spot an error, but Deri's eyes > will be better than mine here. > > In the below, you mi

Re: Problem building latest git source

> re-run 'configure'. It might help to 'make distclean' first...but I > wouldn't be surprised if you hit the same afmtodit problem I did. I'll > look at BuildFoundries and see if I can spot an error, but Deri's eyes > will be better than mine here. > > In the below, you mi

Re: build system: devpdf/download regression

On Sunday, 26 June 2022 13:11:12 BST Ingo Schwarze wrote: > Hi Deri, > > thanks for your extensive explanation. > [...] > > In the same way that the choice of URW directory is passed into > > Foundry.in, although I would prefer separate variables, one for >

Re: pic diagram on arbitrarily large page

t vertically and horizontally to an arbitrary extent. As it is, I have > already run out of space, and new boxes do not appear on the chart (or > appear in the wrong place). > > R. This seems to work:- .sp 2i .PS 18i 5i for j=1 to 18 do ! ellipse "Deri"; arrow; ! .PE And run

Re: build system: devpdf/download regression

an use these fonts, too, couldn't we? > That would seeem less selfish to me on the part of the gs(1) > program, wouldn't it? If the results of gs -h include the text %rom% I believe this means some files have been baked in, but you should talk to the ghostscript packager. One wrinkle, if you go with just one copy of the fonts and use symlinks is that ghostscript uses different names for the fonts than the old ms-dos names. Cheers Deri > Yours, > > Ingo

Re: build system: devpdf/download regression

On Wednesday, 22 June 2022 22:29:29 BST G. Branden Robinson wrote: > Hi Deri, > > At 2022-06-22T21:30:25+0100, Deri wrote: > > I think I have sussed what might be happening. In the port build the > > standard fonts get built because of the addition of > > /usr/lo

Re: build system: devpdf/download regression

On Wednesday, 22 June 2022 14:48:24 BST Ingo Schwarze wrote: > Hello Deri, > > Deri wrote on Wed, Jun 22, 2022 at 01:07:34AM +0100: > > I've tracked down the problem. The configure flag --with-urw-fonts-dir > > was not being used when searching for fonts for the default f

Re: build system: devpdf/download regression

esults. Sometimes they subtly change the names of the fonts which ghostscript uses and I have to add the alternative names. If you can't find the fonts it can mean they have baked the fonts in what they call %rom% so they are not available as real files. Cheers Deri

[groff] 01/01: [gropdf]: Add more search paths to Foundry file.

deri pushed a commit to branch master in repository groff. commit d55157d39ab4d01bccea276122a2f3a5b1e30452 Author: Deri James AuthorDate: Wed Jun 22 00:24:04 2022 +0100 [gropdf]: Add more search paths to Foundry file. * font/devpdf/Foundry.in: Use the directory specified

Re: build system: devpdf/download regression

ges. It would help me a lot if you could send me a captured log of your "make", especially if you can use the version of BuildFoundries I have just committed which should show the paths used for searching. Cheers Deri

[groff] 01/01: [gropdf]: Correct display of pathnames used.

deri pushed a commit to branch master in repository groff. commit ced9cd5984814f9701fd681b6c949d0708c2687c Author: Deri James AuthorDate: Tue Jun 21 16:38:39 2022 +0100 [gropdf]: Correct display of pathnames used. * font/devpdf/util/BuildFoundries.pl: Convert array to string

Re: build system: devpdf/download regression

On Tuesday, 21 June 2022 15:54:54 BST G. Branden Robinson wrote: > > +BuildFoundries: warning: line 75: > > +The path(s) used for searching: > > +ARRAY(0x23cef899970) > > Urp. The form of that output is certainly bogus. Did I break it in a > recent change? I'll check. Nope. That was me,

[groff] 01/01: [gropdf]: Fix to gropdf.

deri pushed a commit to branch master in repository groff. commit 52f725f019ba87575ba3affbae8e6733b2e6ff13 Author: Deri James AuthorDate: Tue Jun 21 10:54:05 2022 +0100 [gropdf]: Fix to gropdf. * src/devices/gropdf/gropdf.pl: If pdfbookmark was called within 5p of top of page

Re: Text editor with visual/mouse entry

accessible text > entry. I’m struggling to hunt down the name of the tool so was wondering if > anyone had a clue as to what it might be? > > Thanks, > Karthik Hi Karthik, I use a program called dasher (available for Mageia). urpmi dasher See:- http://www.inference.org.uk/dasher/ Cheers Deri

[bug #62640] groff command insists on a device postprocessor even if -Z or -X

Follow-up Comment #3, bug #62640 (project groff): It's too hot to think properly, sorry. I thought the problem was no DESC file for device cat (the quickness of the eye deceives the brain), and when I tried your test (without a directory font/devcat) I got "cannot load 'DESC' description file for

[bug #62640] groff command insists on a device postprocessor even if -Z

Follow-up Comment #1, bug #62640 (project groff): A valid postprocessor is required to provide the appropriate values from the DESC file. Without these values the resulting -Z output would be meaningless. The particular postprocessor for which the output is intended, is specified in the first

Re: install-font script (was: groff 1.23.0.rc2 readiness)

On Monday, 6 June 2022 19:08:23 BST Deri wrote: > As I suggested it would be helpful if you are able to run gs -h on a windows > box under cygwin and natively, the output would help us. I have now managed to run gs -h under a VM of windows 10 with latest ghostscript, and you are c

[groff] 01/01: [gropdf]: Changes to BuildFoundries.

deri pushed a commit to branch master in repository groff. commit 4ae4aeb6555f4f16c28fcb03eb1f56577826054c Author: Deri James AuthorDate: Fri Jun 10 21:13:24 2022 +0100 [gropdf]: Changes to BuildFoundries. * font/devpdf/util/BuildFoundries.pl: Collect search paths into an array

Re: zero-width space (was Re: How to print a literal '.' as the first character in a line?)

lar spaces to trigger end of sentence detection, they will be disappointed because they all prevent detection just the same as \&. You may want to mention its use in preventing groff recognising ligatures. Typing reff\ will prevent the fi ligature being used. Cheers Deri

Re: building without tex (was: zero-width space)

e tex2dvi available on my system, I would not be too despondent. Cheers Deri

Re: Zero Width Space (was Re: How to print a literal '.' as the first character in a line?)

| nroff You should see the text ".sp". Any escape with zero movement acts in this way, it is not special to \&. The difference is that \& is the shortest escape which causes no movement, so is useful for this purpose, but it is essentially a space which has no width. Cheers Deri

Re: [groff] 14/15: [font/devpdf]: Revise path component separation.

k whether gs -h uses alternative separators on other operating systems? Also, shouldn't foundry.in have some fiddling as well? Cheers Deri

Re: [groff] 14/15: [font/devpdf]: Revise path component separation.

k whether gs -h uses alternative separators on other operating systems? Also, shouldn't foundry.in have some fiddling as well? Cheers Deri ___ Groff-commit mailing list Groff-commit@gnu.org https://lists.gnu.org/mailman/listinfo/groff-commit

[bug #62572] [gropdf] would like complaint if embedding needed but download file useless

Follow-up Comment #3, bug #62572 (project groff): > > Gropdf could have a moan if the -e flag is present and the required font is not mentioned in the download file, > > Yes, this is exactly what I mean to request with this Savannah ticket. Is it something you feel good about doing? > If you

[bug #62551] [PATCH] doc/groff.texi: Fix content and style nits

Follow-up Comment #10, bug #62551 (project groff): Is it true that previously you didn't need a full TeX installation to build groff from git, it just did not build groff.pdf as part of the process. Now it seems the build borks very early on if tex2dvi is not found, so you have to have the

[bug #62572] [gropdf] would like complaint if embedding needed but download file useless

Follow-up Comment #1, bug #62572 (project groff): I'm not sure how to do this, it is quite permissable to have a blank download file, just as it is in grops. The file in grops lists those fonts which require to be embedded since they are not part of the 35 base fonts for postscript. In gropdf a

[bug #59933] Curly brackets displayed correctly in ps, but not in pdf

Follow-up Comment #4, bug #59933 (project groff): On Wednesday, 1 June 2022 13:25:51 BST Oliver wrote: > Hi Branden, > > thank you for the update! > > I checked, there is no directory type1/ under /usr/share/fonts. > > Then, I did a "locate a0100" and found the fonts in >

[bug #62346] [PATCH] [gropdf] B0-B6 sizes don't work as documented

Follow-up Comment #4, bug #62346 (project groff): The patch is fine, although it may become moot depending on what is decided in bug #62344. I'm pretty agnostic on the "best" solution, I'm quite happy to add code to gropdf to parse paper.tmac, if this considered to be the authoritive source.

[bug #62346] [PATCH] [gropdf] B0-B6 sizes don't work as documented

Follow-up Comment #2, bug #62346 (project groff): Copied from somewhere on the net!! ___ Reply to this item at: ___ Message sent via Savannah

Re: Drawing a pie chart

is the sort of thing you want, you can download the software here:- http://chuzzlewit.co.uk/busgrap-20181129.tgz Cheers Deri Introduction.pdf Description: Adobe PDF document

Re: delete the --with-doc option of the configure script

t; to fix that bug with this patch. > > Yes, those sounds like bugs too, and probably both my fault to boot. I believe ghostscript is not involved in making msboxes.pdf so should not depend on finding ghostscript. Cheers Deri

[bug #62294] [gropdf] can't reproduce the 'ydieresis' character

Update of bug #62294 (project groff): Status: In Progress => Fixed ___ Follow-up Comment #2: Fixed in commit 17b5fff1eece9161036e50017dc6ef387e8fad1b 2022-04-11 Deri Ja

[groff] 01/01: [gropdf]: fails to deal with 255th glyph in font.

deri pushed a commit to branch master in repository groff. commit 17b5fff1eece9161036e50017dc6ef387e8fad1b Author: Deri James AuthorDate: Mon Apr 11 23:32:50 2022 +0100 [gropdf]: fails to deal with 255th glyph in font. Savannah bug #62294 * src/devices/gropdf/gropdf.pl

[bug #62294] [gropdf] can't reproduce the 'ydieresis' character

Update of bug #62294 (project groff): Status:None => In Progress Assigned to:None => deri ___ Follow-up Comment #1: Confirmed

Re: Proposal: drop devps "oldfonts" support

be already installed on a postscript printer) or the extended glyphs available in current URW fonts. If you are using the extended glyphs then the font needs to be embedded in the postscript or pdf file, I believe. Cheers Deri

[bug #61908] [gropdf] rotated text from pic(1) not correct in landscape orientation

Follow-up Comment #4, bug #61908 (project groff): I meant this one! 1307a645ca75217f1f287dffe3f9afb8f505a64d ___ Reply to this item at: ___ Message

[bug #61908] [gropdf] rotated text from pic(1) not correct in landscape orientation

Update of bug #61908 (project groff): Severity: 3 - Normal => 2 - Minor Status: In Progress => Fixed ___ Follow-up Comment #2: Fixed in

Re: Resources for *roff internals and PDF generation

s those areas. All these "extensions" are facilitated using the \X escape for example, which allows you to send information directly to the output driver. The gropdf man page. This describes some more \X extensions which are understood solely by the gropdf device driver. Cheers Deri

Re: Multiline Subject as PDF metadata

On Monday, 31 January 2022 08:15:55 GMT Dave Kemper wrote: > On 1/28/22, Deri wrote: > > If you are using -T pdf you > > don't need to include -mpdfmark, this is documented in the gropdf man page > > and the pdfmark.pdf is referenced. > > True, but just barely.

Re: Multiline Subject as PDF metadata

On Friday, 28 January 2022 21:29:35 GMT Dave Kemper wrote: > As a side issue, it looks like the .pdfinfo macro mentioned in this > thread is un(der)documented. > > It's documented in the pdfmark documentation > (contrib/pdfmark/pdfmark.ms), but it seems to apply to any document > rendered with

[groff] 01/01: Allow multiline text in .pdfinfo

deri pushed a commit to branch master in repository groff. commit 392f88f843c51c59f6dfe6c3bdc4731cd738ddd7 Author: Deri James AuthorDate: Wed Jan 26 00:17:47 2022 + Allow multiline text in .pdfinfo * src/devices/gropdf/gropdf.pl: Use either 'n

Re: Multiline Subject as PDF metadata

$1)))eg; - if ($pdfmark=~m/(.+) \/DOCINFO\s*$/) + if ($pdfmark=~m/(.+) \/DOCINFO\s*$/s) { - my @xwds=split(' ',"<< $1 >>"); + my @xwds=split(/ /,"<< $1 >>"); my $docinfo=ParsePDFValue(\@xwds); foreach my $k (sort keys %{$docinfo}) I will soon be adding this patch to groff git. Cheers Deri

Re: Multiline Sucject as PDF metadata

r, the standard allows you to include your own custom keys as well. I tested this with this troff code:- .sp 1i .pdfinfo /Title PDFINFO Test .pdfinfo /Synopsis Here is a little more text Deri James It works, embedding the new field "Synopsis" in the dictionary. Unfortunately, okular, evince and

[groff] 02/02: [gropdf]: Fix Savannah #61908

deri pushed a commit to branch master in repository groff. commit 1307a645ca75217f1f287dffe3f9afb8f505a64d Author: Deri James AuthorDate: Mon Jan 24 14:39:55 2022 + [gropdf]: Fix Savannah #61908 * src/devices/gropdf/gropdf.pl: Adjust text position when given

[groff] 01/02: gropdf.pl: A fix to importing pdf versions > 1.4.

deri pushed a commit to branch master in repository groff. commit c5e1a36b43dcd434452161952a9e80741b4f997c Author: Deri James AuthorDate: Mon Jan 24 14:03:12 2022 + gropdf.pl: A fix to importing pdf versions > 1.4. --- src/devices/gropdf/gropdf.pl | 2 +- 1 file changed, 1 insert

[bug #61908] Problem with rotated text from pic.

URL: <https://savannah.gnu.org/bugs/?61908> Summary: Problem with rotated text from pic. Project: GNU troff Submitted by: deri Submitted on: Mon 24 Jan 2022 02:12:36 PM UTC Category: Device gropdf Se

[bug #61836] want a page resequencer for intermediate output

Follow-up Comment #1, bug #61836 (project groff): It seems I have neglected to document two \X'pdf: ’ calls in the gropdf man page, which may be useful here. They are pagename, which allows you to tag a page with a name, and switchtopage which continues output before/after a named page. So, for

[groff] 01/01: * src/devices/gropdf/gropdf.pl: Fixes to importing pdf versions > 1.4.

deri pushed a commit to branch master in repository groff. commit 9064999adde2250851d8b66205f8eccad6c502b9 Author: Deri James AuthorDate: Tue Nov 16 11:53:07 2021 + * src/devices/gropdf/gropdf.pl: Fixes to importing pdf versions > 1.4. --- ChangeLog

[bug #61407] [mom] Remove default error messages from mom-files.

Follow-up Comment #4, bug #61407 (project groff): I believe the transparent node message occurs when pdf.tmac calls .asciify in order to "clean" the text to use in the bookmark text, and it includes nodes which can't be converted back text. Last time I looked this message could not be suppressed

[bug #61276] [PATCH] .Ql macro in troff-mode does not put text in single quotes

Follow-up Comment #5, bug #61276 (project groff): I'm rather lucky, I don't need a costume to scare the kids! ___ Reply to this item at: ___ Message

[bug #55107] PDFPIC: .psbb: support extraction of MediaBox from pdf files

Follow-up Comment #13, bug #55107 (project groff): Keith, Sorry, you will have to help me here, if you want me to understand what you meant. > I am willing to pursue an extended lex/yacc implementation, (subject to Deri actually answering the question I've now asked twice, without a respo

[bug #55107] PDFPIC: .psbb: support extraction of MediaBox from pdf files

Follow-up Comment #11, bug #55107 (project groff): Am I correct in guessing that a bounding box/MediaBox extractor would have a lot of shared logic for PS and PDF? If so, one preprocessor could perform both tasks. I guess we could call it "grobb" or something, and assign a -B flag to it in

[bug #55107] PDFPIC: .psbb: support extraction of MediaBox from pdf files

Follow-up Comment #10, bug #55107 (project groff): Personally, I don't see a justification for implementing psbb as a preprocessor. I am willing to pursue an extended lex/yacc implementation, (subject to Deri actually answering the question I've now asked twice, without a response: should

[bug #55107] PDFPIC: .psbb: support extraction of MediaBox from pdf files

Follow-up Comment #3, bug #55107 (project groff): This was my option (D) in this email (for PDFPIC, but also applies to .psbb):- https://savannah.gnu.org/bugs/?55107 ___ Reply to this item at:

Re: Portability to Mac OS X (was: Sed failure in contrib/sboxes on MacOS)

the different indexes. You may need to click on the button at the top left followed by the second button in the row of buttons which appear after you have clicked the top left. Cheers Deri

Re: Portability to Mac OS X (was: Sed failure in contrib/sboxes on MacOS)

Is produced entirely by groff and has a full clickable index. Cheers Deri

[bug #61386] [man] TH 'extra2' argument can overrun center footer

Update of bug #61386 (project groff): Status: Fixed => In Progress Open/Closed: Closed => Open Planned Release: 1.23.0 => None

[bug #61276] [PATCH] .Ql macro in troff-mode does not put text in single quotes

Follow-up Comment #1, bug #61276 (project groff): The groff_mdoc man page says:- .Ql The quoted literal macro behaves differently in troff and nroff mode. If formatted with nroff(,) a quoted literal is always quoted. If formatted with troff, an item is only quoted if the width of the item is

Re: Make pdfbackground less noisy

On Tuesday, 19 October 2021 17:16:32 BST Peter Schaffter wrote: > Deri -- > > Is there a way to suppress the diagnostics pdfbackground spits out? > mom files processed with pdfmom are already saddled with pointless > "can't transparently output node at top level" messag

Re: Problems with .PDFPIC caused by pdfinfo

On Tuesday, 12 October 2021 11:49:23 BST Keith Marshall wrote: > Ref: https://savannah.gnu.org/bugs/index.php?55107 > > On 01/10/2021 01:10, Deri wrote: > > I did try to help Keith with this previously, but I was mildly "told > > off" (on list) for sending my help o

Re: [groff] 07/09: [sboxes]: Add license to sboxes.am.

; 1 file changed, 24 insertions(+), 4 deletions(-) > > diff --git a/contrib/sboxes/sboxes.am b/contrib/sboxes/sboxes.am > index 47c916c..fc9be14 100644 > --- a/contrib/sboxes/sboxes.am > +++ b/contrib/sboxes/sboxes.am > @@ -1,3 +1,22 @@ > +# Copyright (C) 2021 Free Softwar

Re: [groff] 07/09: [sboxes]: Add license to sboxes.am.

; 1 file changed, 24 insertions(+), 4 deletions(-) > > diff --git a/contrib/sboxes/sboxes.am b/contrib/sboxes/sboxes.am > index 47c916c..fc9be14 100644 > --- a/contrib/sboxes/sboxes.am > +++ b/contrib/sboxes/sboxes.am > @@ -1,3 +1,22 @@ > +# Copyright (C) 2021 Free Softwar

[groff] 01/01: Handle pdfs > v1.4 loaded by \X'pdf: pdfpic.

deri pushed a commit to branch master in repository groff. commit 7a5d3ee0974568265901edff398dc20466df2ab5 Author: Deri James AuthorDate: Sun Oct 10 19:34:32 2021 +0100 Handle pdfs > v1.4 loaded by \X'pdf: pdfpic. * src/devices/gropdf/gropdf.pl: Improve loading of pdfs ab

[groff] 01/01: Add new background boxes to gropdf.

deri pushed a commit to branch master in repository groff. commit fedbf6ff9d3b84320b88c3a0ec8c951d6c07623a Author: Deri James AuthorDate: Sun Oct 10 14:39:24 2021 +0100 Add new background boxes to gropdf. * src/devices/gropdf/gropdf.pl: New \X'pdf background' command. * tmac

[bug #61302] Build errors

Follow-up Comment #7, bug #61302 (project groff): Well the psselect fix was accepted upstream very quickly. https://github.com/rrthomas/psutils/commit/77c2ec947dd5c6525d313f4065533488fa345f10 ___ Reply to this item at:

[bug #61302] Build errors

Follow-up Comment #6, bug #61302 (project groff): Hi Branden, I was confused in thinking just having libuchardet available would be sufficient for groff to use it, you are correct, I needed to install the devel package as well. Maybe the message about uchardet could mention it requires the devel

[bug #61302] Build errors

Follow-up Comment #5, bug #61302 (project groff): Hi Branden, I have diagnosed the problem with the perl version of psselect and reported it upstream. https://github.com/rrthomas/psutils/issues/38 While eventually this will fix the problem, I'm not sure how long it will take to work through.

[bug #61302] Build errors

Follow-up Comment #2, bug #61302 (project groff): GROFFdoc/pic.html [2] [1] Wrote 1 pages pnmcrop: The image is entirely background; there is nothing to crop. This is bad news. I don't get these. Something is going wrong in/around grohtml. I expect your copy of the HTML

[bug #61302] Build errors

URL: <https://savannah.gnu.org/bugs/?61302> Summary: Build errors Project: GNU troff Submitted by: deri Submitted on: Wed 06 Oct 2021 10:35:06 PM UTC Category: Core Severity: 3 - Normal

Re: Pushing a mom test fix

e, you will see the separate pages. So the actual number of pages is correct, a slide can be more than one page, depending on the number of transitions. Cheers Deri

Re: Problems with .PDFPIC caused by pdfinfo

On Monday, 20 September 2021 20:39:49 BST Keith Marshall wrote: > On 20/09/2021 19:22, Dave Kemper wrote: > > Hi Heinz-Jürgen, > > > > Thanks for debugging and submitting a fix for this problem! > > Except that it's not really the most appropriate solution; that was > proposed four years ago...

[bug #61180] BuildFoundries: Some fonts are not found with package ghostscript 3.54.0

Update of bug #61180 (project groff): Status:None => Invalid Open/Closed:Open => Closed ___ Reply to this item at:

[bug #61180] BuildFoundries: Some fonts are not found with package ghostscript 3.54.0

Follow-up Comment #3, bug #61180 (project groff): In which directory did you find these fonts, is it one of the directories mentioned at the bottom your original comment? Please could you also post the result of running "gs -h". ___

[bug #61180] BuildFoundries: Some fonts are not found with package ghostscript 3.54.0

Follow-up Comment #1, bug #61180 (project groff): Please can you do a listing of the directory containing the fonts in ghostscript 9.54. This is the equivalent listing for 9.53.3:- [derij@pip ~]$ ls /usr/share/ghostscript/9.53.3/Resource/Font/ C059-BdIta NimbusRoman-Regular

<    1   2   3   4   5   6   7   8   >