On Friday, 30 June 2023 16:26:51 BST G. Branden Robinson wrote:
> Hi Deri,
>
> At 2023-06-30T16:09:55+0100, Deri wrote:
> > On Friday, 30 June 2023 15:43:49 BST Dave Kemper wrote:
> > > Are any of the solutions put forth in this thread suitable for
> > > commit to groff git (obviously not on maste
Hi Deri,
At 2023-06-30T16:09:55+0100, Deri wrote:
> On Friday, 30 June 2023 15:43:49 BST Dave Kemper wrote:
> > Are any of the solutions put forth in this thread suitable for
> > commit to groff git (obviously not on master till it's unfrozen)?
> > They don't appear to have been pushed to any of t
On Friday, 30 June 2023 15:43:49 BST Dave Kemper wrote:
> Are any of the solutions put forth in this thread suitable for commit
> to groff git (obviously not on master till it's unfrozen)? They don't
> appear to have been pushed to any of the branches. And I don't see a
> savannah ticket for the
Are any of the solutions put forth in this thread suitable for commit
to groff git (obviously not on master till it's unfrozen)? They don't
appear to have been pushed to any of the branches. And I don't see a
savannah ticket for the issue.
On Wednesday, 14 June 2023 03:57:01 BST G. Branden Robinson wrote:
> At 2023-06-14T00:53:42+0100, Deri wrote:
> > This is using a real font, deleted pdf:SS.
>
> Looks great! It's not led astray by the superscripts or anything.
>
> Regards,
> Branden
Hi Branden,
These are the files you need to
On Tue, 13 Jun 2023, Deri wrote:
Here's my 1.22.4 version with Tadziu's fix. The pdf shows the difference
between using my SS font, using Tadziu's fix to pdf.tmac and using grops
and the type 3 SS font.
That solves my issues.
Thanks Deri
- Damian
Pacific Engineering Systems International .
At 2023-06-14T00:53:42+0100, Deri wrote:
> This is using a real font, deleted pdf:SS.
Looks great! It's not led astray by the superscripts or anything.
Regards,
Branden
signature.asc
Description: PGP signature
On Wednesday, 14 June 2023 00:33:16 BST G. Branden Robinson wrote:
> At 2023-06-13T17:15:56-0500, G. Branden Robinson wrote:
> > I don't think we're _quite_ there, though; we need to contrive italic
> > corrections too, which seems like it would be harder without a real
> > font,[1] since they vary
At 2023-06-13T18:33:16-0500, G. Branden Robinson wrote:
> I undertook to do this. Lacking experience as a real typographer, I
> did things by eyeballing them with sample inputs that seemed likely
> provocative of glyph collisions in mathematical typesetting, and by
> limiting myself to adjustments
At 2023-06-13T17:15:56-0500, G. Branden Robinson wrote:
> I don't think we're _quite_ there, though; we need to contrive italic
> corrections too, which seems like it would be harder without a real
> font,[1] since they vary by glyph. See the attachments.
[...]
> [1] Well, maybe not. We can hand
At 2023-06-13T17:15:56-0500, G. Branden Robinson wrote:
> See the attachments.
Sigh.
.sp
.EQ
f ( pi ) + 2 pi int sin ( omega t ) dt + e sup { i pi sup { rho + 1 } }
.EN
.sp
.EQ
f ( pi ) + 2 pi int sin ( omega t ) dt + e sup { i pi sup { rho + 1 } }
.EN
.br
.ft I
A\[*p]\[*r]\[*w]Z
.sp
A\s'16'\[*p]\
Hi Tadziu!
At 2023-06-13T17:11:50+0200, Tadziu Hoffmann wrote:
> > I think the likeliest site to fix PDF output is the `pdf:SS`
> > macro in pdf.tmac.
>
> You are right.
>
> This works:
>
> .de pdf:SS
> .char \\$1 \s'n[.ps]u*89u/100u'\S'15'\\$1\S'0'\s'0'
> ..
> .pdf:SS \[*a]
> .pd
On Tuesday, 13 June 2023 21:46:59 BST Damian McGuckin wrote:
> Could I impose and ask for a patch to the 1.22.4 .tmac file please?
>
> I would like to test that against my updated EQN User Guide.
>
> Thanks heaps - Damian
Hi Damian,
Here's my 1.22.4 version with Tadziu's fix. The pdf shows the
On Tue, 13 Jun 2023, Tadziu Hoffmann wrote:
I think the likeliest site to fix PDF output is the `pdf:SS`
macro in pdf.tmac.
You are right.
This works:
.de pdf:SS
.char \\$1 \s'n[.ps]u*89u/100u'\S'15'\\$1\S'0'\s'0'
..
.pdf:SS \[*a]
.pdf:SS \[*b]
(etc.)
Could I impose and ask for a
On Tuesday, 13 June 2023 16:11:50 BST Tadziu Hoffmann wrote:
> > I think the likeliest site to fix PDF output is the `pdf:SS`
> > macro in pdf.tmac.
>
> You are right.
>
> This works:
>
> .de pdf:SS
> .char \\$1 \s'n[.ps]u*89u/100u'\S'15'\\$1\S'0'\s'0'
> ..
> .pdf:SS \[*a]
> .pdf:S
> I think the likeliest site to fix PDF output is the `pdf:SS`
> macro in pdf.tmac.
You are right.
This works:
.de pdf:SS
.char \\$1 \s'n[.ps]u*89u/100u'\S'15'\\$1\S'0'\s'0'
..
.pdf:SS \[*a]
.pdf:SS \[*b]
(etc.)
At 2023-06-13T02:48:47+0200, Tadziu Hoffmann wrote:
>
> > I tried two different methods of getting it to adjust the
> > font height, and neither worked at all.
>
> For me, the following works:
>
> .fzoom S 890
> .EQ
> i iota
> .EN
Huh. For me this works with ps but not pdf; in the latt
> I tried two different methods of getting it to adjust the
> font height, and neither worked at all.
For me, the following works:
.fzoom S 890
.EQ
i iota
.EN
Unfortunately, this also scales the uppercase Greek letters and
other mathematical symbols, which we don't want. In grops, we
At 2023-06-13T10:05:33+1000, Damian McGuckin wrote:
> Tadziu, Deri, thanks for looking into this where looking is the key
> word.
>
> Tadziu, your eyes had an answer that my eyes could see but not
> identify.
pdf.tmac synthesizes the slanted Greek glyphs like this.
https://git.savannah.gnu.org/c
Tadziu, Deri, thanks for looking into this where looking is the key word.
Tadziu, your eyes had an answer that my eyes could see but not identify.
On Tue, 13 Jun 2023, Deri wrote:
Is this because the lowercase greek characters come from the SS font in
postscript, which is not available to gr
At 2023-06-12T23:45:36+0200, Tadziu Hoffmann wrote:
> > But, the output direct to PDF from 'groff' does not match that of
> > going to Postscript and then converting that to PDF using 'ps2pdf'.
>
> The main difference that I can see is that in p8ps.pdf the symbol
> font has been scaled to match th
On Monday, 12 June 2023 22:45:36 BST Tadziu Hoffmann wrote:
> > But, the output direct to PDF from 'groff' does not match that of
> > going to Postscript and then converting that to PDF using 'ps2pdf'.
>
> The main difference that I can see is that in p8ps.pdf the symbol
> font has been scaled to
> But, the output direct to PDF from 'groff' does not match that of
> going to Postscript and then converting that to PDF using 'ps2pdf'.
The main difference that I can see is that in p8ps.pdf the symbol
font has been scaled to match the x-height of the text font.
In p8pdf.pdf the Greek letters
Hi Damian,
You can use diffpdf to find out where the differences are. diffpdf has
toggle switches for text only- vs. shape only-comparisons and produces
visual highlights.
Best regards,
Oliver.
On 12/06/2023 21:33, Damian McGuckin wrote:
The issue could be as simple as a discrepancy between
The issue could be as simple as a discrepancy between the font definitions
used between Postscript and PDF.
But I do not know enough to debug the issues.
The PDF rendering on the screen (or on paper)should match the Postscript
rendering that comes out of a printer which is sent that same Po
Hi Oliver,
On Mon, 12 Jun 2023, Oliver Corff wrote:
isn't it the case that the paper format must also be announced to
gropdf, not only the source document, in case the system default is
letter?
I am a total novice.
Did you try the -p option with gropdf?
No. I just used
groff -
Hi Damian,
isn't it the case that the paper format must also be announced to
gropdf, not only the source document, in case the system default is letter?
Did you try the -p option with gropdf?
Best regards,
Oliver.
On 12/06/2023 09:56, Damian McGuckin wrote:
I have used ditroff and then gro
I have used ditroff and then groff to produce Postscript for ages, from
which I then use 'ps2pdf' or some equivalent to produce a PDF document. We
even wrote (for clients) custom Postscript programs whose output we
imported into troff. I often send sai Postscript to printers. I only
create
28 matches
Mail list logo
