> > Another important issue is security. PS, as a
> > programming language, allows far too much things.
To put this into perspective, many people have no qualms
running arbitrary javascript code in their browsers, not
only from from the URL displayed by the browser but also
from uncounted other
On Wed, 11 Oct 2017 18:41:38 -0400
"James K. Lowden" wrote:
> On Sat, 07 Oct 2017 15:17:25 +0200 (CEST)
> Werner LEMBERG wrote:
>
> > Another important issue is security. PS, as a programming language,
> > allows far too much things.
>
> But PS, as a programming language, is under programme
On Sat, 07 Oct 2017 15:17:25 +0200 (CEST)
Werner LEMBERG wrote:
> Another important issue is security. PS, as a programming language,
> allows far too much things.
But PS, as a programming language, is under programmer control. To
treat it as though it accepts input from untrusted anonymous so
> Other that Ghostscript's compression perhaps not being
> as good, so the image grows in bytes, does this matter?
> The resulting pixels are the same?
If ghostscript uses lossy compression, then the pixels will
be similar but not *exactly* the same. Possibly ghostscript
might also apply color m
Hi Heinz,
> 143.pdf was produced using -Tpdf
>
> -rw-rw-r-- 1 oe users 2299609 7. Okt 13:14 143.pdf
> -rw-rw-r-- 1 oe users 2265584 7. Okt 17:56 opt.pdf
Can you try `ps2pdf 143.pdf gs.pdf' and tell us its size.
I know it's `ps...', but it reads PDF too.
--
Cheers, Ralph.
https://plus.google.c
Am Samstag, 7. Oktober 2017, 15:17:25 CEST schrieb Werner LEMBERG:
>
> If you want small PDF files, I suggest pdfsizeopt as a postprocessor.
>
> https://github.com/pts/pdfsizeopt
>
>
> Werner
143.pdf was produced using -Tpdf
-rw-rw-r-- 1 oe users 2299609 7. Okt 13:14 143.pdf
-rw-r
> I understand the motivation for PDF was speeding rendering, e.g. no
> lexing of PostScript, and remove control flow so the linear
> description of the page dominated render time, and not hard to
> predict, or faulty, loops.
Another important issue is security. PS, as a programming language,
al
Hi Tadziu,
> (Also, ghostscript has the habit of reprocessing images even in
> pdfwrite mode (instead of passing on compressed image data untouched),
> which is somewhat suboptimal.)
Other that Ghostscript's compression perhaps not being as good, so the
image grows in bytes, does this matter? Th
> This is interesting. I thought that PDF had a more efficient way
> of storing data than PostScript and as a result allowed for
> faster reading and writing, although I've never looked into the
> details. I haven't yet switched over from using grops to gropdf,
> but I was beginning to think it wa
On Fri, Oct 06, 2017, Tadziu Hoffmann wrote:
>
> > This discussion makes me wonder what the 3000-line perl
> > script, grofpdf, can do that a trivial shell script that
> > calls groff and ps2pdf can't.
>
> Embedding of PDF figures, I guess. Also, in a very general
> sense, things like generating
On Fri, Oct 06, 2017 at 05:10:17PM +0200, Tadziu Hoffmann wrote:
> Subject: Re: [Groff] devpdf U-fonts and Russian
>
> Of course, the best solution would be for everybody to stop
> using PDF and start using Postscript instead.
This is interesting. I thought that PDF had a more effi
> This discussion makes me wonder what the 3000-line perl
> script, grofpdf, can do that a trivial shell script that
> calls groff and ps2pdf can't.
Embedding of PDF figures, I guess. Also, in a very general
sense, things like generating an outline. This is potentially
simpler because gropdf ha
This discussion makes me wonder what the 3000-line perl script, grofpdf,
can do that a trivial shell script that calls groff and ps2pdf can't.
doug
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
> I will work on fixing this so that if gropdf runs out of
> undefined characters which can be used it will start using
> defined but unused characters. This is a little trickier,
> since a character which points to an unused glyph may in fact
> get used later in the document.
In Postscript you c
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 05/10/17 20:40, Tadziu Hoffmann wrote:
>> Another strange thing is that, in case of using mixed
>> Russian/Latin symbols in pic and tbl objects, the Latin
>> letters and numbers become mis-positioned.
>> I wonder what I am possibly do wrong. The GROFF version is 1.22.2
>> on Ubuntu 14.04. The c
[Replying to the list because of possible general interest.]
> I followed you advice and it indeed worked. Didn't know that the
> U-fonts can be copied from devpdf to devps :) Thank you for the hint!
> But could you at least reproduce the error from my example? Because if
> it is a bug, it ought
> Another strange thing is that, in case of using mixed
> Russian/Latin symbols in pic and tbl objects, the Latin
> letters and numbers become mis-positioned.
> I wonder what I am possibly do wrong. The GROFF version is 1.22.2
> on Ubuntu 14.04. The compilation command used is:
>
> groff -Kutf8
19 matches
Mail list logo
