(Sorry, I meant "to 1 GB," not "by 1 GB)
Also, to clarify, when I do "forrest run" the PDFs are in fact generated,
but they use the default fonts, so the Japanese once again displays as
As stated previously in this thread, the out of memory issue was resolved by
increasing the memory to Java by 1 GB.
The outstanding issue is that the font is properly embedded when I use
"forrest site" to pre-generate content but not when I use "forrest-run" and
the PDFs are (apparently) created o
On 08.05.2009 03:29:20 David Crossley wrote:
> Heather Phipps wrote:
> > Actually, with my little hack, the font is properly embedded in the PDF only
> > when pre-generated, i.e., when you do "forrest site," but not when the PDFs
> > are generated on the fly, i.e., when you do "forrest run." Not s
Heather Phipps wrote:
> Actually, with my little hack, the font is properly embedded in the PDF only
> when pre-generated, i.e., when you do "forrest site," but not when the PDFs
> are generated on the fly, i.e., when you do "forrest run." Not sure exactly
> what accounts for the difference. If a
Actually, with my little hack, the font is properly embedded in the PDF only
when pre-generated, i.e., when you do "forrest site," but not when the PDFs
are generated on the fly, i.e., when you do "forrest run." Not sure exactly
what accounts for the difference. If anyone has a better understandi
FYI, other 1.1 files generate a PDF successfully, so it appears that the
problem is something more specific, which I have yet to identify...
