On Tuesday 18 Oct 2005 12:44, D. E. Evans wrote:
>
> >We had a discussion on this list a few months ago, that if anyone had
> > done a WYSIWYG front-end for groff years ago, it would be more viable for
> > the masses. Sigh.
> >
> Like all UNIX tools, the specialized ones are the most viable.
On Thursday 20 Oct 2005 19:46, Larry Kollar wrote:
> Is anyone collecting the "reasons for using groff" that have been
> going by in this thread? Such a collection would be a fine beginning
> to an advocacy/"Why Use groff" chapter in UTP (or a standalone web
> page). I'd be particularly interested
On Monday 24 Oct 2005 21:40, you wrote:
> Deri,
>
> Are the barcodes generated by troff? (A special font?)
>
> Or are they images that are generated, and then something like .PSPIC
> glues them into the documents?
I generate the bar code directly, using interleaved 2of5. (GPLed font here:-
On Friday 10 Mar 2006 14:28, Michail Vidiassov wrote:
> Dear All,
>
> let us run some survey.
> Please, tell us, how do you use groff PS output.
> Do you know how other people use it?
> Is it really in use?
> Do you use fonts supplied with groff or install your own font files?
>
> Werner is now des
Hello,
I have been trying to get printer "jogging" to work from within groff. The
print bureau have told me I just need to insert this code on the page which I
need "jogged":-
%%BeginFeature: *Jog
<< /Jog 3 >> setpagedevice
%%EndFeature
so I set up two macros:-
.de Jogger3
ps:
On Monday 01 January 2007 19:52, Eric S. Raymond wrote:
> Here is a slightly expanded version of a diagram I posted back towards
> the beginning of the discussion:
>
[...]
>
> The box in the middle is intended to indicate the use of DocBook as a
> common interchange format.
I may have, on occasion
Follow-up Comment #4, bug #64576 (project groff):
Just completed a fix to allow any input to be used as a valid *roff
identifier. This allows all UTF-8 to be used as well. So both "Known Issues"
in my NewGropdf document are now ticked off. :-)
On 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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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:
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
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
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
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
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
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
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
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:
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
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]
.
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
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
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'
>
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
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
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/
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
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
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
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
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
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
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
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
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
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
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 '\-'
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
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
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
On Monday 21 April 2008 15:40:57 Ralph Corderoy wrote:
> Hi,
>
> I'm on Ubuntu 7.10 with
>
> groff 1.18.1.1-12
> evince2.20.1-0ubuntu1
>
> I'm finding evince doesn't treat the PostScript from groff as being A4.
>
> $ cat /etc/papersize
> a4
> $ date | groff -ma4 >date.ps
On Friday 23 May 2008 19:23:12 pod wrote:
> How can I define own colors?
Hi Pod,
Dean has illustrated the use of "shaded" in pic. You can get a list of
predefined colour names by looking for the file "ps.tmac". You can also
define your own colours (from 'info'):-
==
On Monday 29 September 2008 20:23:02 Clarke Echols wrote:
> I finally bit the bullet and got rid of my Windows 98 SE operating
> system, replaced the drive with a RAID mirror pair of 500 Gbyte
> drives, added 2 Gbytes of memory, and installed Ubuntu Linux.
>
> I feel like the outcast who came out o
On Friday 10 October 2008 13:43:26 Werner LEMBERG wrote:
> > how to draw a circle with red shade and red edge, while the text is
> > green?
>
How about:-
.PS
r=1
circle rad r "\s-2A\s+2" shaded "red" outline "green" invisible
.PE
Cheers
Deri
On Tuesday 04 August 2009 19:58:04 Werner LEMBERG wrote:
> [Deri, I hope it's OK with you that I cite from your private email to
> me.]
>
Fine.
>
> Some weeks ago Deri James sent me a first implementation of a gropdf
> driver; I've uploaded it temporarily to
>
On Wednesday 05 August 2009 11:30:50 joerg van den hoff wrote:
> just a short feedback:
>
> 1.)
> thanks!
>
> 2.)
> in a first test with
>
> groff 1.19.3
> perl v5.8.8
> macosX
>
> this seems to work more or less correctly.
> but with a small text sample the generated pdf was about a factor of
> 10
On Wednesday 05 August 2009 11:30:50 joerg van den hoff wrote:
> Warning: An error occurred while reading an XREF table.
> The file has been damaged. This may have been caused
> by a problem while converting or transfering the file.
> Ghostscript will attempt t
After having looked at Ted's greeting card example I realised that 'pic'
outputs:-
\X'ps: exec gsave currentpoint 2 copy translate %.4f rotate neg exch neg exch
translate'
to achieve the rotation and terminates it with:-
\X'ps: exec grestore'
I wanted the PDF driver (gropdf) I've been working
t, including
> images.
>
> On the other hand, Deri James has written a PDF driver (gropdf) for
> troff, so following his route you should be able to embed such images
> into a PDF directly. However, I don't know whether his driver is
> mature enough to support such images fo
On Wednesday 02 June 2010 03:04:47 Larry Kollar wrote:
> > It runs slowly
>
> And that statement pretty much casts everything else you say into
> question. "Runs slowly" compared to what? I haven't found any general-
> purpose formatter that even comes close to groff, speed-wise, and
> don't
On Friday 11 June 2010 13:34:36 Werner LEMBERG wrote:
> >> So either something has changed the numerical encoding of \[ua] in
> >> groff (but despite searching I have found no clue), or possibly the
> >> input characters "\[ua]" were mis-interpreted as "\[uA]". Could
> >> this have something to do
On Saturday 03 July 2010 00:31:20 brian m. carlson wrote:
> I'm working on autogenerating some troff input for a project of mine,
> but I found some very odd behavior with the ad request. My testcase is
> attached. If you run groff with -rTC=1, my name is properly centered
> and in italics (as de
On Tuesday 18 Jan 2011 17:51:22 walter harms wrote:
> Hello List,
> i have found an oddity with tbl and large fonts.
> i got the request to make the fonts larger to inprove readability.
> i added the \s16 and found that the width seems to scale but not
> the hight of the table. Is this intended ?
>
On Thursday 20 Jan 2011 23:25:32 Ralph Graulich wrote:
> Hello troffers!
>
> Did someone try to layout E/R diagrams with pic?
> Several years ago I built a very rudimentary toolchain, which read one or
> more config files, took the table definitions from the database's data
> dictionary, sends the
On Saturday 22 Jan 2011 09:54:45 Werner LEMBERG wrote:
> >>"The optional second argument to de changes this to a macro to
> >>
> >> ‘.end’."
> >>
> >> For me this sentence is difficult to understand, although the
> >> meaning is obvious.
> >
> > It was the same thing for me, I couldn
On Saturday 22 Jan 2011 11:25:58 Ted Harding wrote:
> On 22-Jan-11 11:03:47, Deri James wrote:
> > On Saturday 22 Jan 2011 09:54:45 Werner LEMBERG wrote:
> >> >> "The optional second argument to de changes this to a macro to
> >> >>
> >> &
On Friday 04 Feb 2011 08:34:57 Werner LEMBERG wrote:
> Folks,
>
>
> while discussing integration of gropdf into groff with Deri, he told
> me that gropdf essentially depends on downloadable PFA fonts to be
> included in the created PDF files. This boils down to a dependency on
> the URW fonts of
On Wednesday 23 Feb 2011 18:35:41 Patrik Schindler wrote:
>
> Input:
>
> .dropcap Lorem darkblue 3 T 0
> ipsum dolor sit amet, consectetur adipiscing elit. Ut dapibus velit non
> neque consectetur adipiscing. Sed accumsan, augue in eleifend
> consequat, tellus
>
> Call:
> groff -me -ma4 -mdropca
Apologies for asking a rather esoteric question!
There are several troff commands which cause a line break, the most obvious
being ".br". When a line break occurs 2 things may happen:-
1. The current line is flushed, and
2. Position is moved to start of new line
I say "may" because if the cur
On Sunday 06 Mar 2011 14:24:06 Deri James wrote:
> Does my analysis make sense? Is it desirable to make \X et al "transparent"
> so this effect won't happen. Will it break something else? Will I be able
> to work out how to "fix" it? (That last one is sort o
On Tuesday 26 Jul 2011 18:17:17 Werner LEMBERG wrote:
> Folks,
>
>
> I've finally found some time to add Deri's gropdf output device to
> groff, now in the CVS repository. Please test! There are still some
> minor issues (mainly related to packaging), but besides that it seems
> to work well.
>
pdfroff is a very clever and useful utility in groff and I'd appreciate advice
on how best to integrate it into gropdf. Currently gropdf includes its own
pdfmark macros which are intended as a drop in replacement for pdfmark.tmac,
in fact most of the macros are based on Keith Marshall's work.
P
On Thursday 28 Jul 2011 18:02:32 Ralph Corderoy wrote:
> Hi Deri,
>
> > In a pdf every page is an object and the page order is given in an
> > array called "kids" which is an attribute of the "pages" object. So to
> > reorder the pages in a pdf is simply a case of reordering this array
> > before
On Thursday 28 Jul 2011 21:21:33 Peter Schaffter wrote:
> On Thu, Jul 28, 2011, Ralph Corderoy wrote:
> > Would it be better to leave the re-ordering to external utilities, e.g.
> > the pdftk package
> >
> > http://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/
> >
> > on the basis of do one sm
On Friday 29 Jul 2011 22:25:59 Ted Harding wrote:
> Greetings All!
> I'm writing to flag up a little trap that one might
> fall into when using 'tbl'.
>
> Background: I'm setting up a table and I want each
> row to have a row number to the left of the table.
>
> So I have defined a "left margin n
On Wednesday 03 Aug 2011 11:18:09 Bernhard Fisseni wrote:
> Good morning!
>
> I tried to compile CVS groff with devpdf and had the following problems; I
> hope I haven't missed any important instructions. (I probably did.)
>
> - In fonts/devpdf/Makefile.sub, the files list is supposedly gathered
On Friday 02 Sep 2011 12:22:46 Denis M. Wilson wrote:
> Hello all,
>
> There have been various postings on this list about the wrong
> positioning of the radical extender. I found that it depended on which
> font family was being used. It turned out that some text faces have a
> square root sign
On Wednesday 07 Sep 2011 15:19:49 Denis M. Wilson wrote:
>
> Deri,
>
> Am I right in thinking your font U-TI is the URW Nimbus Roman No9 L
> Regular Italic? If so then its sqrt matches that from the Symbol font
> S (if also URW), so a redefinition of sqrt is not necessary.
Denis,
Yes, I was us
On Wednesday 21 Dec 2011 21:44:48 Volker Wolfram wrote:
> Hi all,
>
> my last posting was not full completed.
>
> Here is my Makefile:
>
> default:
> groff -Tps -k -K utf8 -mm -m den 2.mm > test.ps
> ghostview test.ps
> print:
> lpr -Prp test.ps
>
>
> Adding .ad b won't work in my
On Saturday 07 Jan 2012 22:59:46 Ted Harding wrote:
> Just a few somewhat random thoughts. I've been through this
> sort of thing too often for it to be easy or quick to summarise!
I remember reading (on this list) a PHD thesis by Han The Thanh (of pdfTEX
fame) on micro typography, although the o
On Wednesday 25 Jan 2012 20:52:56 Volker Wolfram wrote:
> Ralph Corderoy wrote:
> > Hi Volker,
> >
> > > how can I turn text upside down, will say: rotate by 180 degrees?
> >
> > Do you only need this for a particular output, e.g. Postscript?
> >
> > Cheers, Ralph.
>
> Hi all,
>
> yes, my out
On Tuesday 21 Feb 2012 07:21:15 Clarke Echols wrote:
> I use groff to produce technical white papers. I run gv and
> monitor a PostScript file so every time I update the file while
> writing in vi (by pressing a function key that contains the groff
> command as a vi macro).
>
> When I need to pri
On Saturday 10 Mar 2012 14:05:22 Werner LEMBERG wrote:
> Deri,
>
>
> according to the gropdf man page, Type 42 fonts are supported.
> However, if I use one, I get the fatal message
>
> foo: Font file 'bar.t42' must be an Adobe type 1 font file
>
>
> Werner
Hi Werner,
The man page is wr
On Saturday 10 Mar 2012 13:42:53 Werner LEMBERG wrote:
> Deri,
>
>
> gropdf uses the `*' character in the `download' file. This not
> documented and I ask you to add it.
>
> Another question is how to easily update an installed `download' file
> at all. For example, if I upgrade from ghostscri
On Saturday 10 Mar 2012 14:36:37 Werner LEMBERG wrote:
> groff's PDF output device
> doesn't work; I suspect a bug (or it isn't implemented yet).
This was due to the current gropdf not handling glyphs above 255. I now have a
version which remaps glyphs to unused characters below 255, so your exam
On Sunday 11 Mar 2012 15:02:55 Ralph Corderoy wrote:
> Hi Deri,
>
> > ...so your example now works fine with -T pdf. The pdf produced is
> > huge though, I really must make myself do the font subsetting code.
>
> Out of interest, does `ps2pdf huge.pdf new.pdf' result in a smaller file
> with the
On Wednesday 28 Mar 2012 13:56:57 Petr Man wrote:
>
> Hello Keith,
> thanks, that clears the errors for start. Yet I still end up with
> missing čřž etc characters.
> Petr
Are you talking about missing from the bookmark ouitline panel or missing from
the text of the document?
Missing from outli
On Wednesday 28 Mar 2012 16:02:01 Werner LEMBERG wrote:
> > This is a (painful) limitation of Adobe's pdfmark specification:
> > only a rather limited set of characters is permitted within the text
> > which is specified to describe a bookmark.
>
> This is not correct, AFAIK. There are two encodi
On Friday 27 Apr 2012 06:19:25 bertrand wrote:
> I am using groff 1.21, with the following commands:
> groff -pt -m ms -m pdfmark -m spdf -Tps mydoc.ms > mydoc.ps
> ps2pdf mydoc.ps
If you are using a recent version (from CVS), and want to walk on the wild
side! You could try using the native PDF
On Sunday 06 May 2012 12:01:02 Werner LEMBERG wrote:
> Ideally, there should be a proper ToUnicode cmap in the PDF so that
> copy and paste gives good results. On the PostScript side, it should
> be theoretically possible to use the `GlyphNames2Unicode' dictionary
> (an undocumented Adobe Distille
On Saturday 26 May 2012 10:02:22 Denis M. Wilson wrote:
> On Fri, 25 May 2012 23:41:32 -0400
>
> Peter Schaffter wrote:
> > Building groff from the latest sources, 'make' terminates with
> > Error 2 after multiple warnings of the sort
> >
> > Warning: line 78: Failed to create groff font 'U-AB
On Monday 03 Sep 2012 19:02:59 mikkel meinike wrote:
> I have tried to compile latest groff on my debian chroot on my android
> tablet with ARM processor. Here I have this compilation error. I can see a
> response to an email I have found from Ted that it is essential to give the
> path to the font
On Monday 03 Sep 2012 19:02:59 mikkel meinike wrote:
> I have tried to compile latest groff on my debian chroot on my android
> tablet with ARM processor. Here I have this compilation error. I can see a
> response to an email I have found from Ted that it is essential to give the
> path to the font
On Wednesday 05 Sep 2012 06:31:41 Werner LEMBERG wrote:
> [Please configure your e-mail program so that it replies to CCed
> addresses also.]
>
> >> Minimum example, please, together with your calling sequence.
> >> Werner
> >
> > Sure.
> >
> > Given original text file date string macros as :
>
On Wednesday 05 Sep 2012 17:21:09 smo...@sacredlabor.com wrote:
> Deri,
>
> That works right to PDF. Nice.
>
> For those that have used gs to assemble pdfs, setting various
> pdf properties like permissions and pdf display variables, I wonder
> how that is to be batched now that groff is going d
On Sunday 09 Sep 2012 16:28:04 smo...@sacredlabor.com wrote:
> Can you explain in your own words what is happening with
> .trin '\C'aq' please.
>
> I have a text procesing sequence that does not afford the time
> at the moment to re-engineer how I build pdfs, gs / pdfroff.
>
> Relying on groff
On Tuesday 04 Sep 2012 07:32:48 Werner LEMBERG wrote:
> > The file you need to alter is font/devpdf/Foundry.in. [...]
>
> Deri, as I told you earlier: We need a configure test for that so that
> people can specify a URW font directory. If it isn't found, the
> `Foundry' script has to ignore URW
1 - 100 of 153 matches
Mail list logo