You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-users@xmlgraphics.apache.org by ausj81 ausj81 <au...@hotmail.com> on 2007/08/20 22:56:01 UTC
Re: fop cutting off lines - way to force wrap around?
Thanks for the reply Andreas - I had already considered option a but was
hoping there was a way around having to parse the body since it'd be a
headache but might have to grit my teeth and do it.
Does anyone know if the wrap-option="wrap" property put in an fo:block works
in 0.93 or 0.92? I am currently using 0.25 (and wrap-option doesn't seem to
work there - I put wrap-option="wrap" and still get the same overflow errors
and lines cutoff with japanese/korean/chinese documents), and know I will
have to spend quite a bit of time reworking my code if I upgrade since a lot
of the api has been changed from 0.25 and don't want to do that unless the
wrap-option functions correctly (which would be worth the upgrade trouble as
opposed to the "parse body and insert break characters where appropriate"
method which seems to be the only other alternative unless I'm missing
something). Thanks for any input.
>From: Andreas L Delmelle <a_...@pandora.be>
>Reply-To: fop-users@xmlgraphics.apache.org
>To: fop-users@xmlgraphics.apache.org
>Subject: Re: fop cutting off lines - way to force wrap around?
>Date: Wed, 18 Jul 2007 20:53:19 +0200
>
>On Jul 18, 2007, at 18:45, ausj81 ausj81 wrote:
>
>Hi
>
><snip />
>>The characters are encoded as entities in the xml so
>>ampersand#x30a6;ampersand#x30a7;... and so on but they don't have spaces
>>in them at all and so lines are always getting cutoff in the pdf when it
>>runs out of space.
>
>Indeed. Maybe your particular case isn't covered by the implementation
>yet, but normally FOP supports Unicode compliant line- breaking.
>IOW: if Unicode says "no break", then FOP says "no break", unless XSL- FO
>specific properties force it otherwise.
>
>If the rules for the languages you are using are covered by FOP's
>implementation of UAX#14, then the only valid ways around it are:
>
>a) pre-process the text, and insert characters that generate legal
>break-opportunities
>b) use the XSL-FO wrap-option="wrap" property on the surrounding fo:block
>
>Unfortunately, last I checked, b) was either unimplemented or broken in
>FOP 0.93 and the Trunk, so a) would be the only solution... but before you
>start working on that, I hope someone chimes in who can confirm with
>certainty that it is not merely a limitation in FOP's current
>implementation.
>
>
>Cheers
>
>Andreas
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
>For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
_________________________________________________________________
Now you can see troubleĀ
before he arrives
http://newlivehotmail.com/?ocid=TXT_TAGHM_migration_HM_viral_protection_0507
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org