Peter Lord wrote:
On 11/01/13 11:26, Lukas Theussl wrote:
Peter Lord wrote:
> On 11/01/13 08:14, Lukas Theussl wrote:
>> My question was: is the wrapping different in the apt source and the
>> pdf/html output? Pre-formatted text preserves line-breaks, so you
would
>> have to adjust the apt source to fit your needs.
>>
>> However, it seems to me that it should be possible to modify this
>> behavior with some xsl-fo attributes as you have indicated. You'll
have
>> to play around with some keep-together settings, in particular
>> keep-together.within-line, see
>>
http://stackoverflow.com/questions/2227797/xls-fo-fop-0-94-using-the-keep-together-with-wrap-option-wrap

>>
>>
>> But I'm no fo expert, maybe try a specialized fo list/forum if you
can't
>> get it to work.
>
> Thanks again.
>
> I found that the maven generated .fo file is not removed - which helps
> debugging!.  Reading this I can get my pdf-config.xml to insert the fop
> attributes in the correct place.
>
> However its still not wrapping.
>
> I understand that the FOP version used by the pdf plug-in (0.95) is now
> old with line break related issues resolved.   I think I'll need to
wait
> until the plug-in uses 1.0 or 1.1


Indeed, that's another issue I had forgotten. Unfortunately, the fop
upgrade to 1.0 is stalled because of

https://jira.codehaus.org/browse/DOXIA-409

and I just tried locally to use fop 1.1 and got stuck with a missing
dependency which is apparently known to the fop people:

http://comments.gmane.org/gmane.text.xml.fop.user/34912

So waiting for another fop release again... :(

-Lukas


Hi Lukas / all,

Are you aware of any progress in these areas ?

I tried using the trunk, 1.3-SNAPSHOT, but this brought in the same fop
version.

I haven't checked anything for a long time but the latest FOP version is still 1.1, so I don't expect any progress here.

Sorry...
-Lukas


Thanks again,

Pete



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to