Hi, Georg Datterl wrote: > Hi Chris, > > I was afraid the specification was to blame. One could implement an > extension, put it on flow, maybe even page-sequence and make it inheritable. > So it would not break existing code. That would be quite easy. Only I don't > know how much work the changes in the actual line-breaking algorithmus would > be.
See following bug report for a discussion of the issue: https://issues.apache.org/bugzilla/show_bug.cgi?id=43474 As a summary: I don’t think anything should be done in FOP. This issue is better handled upstream (usually by inserting zero-width spaces “at the right places”, which sometimes can be properly done only by a human being). If the URL doesn’t fit in a table cell, then don’t put it in a table. Or increase the width of the table cell accordingly. URL quickly become unreadable when they are broken anyway. Vincent > Mit freundlichen Grüßen > > Georg Datterl > > ------ Kontakt ------ > > Georg Datterl > > Geneon media solutions gmbh > Gutenstetter Straße 8a > 90449 Nürnberg > > HRB Nürnberg: 17193 > Geschäftsführer: Yong-Harry Steiert > > Tel.: 0911/36 78 88 - 26 > Fax: 0911/36 78 88 - 20 > > www.geneon.de > > Weitere Mitglieder der Willmy MediaGroup: > > IRS Integrated Realization Services GmbH: www.irs-nbg.de > Willmy PrintMedia GmbH: www.willmy.de > Willmy Consult & Content GmbH: www.willmycc.de > -----Ursprüngliche Nachricht----- > Von: Chris Bowditch [mailto:[email protected]] > Gesendet: Dienstag, 6. Oktober 2009 11:39 > An: [email protected] > Betreff: Re: AW: force wordbreak > > Georg Datterl wrote: >> Hi J, > > Hi Georg, > >> >> I just wondered. If FOP doesn't find a break possibility, the text is >> printed outside of the area. In table cells, the text is printed into the >> next cell. Does anybody need this? Wouldn't it be better to break anyway if >> the outer areas ipd is reached? And if I WANT to write into the next cell, I >> could always use keep-together.within-line="always"... > > or wrap-option="no-wrap" > > I think the reason this is not done as you suggest is because the > specification mandates the current behaviour. However, I concur with you. It > would be more beneficial if the behaviour was user friendly and either > wrapped or not the text based on the wrap-option property. > > Thanks, > > Chris > >> Regards, >> >> Georg Datterl >> >> ------ Kontakt ------ >> >> Georg Datterl >> >> Geneon media solutions gmbh >> Gutenstetter Straße 8a >> 90449 Nürnberg >> >> HRB Nürnberg: 17193 >> Geschäftsführer: Yong-Harry Steiert >> >> Tel.: 0911/36 78 88 - 26 >> Fax: 0911/36 78 88 - 20 >> >> www.geneon.de >> >> Weitere Mitglieder der Willmy MediaGroup: >> >> IRS Integrated Realization Services GmbH: www.irs-nbg.de >> Willmy PrintMedia GmbH: www.willmy.de >> Willmy Consult & Content GmbH: www.willmycc.de >> -----Ursprüngliche Nachricht----- >> Von: J.Pietschmann [mailto:[email protected]] >> Gesendet: Montag, 5. Oktober 2009 23:12 >> An: [email protected] >> Betreff: Re: force wordbreak >> >> On 05.10.2009 14:22, Georg Datterl wrote: >>> Probably the only thing you can do is insert zero-width spaces. >> Hmm, I've pondered crafting hyphenation patterns for URLs for some time. >> Q: Where should breaks in an URL occur? Only after '/' and '&'? >> This may leave URLs with large fragment Ids unbroken, which are >> unfortunately quite common. >> >> Once the patterns are there, >> <fo:block language="url" hyphenation-character="&zws;">... >> should work nicely. OTOH, hyphenation properties are block level only, which >> will have the side effect of not hyphenating natural language around the URL >> ... >> >> J.Pietschmann --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
