[bug #64576] [pdf.tmac] pdf*href option handling insufficiently flexible

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. :-)

Re: [groff] Macron characters in pdf files

On Mon 04 Jun 2018 23:21:15 Peter Schaffter wrote: > Greetings. > > I've verfied that the problem discussed in the following forwarded > email exists. -Tps has no trouble finding macron characters > composed in vim; -Tpdf does. Deri, I think this is your bailiwick. > > :) > Hi Peter, I'm hav

Re: [groff] hyphen, minus sign and hyphen-minus

On Sat 26 May 2018 13:16:42 Pali Rohár wrote: > And as I said "man -T dvi | dvipdfmx" > gives me better PDF output as man -Tpdf. So for reading I would really > prefer man -Tdvi Hi Pali, Have you tried passing -P-e on the command line when using -T pdf? One difference is that dvipdfmx always emb

Re: [groff] hyphen, minus sign and hyphen-minus

On Sat 26 May 2018 11:50:31 Ralph Corderoy wrote: > Hi Deri, > > > man -Tpdf will produce what you want. The '\-' (minus) is used as the > > output glyph, but any copy/paste (or searching within document) will > > use '-' (hyphen). > > > > This is similar to the treatment of ligatures. If you loo

Re: [groff] hyphen, minus sign and hyphen-minus

On Fri 25 May 2018 16:59:50 Pali Rohár wrote: > Happens for: man -Tps and man -Tdvi > > And I think that the best readable output is by grodvi driver. So would > really like to have working copy+paste from the dvi output (converted to > PDF viewer). man -Tpdf will produce what you want. The '\-'

Re: [groff] groff as the basis for comprehensive documentation?

On Sat 21 Apr 2018 08:16:36 Nate Bargmann wrote: > Note that I am only working with Groff's man macro package and do > understand that other macro packages may have greater demands on the > HTML generator. You might consider supporting mdoc macros. You may have seen:- http://chuzzlewit.co.uk/WebM

Re: [groff] PSPIC vs PDFPIC: adjust documentation to reality, or the reverse?

On Tue 10 Apr 2018 19:26:57 Tadziu Hoffmann wrote: > > I don't have a specific name suggestion, and I'm aware that > > this is a bikeshed, but can I suggest a more explicit variable > > name? Otherwise the next time some old behaviour needs to be > > switchably deprecated we're in for some confusi

Re: [groff] PSPIC vs PDFPIC: adjust documentation to reality, or the reverse?

On Mon 02 Apr 2018 12:14:03 Ralph Corderoy wrote: > Good afternoon Bernhard, > > > > So pdfpic is an extension of pspic. By that you can now even replace > > > all PSPIC by PDFPIC, nothing gets lost by that. > > > > I read this as suggesting that results with -Tps and -Tpdf should be > > equivale

Re: [groff] PSPIC vs PDFPIC: adjust documentation to reality, or the reverse

On Mon 02 Apr 2018 14:30:51 Doug McIlroy wrote: > > > Would it hence be sensible to change PDFPIC to fit the description > > Yes. This is clearly a bug, even if it's been around for years. > > Doug 100% agreement this should be fixed, although compatibility with previous version will be broke

Re: [groff] Creating a pdf slideshow

On Wed 14 Mar 2018 15:37:00 Ralph Corderoy wrote: > When viewing with mupdf(1) on this 1920×1080, `f' for full-screen, then > `H' to fit its height to the screen gives a slight non-paper edge at > both sides. `W' to fit width instead gets rid of them, losing a bit top > and bottom I presume, but w

[groff] Creating a pdf slideshow

ned out all the wrinkles. Cheers Deri .pl 9c .nr PO 1c .nr LL 14c .nr LT 14c .nr HM 1c .nr FM .5c .RP no .P1 .nr bm 0 1 .nop \!x X papersize=16c,9c .ds PDFHREF.COLOUR 0.0 0.3 0.9 .defcolor pdf:href.colour rgb \\*[PDFHREF.COLOUR] .ds PDFHREF.TEXT.COLOUR pdf:href.colour .OH "'\m[grey]Slid

Re: [groff] pdfmom: needs C locale?

On Sat 10 Mar 2018 12:29:54 Ralph Corderoy wrote: > I don't know how all those other commands did. :-) > What's the output of > > dpkg-query -W grep > grep --version > od -tx1z <<<$'x\xa0\xa0y' > LC_ALL=en_GB.utf8 grep z <<<$'x\xa0\xa0y' > LC_ALL=en_GB.utf8 grep z <<<$'x\xa0\x

