I don't know of anything. At least there doesn't seem to be anything in
XSL 1.1. I can bring it up at the XSL 2.0 workshop in October in case I
get accepted.
On 14.09.2006 05:36:15 Wyatt Tellis wrote:
Do you know if there are plans to update the XSL-FO standard to give
better control over
Do you know if there are plans to update the XSL-FO standard to give
better control over wrapping? It seems that something like this really
shouldn't fall under the category of hyphenation.
-Wyatt
Jeremias Maerki wrote:
overflow won't help here. wrap-option only controls whether to wrap or
I'd have to look up whether according to UAX#14/TR14 we would be allowed
to break between two * characters in the first place. Not that FOP
already implements the full rule set, yet! At any rate, I'd try to
insert a zero-width space (#x200B;) after each * character to allow
for breaks in between.
The asterisks are only one example. What about other character strings?
Unfortunately I have no control over what data is put in the report, but
I have to make sure that all characters are presented to the reader. I
can implement the (#x200B;) workaround, but would prefer a FO only
solution.
overflow won't help here. wrap-option only controls whether to wrap or
not, not how to wrap. XSL-FO uses country, language and script to
indirectly specify how line-breaking should be done. script is not
supported and country/language are currently only used to select the
right hyphenation pattern
I'm building a medical report printing application and I'm having
trouble forcing long characters strings (not really words) to wrap. FOP
gives the error: Line 1 of a paragraph overflows the available area.
(fo:block... For example I may have a series of 80 '*' characters. I
would like to
