Re: (A possible) way to change the background color of pdf

g0.html a way of setting the paper colour in pdf files is described. Currently you need to checkout the gropdf- boxes branch of the git repository to use it. Cheers Deri

[bug #60707] Request predictable PostScript output

Follow-up Comment #1, bug #60707 (project groff): This wish probably needs renaming since it is clear from the information in comment #1 that the problem is not with grops which produces the postscript but with groff which produces the intermediate file which grops reads.

[bug #60655] want option for output drivers to suppress comments

Follow-up Comment #12, bug #60655 (project groff): Hi Dave, I don't see much fragility in what you are using now, the postscript language "build artifacts" are unlikely to change in any meaningful way which will stop your current workflow from continuing to work. Perhaps a general user who has

[bug #60655] want option for output drivers to suppress comments

Follow-up Comment #10, bug #60655 (project groff): You don't mention whether you found my suggestion for grepping the groff intermediate output produced by -Z was helpful or not. After all this is the input read by grops and you are not testing whether postscript has changed, but whether your

[bug #60655] want option for output drivers to suppress comments

Follow-up Comment #8, bug #60655 (project groff): One way of checking whether your change to roff code will alter the output is to diff the -Z output of both versions. This will easily show what page the change occurs on so you can use your slow method on just the page identified by the -Z diff.

Re: Auto-resize paper size during document run?

=..." command (see man gropdf) which allows you to change the paper size within the document. So individual pages within a document can have different sizes, the command affects the next page added to the document. If you use MOM I believe you can use the PAPERSIZE command. Cheers Deri

[bug #60655] want option for output drivers to suppress comments

Follow-up Comment #6, bug #60655 (project groff): My question is why do you want to suppress CreationDate, since this previously came up about reproducible builds and a solution was found. I don't see a need for a general user needing to do this, so why a flag?

Re: How to build groff (was: Install hiccups with groff 1.23.0 tarball)

On Sunday, 23 May 2021 09:27:13 BST G. Branden Robinson wrote: > Yes. The problem here is that you're neither bootstrapping _from a Git > repository_, nor from a distribution tarball. A snapshot archive is > neither fish nor fowl and apparently we have no documentation > instructing people how

[bug #60655] want option for output drivers to suppress comments

Follow-up Comment #4, bug #60655 (project groff): There is already a method for preventing "build artifacts" in grops and gropdf, what more would this add? ___ Reply to this item at:

[bug #60655] want option for output drivers to suppress comments

Follow-up Comment #3, bug #60655 (project groff): You have not mentioned why you want to suppress CreationDate nor what are the other related comments. ___ Reply to this item at:

Re: Not predefined Extended Latin character needed, interesting solution found

bed the font a little more complex (U- fonts are always downloaded). There are plenty of people with far more knowledge about these things than I so please comment on whether I have this correctly, and what would be best for our users. Cheers Deri

Re: Not predefined Extended Latin character needed, interesting solution found

On Tuesday, 18 May 2021 21:51:09 BST Oliver Corff wrote: > Hi Deri, > > I just attempted to follow your advice and compile groff from scratch. I > downloaded 1.22.4 and ran ./configure. > > I am a bit confused because ./configure warns me that I do not have URW > fonts, but

Re: Not predefined Extended Latin character needed, interesting solution found

On Monday, 17 May 2021 17:58:26 BST Oliver Corff wrote: > Hi Deri, > > On 17/05/2021 17:00, Deri wrote: > > printf '.ft U-TR\n\xc4\x8cSSR' | groff -kT pdf | okular - > > on my installation (groff 1.22.4) there is no U-TR font out of the box, > and thus I only get these

Re: Not predefined Extended Latin character needed, interesting solution found

On Monday, 17 May 2021 14:47:02 BST Oliver Corff wrote: > Hi Ingo, > > that's interesting. When producing for a UTF8 target, your observation > is correct, but for PDF groff does not seem to function as naively assumed. > Groff needs to know you have a font which includes a Ccaron glyph, so

Re: [bug #60604] m4/groff.m4: GROFF_URW_FONTS_CHECK: stale URL

On Sunday, 16 May 2021 02:37:26 BST G. Branden Robinson wrote: > One will also likely get the squawkage discussed in this ticket. > > > configure: > No URW fonts in Type 1/PFB format were found on your system; URW font > generation for groff's 'gropdf' output driver will not work properly. >

[bug #60604] m4/groff.m4: GROFF_URW_FONTS_CHECK: stale URL

Follow-up Comment #4, bug #60604 (project groff): Is there a reason why there is separate logic in the configure script from that used in BuildFoundries.pl? In commit f61c6ca5b84b488cbd324f2d23285fff1d807f04 a facility to do a dry run search was added to BuildFoundries.pl, which could be used.

New extension to gropdf

ever to improve it. Cheers Deri groff-list-20210402.tgz Description: application/compressed-tar msboxes.pdf Description: Adobe PDF document

[groff] 01/01: Changes to the ghostscript fontnames (9.53.3).

deri pushed a commit to branch master in repository groff. commit 56778b6dd3ba8d18105230dfe19fcfb6ae8fc5a3 Author: Deri James AuthorDate: Sat Mar 27 12:03:48 2021 + Changes to the ghostscript fontnames (9.53.3). * font/devpdf/Foundry.in: HI and HBI switch to using Italic

[bug #60061] Narrow scope of groff Texinfo manual

to have specified values for the "pictures" to render correctly. After the book has been generated, in order to generate it again, either do a 'make clean' or call make like this:- touch groff.texi; make ARGS='...' Deri James (file #51016)

[bug #60061] Narrow scope of groff Texinfo manual

Follow-up Comment #6, bug #60061 (project groff): Here's the build environment. Just untar and cd into texi2groff-beta and "make". There are still many rough edges, there is a list of items not handled by the parser along with a count of how often they triggered, which is present after the

Re: Mangled pdf in Chrome browser?

On Saturday, 20 February 2021 16:42:09 GMT Peter Schaffter wrote: > A user contacted me off list saying that the example pdf file at > > https://www.schaffter.ca/mom/pdf/sample-formatted-article.pdf > > is rendering as garbage in the Chrome browser. I don't use Chrome. > Can someone check if

[bug #60061] Narrow scope of groff Texinfo manual

Follow-up Comment #4, bug #60061 (project groff): Trying with a tar file containing complete build. ___ Reply to this item at: ___ Message sent via

[bug #60061] Narrow scope of groff Texinfo manual

Follow-up Comment #3, bug #60061 (project groff): I'm trying to attach the pdf. If it fails please let me know if I can send it direct by email. ___ Reply to this item at:

[bug #60061] Narrow scope of groff Texinfo manual

Follow-up Comment #2, bug #60061 (project groff): I am not sure if you are aware of some work I did awhile ago around making groff produce the "groff book" rather than Tex This was a program which converted the texinfo file into a roff file which could be run through groff with the ms macro to

Re: source code of groff-and-mom.pdf

ouldn't have to be the complete code of > course, but may-be somthing like the first and last 10 pages or so. Thanks > a lot, > PanTau On my system it can be found at:- /usr/share/doc/groff-1.22.4/examples/mom/mom-pdf.mom You may have to adjust for your version of groff. Cheers Deri

Re: Large curly brackets in tbl

script:- ps2pdf -dEmbedAllFonts=true -dPDFSETTINGS=/prepress ESB.ps Or try:- groff -Tpdf -te -P-e ESB.tbl > ESB-g.pdf Which will create a pdf with all the fonts embedded. Cheers Deri

Re: Greeting card revisited: PS and PDF discrepancies

n(t) line invis from (-x0,-y0) to (x0,y0) \ "\m[GR0]\v'-0.22m'\D'e 0.5i 0.125i'\v'0.22m'" aligned } .PE === = It will work on both postscript and pdf. Cheers Deri

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

Update of bug #59933 (project groff): Status:None => Works For Me Assigned to:None => deri ___ Follow-up Comment #1: When I view th

Re: Escaping hyphens ("real" minus signs in groff)

;== with ucmap Of course, if the pdf is produced by using grops and ghostscript the result will be the same as using gropdf with no ucmap, i.e. '-' and '\-' will be pasted as different characters. Cheers Deri

Re: Escaping hyphens ("real" minus signs in groff)

copy to text the minus unicode cha character is seen. (On my system the fi ligature is separated into f i still but I suspect that is KDE being "helpful"). Cheers Deri

Re: [PROPOSAL] time zones and reproducible builds (was: How to make groff use local timezone?)

Am I missing a nuance that makes diffing the source code produced by the post processors useful? Cheers Deri

Re: [PROPOSAL] time zones and reproducible builds (was: How to make groff use local timezone?)

ws for incremental amendment by adding to the generation number. Cheers Deri

Re: [PROPOSAL] time zones and reproducible builds (was: How to make groff use local timezone?)

The only sensible time to include in the meta-data is the time the pdf was created, why lose potentially useful information? Cheers Deri

[bug #55557] [PATCH] gropdf, gpinyin, gperl, glilypond, hyphenex can execute arbitrary commands

Follow-up Comment #6, bug #7 (project groff): No objection here, so long as the patch to gropdf is excluded, for the reasons given in #4. ___ Reply to this item at:

[bug #55557] [PATCH] gropdf, gpinyin, gperl, glilypond, hyphenex can execute arbitrary commands

Follow-up Comment #4, bug #7 (project groff): Commit 2fc912f0751320a1fba0094dded38e2df46d1dbe fixed this for gropdf. I remember finding a case where the patch caused a problem with multiple input files. ___ Reply to this item at:

Re: UTP 1.1 build failure on Debian Stable

as removed from the install after the build. So long as groff is built after ghostscript, all should be well. Cheers Deri

Re: UTP 1.1 build failure on Debian Stable

9.27, you should be able to progress. If you have a different version of groff than 1.22.4 use the appropriate version number in the path above. Cheers Deri

Re: Learning troff - where to start?

as your baby since my efforts are minor compared to all the people who did the real work. If I had to do all that typing (well using dasher) we would probably still be waiting! Cheers Deri

Re: Learning troff - where to start?

On Wednesday, 14 October 2020 03:20:17 BST Damian McGuckin wrote: > The UTP Revival Project recreated the source code because Tim and Sale > were unable to locate a copy of the original source. It is located at: > > http://home.windstream.net/kollar/utp/ There is a version with

[bug #57506] Erroneous "slant" value in Times italic font(s) for ps device

Follow-up Comment #3, bug #57506 (project groff): > (4) Do we need to do something similar for the basic 14 PDF fonts? As part of install these are copied from the font/devps directory. ___ Reply to this item at:

Re: Why do Unicode Characters in the PDF Outline show up as, for example, [u1FOA1]?

, parameters to .pdfhref are just treated as ascii, i.e PDFDocEncoding. Cheers Deri

Re: Groff macro to make .UR and .UE links clickable in PDF?

lpful" ones. Cheers Deri

Re: Groff macro to make .UR and .UE links clickable in PDF?

inst his lengthy man page when he wants to produce a pdf version. Cheers Deri pdfman Description: Perl program

[bug #58206] [PATCH] fix PDFPIC issue with determining size of pdfs containing images

Follow-up Comment #7, bug #58206 (project groff): PDFPIC is not written by me, but I understand why it was written! The gropdf driver supports this:- \X’pdf: pdfpic file alignment width height line-length’ Place an image of the specified width containing the PDF drawing from file file of

Re: eqn sqrt and pdf?

order that we can know when we need to rebuild groff. Is the download file expected to be immutable? There are instructions how to add fonts to groff, which involves changing the download file. How do packagers deal with configuration files which are intended to be editable by users? Cheers Deri

Re: eqn sqrt and pdf?

given to gropdf, i.e. it is one of the base fonts. Cheers Deri

Re: eqn sqrt and pdf?

On Sunday, 1 March 2020 09:36:53 GMT Colin Watson wrote: > > > * troff should use the current version of ghostscript > > > > I'd guess so. > > > > Debian's groff maintainer, Colin Watson, is a subscriber here, and may > > pipe up soon. > > Apparently the current ghostscript version at build

Re: eqn sqrt and pdf?

On Monday, 24 February 2020 14:21:26 GMT Marc Chantreux wrote: > hello, > > > The symbol font is one of the base type 1 fonts which all pdf viewers > > should support, so the font is not actually embedded in the pdf. You > > could try adding "- P-e" to the groff command. > > Even if Tadziu told

Re: eqn sqrt and pdf?

On Friday, 21 February 2020 15:26:50 GMT John Gardner wrote: > I can confirm the PDF you've produced is correctly-formed; so this narrows > the problem down to a missing font (or misconfigured environment). > > What program are you using to preview the PDF? Marc, The symbol font is one of the

Re: man Macro Package and pdfmark

/groff_book.pdf Not sure there is any real benefit, just the satisfaction of knowing groff can produce its own documentation! Cheers Deri

Re: man Macro Package and pdfmark

d for windows users, you might like to try running it through the attached program as a pre- processor before calling groff. I.E.:- pdfman | groff -Tpdf -k -mandoc > your_man_page.pdf (Add your extra personal macros as required). You can see an example of the sort of documents this produces by pointing your browser at:- http://chuzzlewit.co.uk/WebManPDF.pl/man:/7/groff_mdoc I hope this is useful. Cheers Deri pdfman Description: Perl program

[bug #57747] Malfunctioning romanian special characters

Follow-up Comment #1, bug #57747 (project groff): It may be that some of the Romainian glyphs are not present in the font you are using. You may need to install a font (into groff) which contains all the glyphs you need. A suitable font is already on the system, since vim is using it, but it

[groff] 01/01: Certain pdfmark destination names caused gropdf to fail.

deri pushed a commit to branch master in repository groff. commit 800b0197ea8b2dcaee5b22e890f5dbea22b8d250 Author: Deri James Date: Mon Dec 30 17:37:48 2019 + Certain pdfmark destination names caused gropdf to fail. * src/devices/gropdf/gropdf.pl: Look for pdfmark types, (i.e

[groff] 01/01: Update man page of gropdf to document \X calls.

deri pushed a commit to branch master in repository groff. commit 14c4fd87810427f1240a18c69ef63414087de028 Author: Deri James Date: Sun Dec 29 22:16:17 2019 + Update man page of gropdf to document \X calls. * src/devices/gropdf/gropdf.1.man: The calls 'pagname

Re: FAMILY-dependent apostrophe behaviour with -mom

On Monday, 2 December 2019 19:26:02 GMT Marc Simpson wrote: > Hi Deri, > > On Mon, Dec 2, 2019 at 10:50 AM Deri wrote: > > If you can provide some examples, I would like to look into this > > difference. > Sure: I've just put a Fossil repo up at > > http://fos

Re: FAMILY-dependent apostrophe behaviour with -mom

> Marc Hi Marc, If you can provide some examples, I would like to look into this difference. I think I need a mom source file which shows the difference and a copy of the groff font file and associated .pfa font which has the problem. It may also help if you can produce the pdfs one from pdfmom and one from pdfroff (although pdfmom -T ps should be using pdfroff). Cheers Deri

Re: Cannot find the module of “pfbtops"

based on RedHat, there are five rpms:- groff groff-doc groff-for-man groff-perl groff-x11 Please check if you have them all installed. pbftops is actually in the groff package but the groff executable is in the groff-for-man rpm. Cheers Deri

Re: [Groff] mm TC - how to place in the beginning of document?

On Saturday, 23 November 2019 14:02:26 GMT Ralph Corderoy wrote: > The mom macros have a method of moving the table of contents with -Tpdf > that depends on gropdf(1)'s .pdfpagename and .pdfswitchtopage. (Deri, > I don't think they're documented?) mom uses them with the page name

Re: [Groff] mm TC - how to place in the beginning of document?

On Saturday, 23 November 2019 14:02:26 GMT Ralph Corderoy wrote: > The mom macros have a method of moving the table of contents with -Tpdf > that depends on gropdf(1)'s .pdfpagename and .pdfswitchtopage. (Deri, > I don't think they're documented?) mom uses them with the page name

Re: [groff] Table of content for UTP in groff format

? > > > Regards > > > [1]: https://www.oreilly.com/openbook/utp/ You can find a pdf version which includes an outline, clickable TOC and index here:- https://github.com/DeriJames/UTP-1.1 Many people on this list did the hard work of preparing the troff source. Cheers Deri

[groff] 02/03: Add new ghostscript font names

deri pushed a commit to branch master in repository groff. commit ef16d931a451621c14ca5b7706f91bc87797cf50 Author: Deri James Date: Sat Sep 21 16:03:37 2019 +0100 Add new ghostscript font names * font/devpdf/Foundry.in: Add changed font names --- font/devpdf/Foundry.in | 142

[groff] 03/03: Changes to allow configure to check for URW fonts

deri pushed a commit to branch master in repository groff. commit f61c6ca5b84b488cbd324f2d23285fff1d807f04 Author: Deri James Date: Sat Sep 21 16:27:05 2019 +0100 Changes to allow configure to check for URW fonts * font/devpdf/util/BuildFoundries.pl: Call the program

[groff] 01/03: Prevent gropdf executing arbitrary commands

deri pushed a commit to branch master in repository groff. commit 2fc912f0751320a1fba0094dded38e2df46d1dbe Author: Deri James Date: Sat Sep 21 15:52:54 2019 +0100 Prevent gropdf executing arbitrary commands * src/devices/gropdf/gropdf.pl: See bug #7 --- src/devices/gropdf

[bug #56748] URW font name changes (again!!)

URL: <https://savannah.gnu.org/bugs/?56748> Summary: URW font name changes (again!!) Project: GNU troff Submitted by: deri Submitted on: Sun 11 Aug 2019 03:16:51 PM UTC Category: Font devpdf Sever

Re: [groff] Unicode fonts output

On Tuesday, 6 August 2019 20:33:14 BST Jean Louis wrote: > * Peter Schaffter [2019-08-06 21:23]: > > On Tue, Aug 06, 2019, Deri wrote: > > > Two problems:- > > > > > > One, my solution used underscores when it should have used > > > hyphens, so th

Re: [groff] Unicode fonts output

t;U-"!! Two, I have found, in your example, the .FAMILY line needs to come after .START. The attached works Ok on my setup. Cheers Deri .\" -*- mode: text; coding: utf-8; -*- \# \# Copyright (C) 2004-2018 Free Software Foundation, Inc. \# \# Copying and distribution of this file, with or

Re: [groff] Unicode fonts output

e other uses of "FAMILY" in mom. If you are using .FT to set the family and font together, i.e. .FT HR Then use:- .FT U_HR This will not work if the URW fonts are not found when groff was built or packaged. Cheers Deri

Re: [groff] Termux Android app and Groff

On Friday, 17 May 2019 23:05:17 BST Mikkel Meinike Nielsen wrote: > Thanks for advice Deri > > So that should mean that viewing it in an other PDF viewer would show the > right fonts?? > > "One possibility is get groff to actually embed the used base fonts in the > p

Re: [groff] Termux Android app and Groff

On Friday, 17 May 2019 18:39:18 BST Mikkel Meinike Nielsen wrote: > Ok so I have teste now. I have got the fonts. It looks like this > > /data/data/com.termux/files/usr/share/groff/1.22.4/font > > $ ls devps > AB BMBI CI HBI HNR NR S TR freeeuro.afm text.enc > ABI BMI CR HI HR PB SS ZCMI

Re: [groff] Wierd font troubles

On Sunday, 24 March 2019 23:29:37 GMT Dale Snell wrote: > My thought is that Groff should simply > include the URW++ fonts by default. Given that both Fedora and Debian have > deprecated Type1 support, it probably won't be too much longer before those > fonts won't be available from the

[bug #55868] pdfmark hotspot vertical positioning error

Follow-up Comment #1, bug #55868 (project groff): I was unable to see a problem with the seealso pdf. All the hotspots seemed to be in the correct place, i.e. when I clicked on the hotspotted word the link opened, when I moved off the word, the mouse pointer changed shape. Is it the vertical

Re: [groff] [PATCH] Avoid Perl's unsafe "<>" operator

sed, because there will be no change of behaviour. I have been unable to find a way of defeating this protection method to make "<>" safe. Do you know of a way to circumvent it? Cheers Deri

Re: [groff] Upgrade to 1.22.4 breaks PDF font

if you install a different version of these ghostscript fonts they seem to move to a different directory, and possibly a slightly different name, so the download file in devpdf would need amendment. Cheers Deri

Re: [groff] [PATCH] Avoid Perl's unsafe "<>" operator

doesn't need the initial unshift since > that's already handled in contrib/glilypond/args.pl; gropdf declares > $input in a slightly different way since it's also used in the LoadAhead > function. > > Fixes: https://bugs.debian.org/920269 Hi Colin, Have you seen:- https://savannah.gnu.org/bugs/?7 Perhaps the patch could be uploaded there? Cheers Deri

[bug #55557] gropdf can execute arbitrary commands

Follow-up Comment #1, bug #7 (project groff): It looks like putting this line in the program, after any command line flags have been handled/removed from ARGV:- map { $_="< ".$_."\0" } @ARGV; This does a similar job to the code referenced by Colin at:-

[bug #55557] gropdf can execute arbitrary commands

URL: <https://savannah.gnu.org/bugs/?7> Summary: gropdf can execute arbitrary commands Project: GNU troff Submitted by: deri Submitted on: Wed 23 Jan 2019 03:59:31 PM UTC Category: Device

[bug #55334] preconv fails when build with libuchardet on MS-Windows

Follow-up Comment #10, bug #55334 (project groff): If pdfmom is used in a pipeline, or given a filename of "-", it uses a temporary file to store the contents of stdin, so it is unlikely to cause a problem for preconv. ___ Reply to this

Re: [groff] a5 paper size?

olds predefined paper sizes." Try:- \X'papersize=420p,595p' pl 8.26i This is a test The actual named paper sizes don't work, but you can enter the width,length as two numbers. The numbers above are in points but:- \X'papersize=14.8c,21c' Works just as well. However, if you want to create a pdf with all pages as A5, then remove the \X command and add the groff flags "-P-pa5" which also works. Cheers Deri

Re: [groff] 1.22.4.rc4 - Final RC before official 1.22.4

; i don't think a > dedicated commit is needed for that. Good idea. Sorry, my spastic fingers, and I didn't notice until the commit email. Cheers Deri

Re: [groff] 1.22.4.rc4 - Final RC before official 1.22.4

as been committed, mary thanks for your help. Cheers Deri

[groff] 01/01: Problem running gropdf on big endian (Sparc)

deri pushed a commit to branch master in repository groff. commit 92f40b186aa2adda8039fff09c1246bdd30dbd3d Author: Deri James Date: Sun Dec 9 12:45:45 2018 + Problem running gropdf on big endian (Sparc) * src/devices/gropdf/gropdf.pl: Prior to perl v5.9 the 'L<' templ

Re: [groff] 1.22.4.rc4 - Final RC before official 1.22.4

> > [...] > > > I don't think we should attempt to work around that ancient Perl bug. > > I mean, srsly, Perl 5.8.4 in 2018? > > I can't judge if it would be easy or not to work around this problem (I > let Deri comment on that), but I agree that it's

Re: [groff] 1.22.4.rc4 - Final RC before official 1.22.4

On Friday, 7 December 2018 01:41:54 GMT Ingo Schwarze wrote: > Thanks a lot for looking into the matter! Hi Ingo Thanks for all your help. > I think you should commit and push the change to add the '<' before > Bertrand releases. You already tested on little endian, i tested > on big endian,

[groff] 01/01: Problem running gropdf on big endian (Sparc)

deri pushed a commit to branch master in repository groff. commit 2dfd47edd74321fbccd74e9ae4dc70a99d1efb40 Author: Deri James Date: Fri Dec 7 13:24:17 2018 + Problem running gropdf on big endian (Sparc) * src/devices/gropdf/gropdf.pl: When loading a binary (.pfb) font

Re: [groff] 1.22.4.rc4 - Final RC before official 1.22.4

On Thursday, 6 December 2018 20:45:31 GMT Ingo Schwarze wrote: > Hi Deri, hi Bertrand, > > i found out more about why the mom test is failing on Solaris 11. > It turns out not just the test is broken, but there is likely a > portability issue in gropdf(1). > > I see

Re: [groff] Release Candidate 1.22.4.rc3

off itself, and replaced some placeholder tags which held minimal text with their man page text. So the only thing I did was write a script which attempts to convert the sources which were texinfo and man into troff code so that they can be combined into one pdf reference. Cheers Deri >

Re: [groff] Release Candidate 1.22.4.rc3

On Thursday, 29 November 2018 01:03:26 GMT G. Branden Robinson wrote: > At 2018-11-29T00:25:05+0000, Deri wrote: > > I'm interested in the groff book which is currently generated from the > > texinfo document. I have done some work which merges texinfo source > > and several

Re: [groff] Release Candidate 1.22.4.rc3

ages to produce an indexed pdf. It is not ready for this release, but I'm hoping to get it accepted for the next. Deri

[bug #55108] New pre-processor for business charts

Follow-up Comment #1, bug #55108 (project groff): Hi Bertrand, Please can you remind me, if I create a separate branch on my local git, how I push this to the savannah git as a separate branch, so others may test before it is merged. I believe you did give me the info once, when I was making a

[bug #54759] slide-demo.mom: Wrong kerning for "(°C"

Follow-up Comment #3, bug #54759 (project groff): Since you are seeing different results with different viewers, you could try the flags "-P-e" on your test-groff line. (This will embed the fonts in the pdf so the viewers should all look the same, but the file will be much larger).

[groff] 01/01: Savannah bug # 54812

deri pushed a commit to branch master in repository groff. commit d03f7e74fe7deeb0a6408f8027d5789ad75c555b Author: Deri James Date: Wed Oct 17 16:18:56 2018 +0100 Savannah bug # 54812 * font/devpdf/util/BuildFoundries.pl: If a font is not found report list of paths searched

[bug #54812] [PATCH] BuildFoundries.pl: Add the path for searching fonts to a message

Follow-up Comment #4, bug #54812 (project groff): Fixed in commit d03f7e74fe7deeb0a6408f8027d5789ad75c555b ___ Reply to this item at: ___ Message sent

[groff] 01/01: Savannah bug # 54779

deri pushed a commit to branch master in repository groff. commit 8f80fd6e9ef0bdc4180cedab8929b1fb34a913be Author: Deri James Date: Thu Oct 4 23:39:51 2018 +0100 Savannah bug # 54779 * font/devpdf/Foundry.in: Recent ghostscript changed name used for embedding groff font HNBI

[bug #54779] [PATCH] Foundry.in: Add a new name for a font

Update of bug #54779 (project groff): Status:None => Fixed Open/Closed:Open => Closed ___ Follow-up Comment #1: I am committing this

Re: [groff] Clickable links in PDF.

these macros with the -T pdf device, but if have forward references you need to run it twice in a pipeline such as:- groff -Tpdf -dPDF.EXPORT=1 -dLABEL.REFS=1 -ms -z file.trf 2>&1 | LC_ALL=C grep '^\\. *ds' | groff -Tpdf -ms - file.trf Cheers Deri

Re: [groff] improve a few terminal renderings of special characters

On Thursday, 30 August 2018 13:36:47 BST John Gardner wrote: > > The locations vary, e.g. a user's $MANPATH. Have the user specify it? > > That won't help... when I said how "*(NodeJS) shells out to the system to > locate manpages for display/processing"*, I was mainly referring to how > Node

[groff] 01/01: Fixes to gropdf

deri pushed a commit to branch master in repository groff. commit 7b3fa85e0f2da11f9475d2a36bb1a9608a6a999f Author: Deri James Date: Tue Jul 31 17:44:54 2018 +0100 Fixes to gropdf * src/devices/gropdf/gropdf.pl: Make default line width 0.4pt to match grops. Use 'S' operator

Re: [groff] gropdf(1) Has Ugly Thick Lines by Default.

On Monday, 30 July 2018 13:23:04 BST Ralph Corderoy wrote: > Hi Deri, > > Thanks for the very prompt reply. Sorry if I seemed grumpy; just time > pressure from deviating down another rabbit hole. :-) > Hi Ralph, I did not notice the grumps, I'm still looking for Alice to

Re: [groff] gropdf(1) Has Ugly Thick Lines by Default.

ome more on this. :-( Cheers Deri

[groff] 01/01: Add gropdf new features to NEWS file.

deri pushed a commit to branch master in repository groff. commit a3c62d4396f7ac468d41185e03c0d6cbd20fb3db Author: Deri James Date: Tue Jun 19 12:10:09 2018 +0100 Add gropdf new features to NEWS file. * NEWS: new features. --- ChangeLog | 8 +++- NEWS | 15

<    1   2   3   4   5   6   7   8   >