Magnus Hagander writes:
> On Tue, Nov 10, 2015 at 6:15 PM, Tom Lane wrote:
>> I don't know anything about jpdftweak, but if it's being used to get rid
>> of unreferenced hyperlink anchors, maybe we could dispense with that step
>> after this goes in.
> Yeah, that's what I was hoping. You can se
Magnus Hagander wrote:
> On Tue, Nov 10, 2015 at 6:15 PM, Tom Lane wrote:
>
> > Magnus Hagander writes:
> > > When you say it's half the size - is that half the size of the
> > preprocessed
> > > PDF or is it also after the stuff we do on the website PDFs using
> > > jpdftweak? IIRC that tweak i
On Tue, Nov 10, 2015 at 6:15 PM, Tom Lane wrote:
> Magnus Hagander writes:
> > When you say it's half the size - is that half the size of the
> preprocessed
> > PDF or is it also after the stuff we do on the website PDFs using
> > jpdftweak? IIRC that tweak is only there to deal with the size, a
Magnus Hagander writes:
> When you say it's half the size - is that half the size of the preprocessed
> PDF or is it also after the stuff we do on the website PDFs using
> jpdftweak? IIRC that tweak is only there to deal with the size, and
> specifically it deals with "bookmarks" which sounds a lo
On Tue, Nov 10, 2015 at 1:46 AM, Tom Lane wrote:
> I wrote:
> > Curiously though, that gets us down to this:
> > 30615 strings out of 245828
> > 397721 string characters out of 1810780
> > which implies that indeed FlowObjectSetup *is* the cause of most of
> > the strings being entered. I'm no
On Mon, Nov 9, 2015 at 7:46 PM, Tom Lane wrote:
> I wrote:
>> Curiously though, that gets us down to this:
>> 30615 strings out of 245828
>> 397721 string characters out of 1810780
>> which implies that indeed FlowObjectSetup *is* the cause of most of
>> the strings being entered. I'm not sure
On 2015-11-09 19:46:37 -0500, Tom Lane wrote:
> Well, after much digging, I've found what seems a workable answer.
> It turns out that the original form of FlowObjectSetup is just
> unbelievably awful [...].
>
> This gets us down to ~135000 strings to build HEAD, and not incidentally,
> the resulti
I wrote:
> Curiously though, that gets us down to this:
> 30615 strings out of 245828
> 397721 string characters out of 1810780
> which implies that indeed FlowObjectSetup *is* the cause of most of
> the strings being entered. I'm not sure how that squares with the
> observation that there are l
and...@anarazel.de (Andres Freund) writes:
>> In some cases, it is possible for pdfjadetex to error out even with
>> expanded texmf.cnf settings. The sign of this is that jadetex is able
>> to process the file, but pdfjadetex isn't. The upstream maintainer,
>> Sebastian Rahtz, had this to say:
>>
On 2015-11-08 16:29:56 -0500, Tom Lane wrote:
> and...@anarazel.de (Andres Freund) writes:
> > While taking pretty short of forever, postgres-US.pdf seems to build on
> > my debian unstable as of 8d7396e509 + some additional docs. Is this
> > dependant of what version of text you're using (plain te
and...@anarazel.de (Andres Freund) writes:
> While taking pretty short of forever, postgres-US.pdf seems to build on
> my debian unstable as of 8d7396e509 + some additional docs. Is this
> dependant of what version of text you're using (plain tex, pdftex,
> xetex, whatnot)?
> postgres-US.log conta
On 2015-11-08 13:34:18 -0500, Tom Lane wrote:
> $ cd doc/src/sgml
> $ make postgres-US.pdf
> ... lots of crap later ...
> ! TeX capacity exceeded, sorry [number of strings=245828].
> We ran into a very similar issue back around 9.0, and solved it with an
> ugly style-sheet hack, see thread here:
>
12 matches
Mail list logo
