Hi,
This is a pure fop-users_list topic, you don't need to post such thread on
fop-dev_list.
That said, the first stage of the debug process is to isolate the FO
snippet that cause the warning.
So, you should get first the resulting XSL-FO;
then you should feed FOP with that input.
etc...
Hi Gonzalo,
It is our intension to update the dependency on fontbox to be a specific
version. In order to do that we need to wait for a release of fontbox
containing the changes necessary to support OTF CFF Fonts to be
released. Until then we must rely on snapshot releases.
Thanks,
Chris
Great! Thanks for answering!
Gonzalo Vásquez Sáez
Gerente Investigación y Desarrollo (RD)
Altiuz Soluciones Tecnológicas de Negocios Ltda.
Av. Nueva Tajamar 555 Of. 802, Las Condes - CP 7550099
+56 2 335 2461
gvasq...@altiuz.cl
http://www.altiuz.cl
http://www.altiuzreports.com
El
Are you using trunk?
I get this with trunk:
Nov 19, 2013 11:42:05 PM org.apache.fop.events.LoggingEventListener
processEvent
WARNING: Content overflows the viewport of an fo:block-container in
inline-progression direction by 54 millipoints. Content will be
clipped. (See position 490:64)
You only get meaningful line numbers if you're running fo directly, not
in any sort of pipeline where the input fo file is a stream.
On 11/19/2013 04:45 PM, Luis Bernardo wrote:
Are you using trunk?
I get this with trunk:
Nov 19, 2013 11:42:05 PM org.apache.fop.events.LoggingEventListener