Re: [groff] [bernhard.fiss...@mail.de: mom: PDF Author, pdfmom: needs C locale?]

On Fri 09 Mar 2018 16:09:35 Ralph Corderoy wrote: > That seems unlikely. grep thinks files are binary if they contain ASCII > NUL, or have a byte sequence that's invalid for the locale, and it only > emits that `Binary file ... matches' if such a line matches the regexp. > > Does your grep behave

Re: [groff] [bernhard.fiss...@mail.de: mom: PDF Author, pdfmom: needs C locale?]

On Thu 08 Mar 2018 17:06:12 Peter Schaffter wrote: > This seems to be an "on again, off again" bug. We discussed adding > LC_ALL=C to the command string in pdfmom, but I see it's not there. > Deri--any objections to adding it? The alternative is to pass the > -a flag to the various greps, but Ste

Re: [groff] Release Candidate 1.22.3.rc1

On Fri 16 Feb 2018 11:42:13 Peter Schaffter wrote: > After the list discussion back in the fall about slides and > gpresent, Deri tinkered with gropdf and I with om.tmac to implement > slides with mom/gropdf. I think the mom side of things is done, but > I'm holding off releasing the new version u

Re: [groff] Something broke embedded fonts in gropdf output (but not grops)

On Thu 15 Feb 2018 17:06:40 Jim Avera wrote: > Hello, > > Something changed between Ubuntu 16.04 and 17.10 which makes > locally-installed fonts not render correctly in PDFs generated with > groff -Tpdf. However groff -Tps produces correctly-rendering > postscript (files in devps/ and devpdf/

Re: [Groff] PDFPIC macro

On Sun 08 Oct 2017 20:26:02 Keith Marshall wrote: > You may recall that I did begin to explore possibilities, at the time, > but then life ... explicitly a protracted visit to Australia and New > Zealand, followed by too many other priorities on return ... got in the > way. I've now found a bit

Re: [Groff] devpdf U-fonts and Russian

On Fri 06 Oct 2017 13:43:13 Tadziu Hoffmann wrote: > In Postscript you can use the same font with multiple different > encodings; I assume something similar is also possible in PDF. > The way this is done is by making a copy of the font dictionary, > keeping all entries except Encoding, which is re

Re: [Groff] devpdf U-fonts and Russian

On Fri 06 Oct 2017 10:57:43 Tadziu Hoffmann wrote: > Well, I get *different* errors, that at first sight appear > somewhat bizarre but don't give the impression of something > critical > > bash$ groff -Kutf8 -pet -Tpdf RuTest.rof >RuTest.pdf > RuTest.rof: Too many glyphs used in font '39' >

Re: [Groff] pdfmom grep (was parallel text processing)

On Sat 09 Sep 2017 09:51:27 Peter Schaffter wrote: > On Sat, Sep 09, 2017, Ralph Corderoy wrote: > > Hi Peter, > > > > > > > > > The grep in pdfmom is returning a binary file hit when it encounters > > > the diacritic in > > > > > > .ds pdf:look(pdf:bm1) L'étranger > > > > > > > > What does lo

Re: [Groff] parallel text processing ; vertical and horizontal mode

On Thu 07 Sep 2017 18:07:27 Peter Schaffter wrote: > You'll notice that the top of the pdf file has a > line of text spit out by grep(1) that obviously shouldn't be there. > I guess I've never had to deal with diacritics in titles, because > I've never seen this before and the line only appears whe

Re: [Groff] Elegant -ms and -mpdfmark documents

On Tue 05 Sep 2017 23:49:26 Kristaps Dzonsons wrote: > For example, the colouring of links You could insert these lines at the top of the .ms file:- \# These lines set link text and border colours to rgb 0.0 0.3 0.9 .ds PDFHREF.COLOUR 0.0 0.3 0.9 .defcolor pdf:href.colour rgb \*[PDFHREF.COLOUR] .

Re: [Groff] mom : unicode in .INCLUDE'd files

On Sun 23 Jul 2017 10:16:39 Dale Snell wrote: > Hi Erich, > > I suspect that the typeface you're using simply doesn't have the > "char-with-breve" and "char-with-macron" characters. That > happened to me a while back. I needed vowels with macrons to > print out some Romaji (romanized Japanese) w

Re: [Groff] Problems with arcs and angles

On Tue 09 May 2017 13:55:38 John Gardner wrote: > Looks like there's a mistake in groff_out(5). It describes its arc-drawing > command as: > > *Draw arc from current position to (h1, v1)+(h2, v2) with center at (h1, > > > v1);* > > However, gropdf.pl tells a different story. To quote line #2791:

Re: [Groff] Nesting font macros in man pages

On Thu 27 Apr 2017 23:48:29 Steffen Nurpmeso wrote: > Terrible, see the spacing errors surrounding the command list > before the "Substitution" heading! Not your fault of course, but > gr... > > --steffen Well, turns out it WAS my fault! Bug in gropdf, will commit after more testing. Thanks

Re: [Groff] Nesting font macros in man pages

On Thu 27 Apr 2017 20:12:09 Ingo Schwarze wrote: > Does that still apply to > > view-source:http://man.openbsd.org/ksh compared with a PDF version:- http://chuzzlewit.co.uk/WebManPDF.pl/man:/1/ksh

Re: [Groff] Colors with gropdf

On Fri 25 Nov 2016 16:47:26 Robert Marks wrote: > I have recently had to embed a PDF image in a groff document and so have > been using > groff -Tpdf > to do so. > But I find that my \m[red] etc color commands are not recognised (and there > are error messages.. > Some work on Google led me to the

Re: [Groff] pdfmom question

On Tue 01 Nov 2016 15:56:49 Peter Schaffter wrote: > This is a question for Deri James. > > Is there some reason why, in pdfmom, the system() call to groff at > line 125 does not include '$preconv' in the first pass? > > I've been working on flexible vert

Re: [Groff] Times-Roman v. Nimbus Roman No9 L Regular.

On Thu 05 May 2016 15:13:34 Ralph Corderoy wrote: > Hi Deri, > > > One way to add the URW fonts post groff install is to run the > > BuildFoundries program after you have cd'd into the devpdf font > > directory. Within this directory you should find a file called > > "Foundry". Make sure line 68 i

Re: [Groff] .if !dTS - GNU extension?

On Sun 01 May 2016 17:39:59 James K. Lowden wrote: > As far as I can tell, you're defining "best" in terms of the goal of > delivering a base OS without a troff dependency for manual display. I > really don't understand why you consider that desirable. I would like > to see groff used more, not l

Re: [Groff] Times-Roman v. Nimbus Roman No9 L Regular.

On Tue 03 May 2016 10:53:45 Ralph Corderoy wrote: > Hi Werner, > > > > Should I be telling groff that I want to use those Nimbus fonts so > > > it uses their metrics rather than the "almost identical" Times' > > > ones? > > > > If you use the gropdf output device, try groff's `-P -y -P U' option

Re: [Groff] Using Make with pdfmom

gt; there. Is this the only way I can do this, or am I missing some option I > could use instead? In the current git log you should see:- == commit 0fd1ab8c1c07c7c9bfadd30042a617e7f855d13e Author: Deri James Date:

Re: [Groff] Groff command-line argument strangeness

On Mon 26 Oct 2015 05:31:28 Keith Marshall wrote: > > However, when I do this, groff gives the following warnings: > > > > > > Unknown option: I > > Unknown option: r > > Unknown option: c > > > > > > > > Have I done something wrong, and if so, what? > > Reproduced here ... looks like another bu

Re: [Groff] Tbl - repeating column titles

On Thu 24 Sep 2015 18:47:19 Ralph Corderoy wrote: > It may pre-date your time on this list, but some of us here re-entered > the book as troff source from the scan after I got Tim O'Reilly's > permission. http://home.windstream.net/kollar/utp/ > > Cheers, Ralph. You can retrieve the pdf with "cl

Re: [Groff] Mission statement PDF

On Thu 09 Jul 2015 07:04:53 Doug McIlroy wrote: > Peter wrote: > I've fixed the offending line in the Mission Statement pdf > > Out of curiosity, what was the offense? Did some groff construct > lead to it? > > Doug Tadziu said:- > The first element of the Widths array on line 315 of the PDF is

Re: [Groff] Mission statement PDF

On Wed 08 Jul 2015 17:56:10 Peter Schaffter wrote: > I've fixed the offending line in the Mission Statement pdf and > tested it with a batch of viewers. Seems to be working fine. > Uploaded the .pdf to the groff webpage. How fixed? A) Editing line identified by Tadziu by hand, or B) Regenerating

Re: [Groff] How remove title?

On Tue 16 Jun 2015 15:15:27 Peng Yu wrote: > Yes. It can generate the pdf. But the title is "LS("1")". How to > remove the title? It may be that if the title is removed some pdf viewers may show the title as "Untitled". All the viewers I have tried use the filename if a specific title is not giv

Re: [Groff] How remove title?

On Tue 16 Jun 2015 11:47:27 Peng Yu wrote: > I am on Mac. I have installed groff using homebrew. > > $ ls -lgo $(type -P groff) > lrwxr-xr-x 1 32 Jun 16 11:08 /usr/local/bin/groff -> > ../Cellar/groff/1.22.3/bin/groff > > Now, I see the following error. What do they mean and how to fix them? > Th

Re: [Groff] How remove title?

On Tue 16 Jun 2015 11:49:23 Steffen Nurpmeso wrote: > Anyway i finally have to say that it is a pity that, instead of > (making the engine as such multi-pass and) instrumenting the > macros for different output formats that need meta-information, > and extending the macros sets to include more meta

Re: [Groff] How remove title?

On Sat 13 Jun 2015 15:20:24 Peng Yu wrote: > > Do these actually check the manpages on my system? I guess it does > > not. I want to convert manpages on my system. > > Maybe you can make a corresponding version that works locally? Well, that is in fact what happens, on my system it is local. The

Re: [Groff] How remove title?

On Fri 12 Jun 2015 23:23:14 Peng Yu wrote: > Hi, I use the following command to generate a pdf file from a manpage. > But the pdf file has title "Untitled". I want to unset it via groff. > But I don't see an option to set title to be null. Would you please > let me know how to unset the title with

Re: [Groff] can't translate character code 229 to special character `oa' in transparent throughput

On Wed 10 Jun 2015 17:51:23 mikkel meinike wrote: > Deri you talk about an error in the source code of pdfmom? > > Anyway I made this work. I found and old document almost simular that did > not make that mistake. Than I copy/pasted and edite the contet of the old > doc to look like the new doc an

Re: [Groff] can't translate character code 229 to special character `oa' in transparent throughput

On Wed 10 Jun 2015 16:19:24 mikkel meinike wrote: > I just compiled groff from source and I used pdfmom in a way I have done > many times before but this time there was a strange problem that I have not > tried before. The error massages was printed into the document. > > This command is causing t

Re: [Groff] Business Graphics

On Sun 24 May 2015 12:53:07 Ralph Corderoy wrote: > Hi Deri, > > > Its purpose is to provide inline "business type" graphs for groff. I > > know we have grap which seems to be aimed at the more mathematical end > > of graphs, I'm aiming for the sort of graphs which a typical office > > spreadsheet

Re: [Groff] Business Graphics

On Sat 23 May 2015 10:53:49 Clarke Echols wrote: > Sounds interesting. Will there be an ability to fill the pie-chart > segments with color so the PostScript output from groff can be converted > to .jpg files for inclusion in HTML web pages? > > That would be useful. > > Clarke Yes, it works wi

Re: [Groff] Problem with tables changing setting.

On Mon 20 Apr 2015 22:31:03 Radek wrote: > Hi Ralph, > > Relevant part of Makefile is > > PREPROC = -pt > %.pdf: %.tr > groff -U $(PREPROC) -Tpdf -m spdf $< >$@ > > So the command is: groff -U -pt -Tpdf -mspdf table.tr >table.pdf The code snippet you provided does not seem to require the ms

Re: [Groff] gropdf ellipsis (u+2026) breaks with several fonts

On Wed 11 Mar 2015 09:36:15 Ellam ByDefault wrote: > I'm writing a document parser which outputs to groff to be processed with > gropdf. > When the parse document contains unicode ellipsis (u+2026), it goes fine > with few groff fonts, namely Times, Helvetica, Courier. > But with Palatino and the r

Re: [Groff] Blast from the past

On Tue 10 Feb 2015 20:53:42 Jones, Larry wrote: > "ROFF is a program which generates microfilm and 7-track binary magnetic > tape for off line processing on an IBM Magnetic Tape / Selectric > Typewriter..." I loved my selectric. IBM donated it to me when I was at school since no one, including m

Re: [Groff] ASCII dash in UTF-8 locale

On Fri 23 Jan 2015 08:39:20 Anthony J. Bentley wrote: > Heirloom troff and groff both render \- as en dash, not minus sign, > in PDF output. If you use groff's native pdf driver (-Tpdf) I believe minus is rendered, can be searched for and copy/pasted. The postscript driver also outputs a "min

Re: [Groff] Introduction to groff in french

On Thu 11 Dec 2014 00:43:18 Bertrand Garrigues wrote: > I was about to commit my example, however I ran into a problem. When I > generate the pdf with pdfmom -k, I have a few "can't translate character > code 233 to special character `'e' in transparent throughput" errors but > the output is fine.

Re: [Groff] release ready

On Sun 12 Oct 2014 13:43:28 Axel Kielhorn wrote: > While the grops man page says: > > fields may be separated by tabs or spaces; > > This is slightly inconsistent. > (Of course you can argue that these are different programs > and expecting them to use the same syntax is naïve. I wouldn't

Re: [Groff] PDFPIC macro

On Sun 21 Sep 2014 20:50:37 Keith Marshall wrote: > On 21/09/14 20:04, Deri James wrote: > > I'm glad that Ulrich has answered you, it was not my place to > > identify the person as they contacted me privately, > > Sure, but we must strenuously discourage such privat

Re: [Groff] PDFPIC macro

On Sun 21 Sep 2014 15:29:18 Keith Marshall wrote: > >> Good idea! > > > > > > > > Yes, it is. Someone on the list has contacted me, with a view to writing > > the code, > > Who might that be? If it was off-list, then we have a problem -- we all > need to be kept in the picture, with this sort o

Re: [Groff] PDFPIC macro

On Sun 21 Sep 2014 06:38:42 Werner LEMBERG wrote: > >> A good starting point may be to implement a C/C++ library function, > >> to extract the MediaBox properties; that would open the gate to a > >> possible pdfbb request, which gtroff.exe could process internally. > > > > > > Alternatively, we c

Re: [Groff] PDFPIC macro

On Thu 18 Sep 2014 19:13:44 Keith Marshall wrote: > Hmm. Perl. I've always shied away from it, particularly on MS-Windows. > I know there are implementations available, but my experience of > attempting to deploy them has always been extremely unpleasant and > discouraging. > > I'd much rather

Re: [Groff] PDFPIC macro

On Thu 18 Sep 2014 09:42:23 Peter Schaffter wrote: > On Thu, Sep 18, 2014, Keith Marshall wrote: > > > On 17/09/14 22:22, Peter Schaffter wrote: > > > Yes. The way groff stands now, I'm uneasy relying on external tools > > > and .sy for anything but local, user-written macros. There's precedent,

Re: [Groff] More referenceability for -mdoc would be an improvement!?

On Mon 15 Sep 2014 16:24:32 Ingo Schwarze wrote: > I fear that may be the wrong tool for the job. This is all about > local jumping within one single page, I have posted this link before, so apologies if you have already seen it

Re: [Groff] {Groff] underlining

On Tue 08 Jul 2014 09:10:05 Doug McIlroy wrote: > As has been pointed out, underlining by macro is at best inconvenient > in filled text. Thus it was proposed that underline, and perhaps > strike-through might be a groff primitive like .bd. All these capabilities > may be understood as ways to deco

Re: [Groff] Are your gropdf and pdfmom man pages installed?

On Tue 01 Jul 2014 17:41:24 Dale Snell wrote: > On Tue, 1 Jul 2014 19:20:57 -0500 > > Dave Kemper wrote: > > I finally updated my system-wide groff installation from 1.21 to > > 1.22.2. I notice that two man pages new in 1.22.2, those for gropdf > > and pdfmom, were not installed in the upgrade.

Re: [Groff] `fi' makes trouble in pdf

On Mon 02 Jun 2014 14:22:48 Tadziu Hoffmann wrote: > > How do you recommend `disassembling' a PDF to inspect > > its contents? I'm happy grokking PostScript but want to > > see the PDF's structure so pdf2ps's output, for example, > > isn't suitable. > > There is a wonderful program called "qpdf"

Re: [Groff] `fi' makes trouble in pdf

On Mon 02 Jun 2014 11:55:32 Ralph Corderoy wrote: > Hi Tadziu, > > > However, it does not embed the font (it contains an encoding vector > > and only a reference to "Times-Roman") so it is up to the viewer to > > provide the requested font. > > How do you recommend `disassembling' a PDF to inspec

Re: [Groff] `fi' makes trouble in pdf

On Sun 01 Jun 2014 18:40:58 Bernd Warken wrote: > `ttf-mscore-install' did not work for me. > > Von: "Deri James" > > > I've tested on okular 0.17.4 and 0.19.0, both seem Ok.> > > If you'd like to send me the pdf which won't display

Re: [Groff] `fi' makes trouble in pdf

On Sat 31 May 2014 19:29:32 Bernd Warken wrote: > You are right. The error come from my OS. The viewers okular and evince in > Kubuntu 14.04 (actual) and 14.10 (instable) produce the lacking ligature > `fi', but 13.04 (old long-term LTS) is fine. That is independent from > `groff'. > > Bernd Wa

Re: [Groff] lacking characters in groff_char.man

On Tue 27 May 2014 19:55:34 Bernd Warken wrote: > The following characters can't be shown with groff_char.man: > > \[.j] \e[.j] dotlessju0237 j without a dot > \[vA] \e[vA] uni21D5 u21D5 vertical double arrow in both directions > \[-+] \e[-+] uni2213 u2213 minus-plus > \[coproduc

Re: [Groff] Using non-ASCII characters in mom

On Fri 25 Apr 2014 11:35:42 Peter Schaffter wrote: > On Thu, Apr 24, 2014, Per Edin wrote: > > I'm having some trouble getting non-ASCII characters to work in my > > mom-based documents. With pdfmom -k I get them to work without problem > > in running text, but, when I use them inside quotes in .HE

Re: [Groff] Mission statement, second draft

On Wed 19 Mar 2014 20:29:12 Eric S. Raymond wrote: > > If I have misunderstood Eric's intentions with regard to the purpose of > > introducing the .hygiene command, then it would be very helpful if he > > could elucidate further. > > The reason to write .hygiene isn't doclifter, it's to allow ot

Re: [Groff] Mission statement, second draft

On Wed 19 Mar 2014 15:22:42 Eric S. Raymond wrote: > > SO: Supposing that this proposed enterprise goes ahead, WILL WE > > STILL BE ABLE TO USE GROFF AS WE ALWAYS HAVE DONE? > > Yes. Except if you are a man page author who wants to use all the troff syntax, in which case you will find that "some

Re: [Groff] Mission statement

On Tue 18 Mar 2014 12:58:09 Ingo Schwarze wrote: > Security-wise, PDF is > one of the most dangerous file formats, nowadays. That is true if the pdf reader you are using is configured to action all the extra bits which Adobe added to the standard (i.e. forms, flash and javascript). Without thes

Re: [Groff] Mission statement

On Mon 17 Mar 2014 19:11:50 Werner LEMBERG wrote: > > http://chuzzlewit.co.uk:8080/cgi-bin/WebManPDF.pl/man:/groff_mdoc > > This is amazing! Wonderful! I like it a lot. Indeed, viewing man > pages this way makes fun. > > What software is this? I've never seen before such a system. Can you >

Re: [Groff] Mission statement

On Fri 14 Mar 2014 23:26:46 Eric S. Raymond wrote: > > Manpages > > > > > > > > - improve the semantic usefulness of manpage markup; groff currently > > > > formats manpages for TTYs and PostScript from largely > > presentational markup, however increased use of browsers > > necessitates par

Re: [Groff] : New groff preprocessor for Perl parts in groff files.

On Mon 10 Mar 2014 16:30:13 Ingo Schwarze wrote: > Besides, enforcing build order by ordering directories/files > in list variables does not work at all in parallel builds. > I definitely know that this caused fallout in the past, even > before Bernd's commit, at exactly the place Bernd is now fid

Re: [Groff] Groff to pdf/Windows

On Thu 06 Mar 2014 17:24:09 Peter Schaffter wrote: > > Keith, is there any chance I could add something along these lines > > to pdfroff if the -T pdf switch is passed to pdfroff? > > I'm all for this. pdfmom performs splendidly. Nary a hitch with > forward references. Non-mom users could reall

Re: [Groff] Back to the future]

On 06/03/14 16:35, Eric S. Raymond wrote: > No, what I want is for all Unix documentation to be properly wenbbed and > crosslinked. I find it difficult to understand why groff needs a .hygiene, maybe it's because I'm a dirty rascal! It seems to be a switch which is designed to stop naughty man

Re: [Groff] Groff to pdf/Windows

On Thu 06 Mar 2014 21:47:15 Ralph Corderoy wrote: > I'm guessing that > > grep '^\.ds' > > might be the intent. > > Cheers, Ralph. Yes, indeed! Thanks.

Re: [Groff] Groff to pdf/Windows

On Thu 06 Mar 2014 18:08:10 Keith Marshall wrote: > On 06/03/14 16:21, Deri James wrote: > > If you are not using mom the actual command is:- > > > > groff -Tpdf -dPDF.EXPORT=1 -z $cmdstring 2>&1 \ > > > > | grep '^.ds' | groff -Tpdf - $preconv

Re: [Groff] Groff to pdf/Windows

On Thu 06 Mar 2014 09:21:57 Keith Marshall wrote: > A further advantage of using pdfroff is that it will automatically > handle the multiple groff passes required to resolve pdfmark cross > references, if you use the -mpdfmark macro set. I don't know if -Tpdf > will provide a similar level of supp

Re: [Groff] The future redux

On Sat 01 Mar 2014 11:29:08 Ralph Corderoy wrote: > Then there's Dale Dougherty and Tim O'Reilly's _Unix Text Processing_. > http://home.windstream.net/kollar/utp/ Given they were using troff to > produce their books, and continued to use groff for a long time to do > the production even when they

Re: [Groff] man pages (tangential to Future Redux)

On Fri 28 Feb 2014 21:16:37 Walter Alejandro Iglesias wrote: > When people is lazy to read no formating is enough to > make them happy The reason I prefer a typeset man page is because it aids comprehension of what I am reading. I'm all for an easy life me, anything which smooths the stormy s

Re: [Groff] The future redux

On Tue 25 Feb 2014 13:24:15 Eric S. Raymond wrote: > No, no, *no*. PDF on the Web is evil and must die. > > Here's why. It breaks the flatness of URL-space. HTML documents can point > at PDFs, but not *into* PDFs. I get slightly different results. If I use the url:- http://chuzzlewit.co.uk/

Re: [Groff] The future redux

On Wed 26 Feb 2014 10:19:07 Mike Bianchi wrote: > I cannot find man.config or any reference to it in Debian 7.4 (wheezy). > 2.6.2 2012-06-18 MAN(1) > Only manpath.config . > > What am I missing? > > -- > Mike Bianchi > Foveal Systems > > 973 822-2085 It looks like on debian t

Re: [Groff] The future redux

On Wed 26 Feb 2014 13:46:22 Walter Alejandro Iglesias wrote: > What do you want in a man page? Videos? 3D holograms? Only if they would help give an answer to the question you are trying to answer! > XTerm does not constrain nothing. It does what is expected from a terminal. > Do you think y

Re: [Groff] The future redux

On Wed 26 Feb 2014 11:46:32 Ralph Corderoy wrote: > Hi jkl, > > > > man pages don't really need expressive typography. > > > > Man pages are constrained by xterm. A better display system would > > invite tables, graphs, equations, and links. > > I don't think they are. Or they didn't used to b

Re: [Groff] The future redux

I have, so far, kept silent on future direction for groff, since my own use for groff is probably very rare, so my opinion should not carry much weight. I use groff as a typesetting engine called from a front end which produces a troff file which is then passed to groff to produce output. The tr

Re: [Groff] Firt letters overlapping with MOM

On Saturday 05 Oct 2013 17:30:13 Blake McBride wrote: > Thanks. That does fix the problem. > > Why wouldn't this (perhaps with a condition) not be in mom by default? I think it will be. (When Peter sees this) :-) The problem is only visible when you include the mom macro set but the file (t.m

Re: [Groff] Firt letters overlapping with MOM

On Saturday 05 Oct 2013 12:34:33 Blake McBride wrote: > Greetings, > > I installed 1.22.2 and current on my Mac with: > > ./configure --prefix=/usr --mandir=/usr/share/man > make > sudo make install > > (My Mac has GCC 4.2.1) > > t.mom contains: > > Now is the time for

Re: [Groff] need help with composite glyphs

On Monday 29 Jul 2013 09:27:05 Heinz-Jürgen Oertel wrote: > Am Sonntag 28 Juli 2013, 22:24:03 schrieb Werner LEMBERG: > > > If I code the text with \[u u030A] I expect it to be in the PDF. > > > > This glyph is only contained in the URW fonts. For example, try this > > > > with the PDF backend:

[Groff] me macros, page break too early : was Re: mm-macros, page break too early

On Tuesday 05 Mar 2013 15:26:01 Dave Kemper wrote: > > I have sometimes the problem, that a list triggers a page break too early, > > e.g. when a list or a picture would easily fit onto the page. > > I reported a similar bug in the -me macros (at > http://lists.gnu.org/archive/html/bug-groff/2012-

Re: [Groff] groff_lilypond v0.2

On Monday 11 Feb 2013 16:32:46 Werner LEMBERG wrote: > > Unfortunately the .PSPIC works only in groff pdf and dvi mode, not > > in ps. Tty, X and html mode have errors and display only a > > rectangle with the file name. > > What's the problem? For me, using .PSPIC directly to embed a lilypond >

Re: [Groff] .PSPIC seems to be broken

On Saturday 09 Feb 2013 02:20:29 Bernd Warken wrote: > .PSPIC is documented in groff_tmac(5). It is supposed to load an EPS-file. > That should work in the troff modes. In tty-modes and in X-mode it is not > possible to show the EPS-file, so only a box with the file name is > generated. > > But

Re: [Groff] pipes around link

On Sunday 03 Feb 2013 12:15:57 Shiv Shankar Dayal wrote: > Hi, > > When I use pdfhref like > > .pdfhref W URL > > then I get pipes around URL in PS output which makes URL incorrect. How to > solve this problem? I looked at pdfmark.ms but could not figure the > difference. I believe if you use "

Re: [Groff] groff-current fail to compile

On Friday 01 Feb 2013 09:22:25 Werner LEMBERG wrote: > Deri, Peter, any ideas how teo fix this? Maybe > guarding this part in `typesetting.mom' with an if-clause which tests > the availability of font family `N'? > > > Werner Either the document can use only the base 14 fonts, or the docume

Re: [Groff] groff-current fail to compile

On Thursday 31 Jan 2013 23:10:17 g@free.fr wrote: > that was better with 1.22.1 patched with diff.gz. I could compile again. > I could confirm some of the warnings new in 1.22.1 remain in cvs code. > See attached log > > Looking at font/devpdf/util/BuildFoundries were the warnings come from,

Re: [Groff] _Unix Text Processing_ Fails to Build.

On Sunday 27 Jan 2013 08:43:16 Larry Kollar wrote: > Sorry about the long-delayed response, guys. I've been up to my eyeballs > with both fiction and reality this month. I must be crazy to have agreed to > launch two novellas two weeks apart. :-P > > I'll apply the Chapter 9 patch, as the patched

[Groff] Unix Text Processing - PDF Bookmarks

0 $< > x.ps 2>ix.raw + $(VIEW) x.ps + +%.pdf : %.t + groff -step -ms -rRef=0 -Tpdf $< > x.pdf + mv x.pdf $@ + $(VIEW) x.pdf diff -uNBb a/mkindex.pl b/mkindex.pl --- a/mkindex.pl 1970-01-01 01:00:00.0 +0100 +++ b/mkindex.pl 2013-01-10 23:32:01.198153816 + @@ -0,0 +1,412 @@

Re: [Groff] _Unix Text Processing_ on Hacker News.

pl utp.aux > $@.tmp mv $@.tmp $@ clean:: @@ -50,7 +50,6 @@ $(VIEW) x.ps %.pdf : %.t - groff -step -ms -rRef=0 $< > x.ps - ps2pdf x.ps + groff -step -ms -rRef=0 -Tpdf $< > x.pdf mv x.pdf $@ - $(VIEW) x.ps + $(VIEW) x.pdf diff -uNB a/mkindex.pl b/mkindex.pl --- a/mkindex.p

Re: [Groff] EPS vs PDF support in MOM

On Monday 03 Dec 2012 11:48:15 Kobus Botha wrote: > The problem I have now is that PDF_IMAGE does not act as a replacement > for PSPIC The reason the pdf driver for groff cannot behave like pspic is because groff has no way of knowing the media size of the pdf graphic which you are importing. F

Re: [Groff] mom not in groff (ubuntu 12.04)?

On Wednesday 31 Oct 2012 09:20:59 Jan-Herbert Damm wrote: > hello all, hello Peter, > > i recently upgraded to ubuntu 12.04. afterwords om.tmac wouldn't be found > anymore. reason being that ubuntu had installed and groff 1.21. and the tmac > folder didn't contain moms tmac. i copied the latest ve

Re: [Groff] gropdf track kerning issue

On Tuesday 02 Oct 2012 13:45:40 Peter Schaffter wrote: > Deri, > > I've encountered a problem with gropdf and the .tkf request. When > I process this example with -Tpdf, the first block of type renders > perfectly. However, when I add track kerning, two anomalies creep > in: extra space is being

Re: [Groff] Build groff from CVS - afmtodit not found

y.in file solves the problem if you replace the one from cvs in font/devpdf. I am still working on a more robust solution which will stop the make failing if the required fonts are not found. Cheers Deri # Foundry file # Copyright (C) 2011 Free Software Foundation, Inc. # Written by De

Re: [Groff] passing groff special chars to pdfmark as bookmarks

On Monday 10 Sep 2012 06:53:38 smo...@sacredlabor.com wrote: > Is it the single quote apostrophe that is causing the problem, or, is > it something > else ? Were I to pass the string with the french special character > \['e] it is the > 'é' that gets dropped and for the word Séance I get Sance as

  1   2   >