Hi Alexander, Before questioning FOP's implementation you may want to consult the xsl:fo specification at http://www.w3.org/TR/2006/REC-xsl11-20061205/ first. If you believe that FOP strays from this, then please raise your concern on this list.
Often times the solution to a particular problem cannot be elegantly expressed in xsl:fo, however, xsl:fo is not designed as a human writable/readable data format and xslt processors should not be phased by a documents poor aesthetic quality. Computers are good at doing boring jobs like adding zero width space to strings so I would recommend figuring out a way to process the things like serial numbers when you include them in your fo. Pete On Tue, Nov 23, 2010 at 9:34 AM, Alexander Uvarov <[email protected]> wrote: > > On 23.11.2010, at 14:21, Georg Datterl wrote: > >> Hi Alexander, >> >>> Sounds insane for me. I have a lot of places in documents where i need >>> forced hyphenation. >>> It's unacceptable solution. >>> I am wondering why fop don't offer any elegant solution. >> >> Well, can you think of an elegant solution? >> >>> Why not just consider all strings as strings with zero width space after >>> each characters? >> >> Because then hyphenation would not work at all, because after every >> character there would be a possible place to hyphenate. And that's simply >> not correct in normal language. > > Table cell overflow is also inappropriate. If string can't be successfully > hyphenated, in case of overflow forced hyphenation would be better than just > overflow. Imho. > >> >> Regards, >> >> Georg Datterl > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
