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
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
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
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
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
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
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
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 @@
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
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,
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
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 "
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
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
>
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. :-)
101 - 153 of 153 matches
Mail list logo
