On Tuesday, 5 June 2018 16:37:15 BST Peter Schaffter wrote:
> Hi, Deri.
>
> > The results, i.e. failure, are identical for both gropdf and grops.
>
> Hmm... Processing your file, macron.trf, with -Tps and -Tpdf
> produces results different from yours, namely
>
> Wit
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
ome more on this. :-(
Cheers
Deri
rent state at:-
http://chuzzlewit.co.uk/groff_book.pdf
Chapter 6 (Preprocessors) is largely man pages. The pdf is built using groff.
Is this the sort of thing you were envisaging.
I am currently on holiday so minimal email.
Cheers
Deri
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
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
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
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,
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
; 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
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
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
>
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
>
> [...]
>
> > 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
as been committed, mary thanks for your help.
Cheers
Deri
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
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
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
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
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
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
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
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
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
?
>
>
> 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
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
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
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
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
given to gropdf, i.e. it is one of the base fonts.
Cheers
Deri
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
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
/groff_book.pdf
Not sure there is any real benefit, just the satisfaction of knowing groff can
produce its own
documentation!
Cheers
Deri
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
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
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
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
as removed from the install after the build.
So long as groff is built after ghostscript, all should be well.
Cheers
Deri
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
, parameters
to .pdfhref are just treated as ascii, i.e PDFDocEncoding.
Cheers
Deri
inst his lengthy man page when he wants to produce a pdf version.
Cheers
Deri
pdfman
Description: Perl program
lpful" ones.
Cheers
Deri
ws for incremental amendment by adding to the generation number.
Cheers
Deri
The only
sensible time to include
in the meta-data is the time the pdf was created, why lose potentially useful
information?
Cheers
Deri
Am I missing a nuance that makes diffing the source code produced by the post
processors
useful?
Cheers
Deri
;== 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
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
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
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
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
On Thursday, 17 June 2021 18:08:12 BST G. Branden Robinson wrote:
> Amid chewing on this I became worried that my
> approach would slather my name next to every line of the document in
> "git blame" output and look like credit-thieving.
On the contrary, I welcome your improvements.
Cheers
Deri
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
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
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
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
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
=..." 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
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
ever to improve it.
Cheers
Deri
groff-list-20210402.tgz
Description: application/compressed-tar
msboxes.pdf
Description: Adobe PDF document
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
On Sunday, 5 September 2021 11:25:22 BST Ingo Schwarze wrote:
> Hello,
>
> NRK wrote on Sun, Sep 05, 2021 at 07:10:12AM +0600:
> > Recently I've thought about using groff for writing static website.
>
> You mean, like
>
> https://mandoc.bsd.lv/mdoc/
> http://schwarze.bsd.lv/
or perhaps:-
; 1 file changed, 24 insertions(+), 4 deletions(-)
>
> diff --git a/contrib/sboxes/sboxes.am b/contrib/sboxes/sboxes.am
> index 47c916c..fc9be14 100644
> --- a/contrib/sboxes/sboxes.am
> +++ b/contrib/sboxes/sboxes.am
> @@ -1,3 +1,22 @@
> +# Copyright (C) 2021 Free Softwar
On Tuesday, 12 October 2021 11:49:23 BST Keith Marshall wrote:
> Ref: https://savannah.gnu.org/bugs/index.php?55107
>
> On 01/10/2021 01:10, Deri wrote:
> > I did try to help Keith with this previously, but I was mildly "told
> > off" (on list) for sending my help o
On Tuesday, 19 October 2021 17:16:32 BST Peter Schaffter wrote:
> Deri --
>
> Is there a way to suppress the diagnostics pdfbackground spits out?
> mom files processed with pdfmom are already saddled with pointless
> "can't transparently output node at top level" messag
On Monday, 20 September 2021 20:39:49 BST Keith Marshall wrote:
> On 20/09/2021 19:22, Dave Kemper wrote:
> > Hi Heinz-Jürgen,
> >
> > Thanks for debugging and submitting a fix for this problem!
>
> Except that it's not really the most appropriate solution; that was
> proposed four years ago...
e, you
will see the separate pages.
So the actual number of pages is correct, a slide can be more than one page,
depending on the
number of transitions.
Cheers
Deri
Is produced entirely by groff and has a full clickable index.
Cheers
Deri
the different indexes. You may need
to click on the
button at the top left followed by the second button in the row of buttons
which appear after
you have clicked the top left.
Cheers
Deri
be already installed on a
postscript printer) or the extended glyphs available in current URW fonts. If
you are using the extended glyphs then the font needs to be embedded in the
postscript or pdf file, I believe.
Cheers
Deri
s those areas. All these "extensions" are facilitated using the \X escape
for example, which allows you to send information directly to the output
driver.
The gropdf man page.
This describes some more \X extensions which are understood solely by the
gropdf device driver.
Cheers
Deri
On Monday, 31 January 2022 08:15:55 GMT Dave Kemper wrote:
> On 1/28/22, Deri wrote:
> > If you are using -T pdf you
> > don't need to include -mpdfmark, this is documented in the gropdf man page
> > and the pdfmark.pdf is referenced.
>
> True, but just barely.
On Friday, 28 January 2022 21:29:35 GMT Dave Kemper wrote:
> As a side issue, it looks like the .pdfinfo macro mentioned in this
> thread is un(der)documented.
>
> It's documented in the pdfmark documentation
> (contrib/pdfmark/pdfmark.ms), but it seems to apply to any document
> rendered with
r, the standard allows you to include your own custom keys as well. I
tested this with this troff code:-
.sp 1i
.pdfinfo /Title PDFINFO Test
.pdfinfo /Synopsis Here is a little more text
Deri James
It works, embedding the new field "Synopsis" in the dictionary. Unfortunately,
okular, evince and
$1)))eg;
- if ($pdfmark=~m/(.+) \/DOCINFO\s*$/)
+ if ($pdfmark=~m/(.+) \/DOCINFO\s*$/s)
{
- my @xwds=split(' ',"<< $1 >>");
+ my @xwds=split(/ /,"<< $1 >>");
my $docinfo=ParsePDFValue(\@xwds);
foreach my $k (sort keys %{$docinfo})
I will soon be adding this patch to groff git.
Cheers
Deri
t; to fix that bug with this patch.
>
> Yes, those sounds like bugs too, and probably both my fault to boot.
I believe ghostscript is not involved in making msboxes.pdf so should not
depend on finding ghostscript.
Cheers
Deri
On Tuesday, 7 November 2023 19:48:51 GMT G. Branden Robinson wrote:
> Hi Deri,
>
> At 2023-11-07T17:33:06+0000, Deri wrote:
> > On Monday, 6 November 2023 17:47:13 GMT G. Branden Robinson wrote:
> > > Slowly. I landed two small changes this weekend, but they're not
Hi Branden,
I was wondering how the merging of the new gropdf branch was going (I think
you very kindly offered to help merging with master). Recently you have
written on the list:-
"Also, when Deri James's gropdf improvements are merged for groff 1.24, the
file size of groff-man-page
rry if I sound harsh, but this change already cost me hours of work
> to fix.
>
> I am on the brink of getting the 1.22 source code and install that over
> the system package of 1.23, which just brings me hate.
I have added this line to the man.local file (/usr/share/groff/site_tmac on my
system) to
restore the asciitilde behaviour.
.tr ~\(ti
Cheers
Deri
onv and
uchardet for this guessing. What does preconv -v tell you, mine says:-
[derij@pip Chats (deri-gropdf-ng)]$ preconv -v
GNU preconv (groff) version 1.23.0.16-a53f5-dirty with iconv support and with
uchardet support
It is the support information which is important, you may be missing one of
.)
A slight change and you can colour the margins with pure troff so it works for
both postscript and pdf:-
groff -Tpdf -P-pa4 -P-e margins.trf > margins.pdf
Cheers
Deri
.\"
.\"
.pl 29.7c
is the sort of thing you want, you can download the software
here:-
http://chuzzlewit.co.uk/busgrap-20181129.tgz
Cheers
Deri
Introduction.pdf
Description: Adobe PDF document
s attached.
If you prefer I can send you the resulting fonts, plus instructions.
Cheers
Deri
Laplace.pdf
Description: Adobe PDF document
ges.
It would help me a lot if you could send me a captured log of your "make",
especially if you can use the version of BuildFoundries I have just committed
which should show the paths used for searching.
Cheers
Deri
esults. Sometimes they subtly change the names of the fonts
which ghostscript uses and I have to add the alternative names. If you can't
find the fonts it can mean they have baked the fonts in what they call %rom%
so they are not available as real files.
Cheers
Deri
an use these fonts, too, couldn't we?
> That would seeem less selfish to me on the part of the gs(1)
> program, wouldn't it?
If the results of gs -h include the text %rom% I believe this means some files
have been baked in, but you should talk to the ghostscript packager. One
wrinkle, if you go with just one copy of the fonts and use symlinks is that
ghostscript uses different names for the fonts than the old ms-dos names.
Cheers
Deri
> Yours,
>
> Ingo
t vertically and horizontally to an arbitrary extent. As it is, I have
> already run out of space, and new boxes do not appear on the chart (or
> appear in the wrong place).
>
> R.
This seems to work:-
.sp 2i
.PS 18i 5i
for j=1 to 18 do
!
ellipse "Deri";
arrow;
!
.PE
And run
d gropdf man pages have
examples of all
fonts they all need to be specified correctly in the download file for it to
succeed.
Cheers
Deri
> re-run 'configure'. It might help to 'make distclean' first...but I
> wouldn't be surprised if you hit the same afmtodit problem I did. I'll
> look at BuildFoundries and see if I can spot an error, but Deri's eyes
> will be better than mine here.
>
> In the below, you mi
to open device description file 'DESC'
it has come from gropdf.
It will help to know which message you are seeing.
Cheers
Deri
den,
Yes, it's a bug introduced when I switched search order to file within path.
Please test
with fix just posted to git.
Cheers
Deri
On Sunday, 26 June 2022 13:11:12 BST Ingo Schwarze wrote:
> Hi Deri,
>
> thanks for your extensive explanation.
>
[...]
> > In the same way that the choice of URW directory is passed into
> > Foundry.in, although I would prefer separate variables, one for
>
about the NimbusRoman fonts. So if you use
the centos
packages to install the fonts, any program which uses fontconfig to locate
fonts will be aware of
their presence. Gropdf nor grops use fontconfig to find fonts, which is why you
can use the --
with-urw-fonts-dir flag for configure.
Cheers
Deri
> Stay safe - Damian
On Wednesday, 22 June 2022 14:48:24 BST Ingo Schwarze wrote:
> Hello Deri,
>
> Deri wrote on Wed, Jun 22, 2022 at 01:07:34AM +0100:
> > I've tracked down the problem. The configure flag --with-urw-fonts-dir
> > was not being used when searching for fonts for the default f
On Tuesday, 21 June 2022 15:54:54 BST G. Branden Robinson wrote:
> > +BuildFoundries: warning: line 75:
> > +The path(s) used for searching:
> > +ARRAY(0x23cef899970)
>
> Urp. The form of that output is certainly bogus. Did I break it in a
> recent change? I'll check.
Nope. That was me,
On Wednesday, 22 June 2022 22:29:29 BST G. Branden Robinson wrote:
> Hi Deri,
>
> At 2022-06-22T21:30:25+0100, Deri wrote:
> > I think I have sussed what might be happening. In the port build the
> > standard fonts get built because of the addition of
> > /usr/lo
On Monday, 6 June 2022 19:08:23 BST Deri wrote:
> As I suggested it would be helpful if you are able to run gs -h on a windows
> box under cygwin and natively, the output would help us.
I have now managed to run gs -h under a VM of windows 10 with latest
ghostscript, and you are
c
| nroff
You should see the text ".sp". Any escape with zero movement acts in this way,
it is not special to
\&. The difference is that \& is the shortest escape which causes no movement,
so is useful for
this purpose, but it is essentially a space which has no width.
Cheers
Deri
k whether
gs -h uses
alternative separators on other operating systems? Also, shouldn't foundry.in
have some fiddling
as well?
Cheers
Deri
lar
spaces to trigger end of sentence detection, they will be disappointed because
they all prevent
detection just the same as \&.
You may want to mention its use in preventing groff recognising ligatures.
Typing reff\ will
prevent the fi ligature being used.
Cheers
Deri
e tex2dvi available on my system, I would not be too despondent.
Cheers
Deri
1 - 100 of 740 matches
Mail list logo
