Re: [xsl] [XSL-FO] column of small width

Subject: Re: [xsl] [XSL-FO] column of small width
From: Arved Sandstrom <Arved_37@xxxxxxxxxxxxxx>
Date: Wed, 20 Dec 2000 23:33:12 -0400
"Nikolai Grigoriev" <grig@xxxxxxxxxxx> wrote:

Arved Sandstrom wrote:

>> Let's assume that your content is inside an fo:block; i.e.
>>
>> <fo:table-cell><fo:block>TEXT</fo:block></fo:table-cell>
>>
>> The default wrap-option is "wrap", meaning that line-breaking occurs for
>> overflow. So you're seeing this for your first example.
>>
>> But in the second example it's not a line-breaking problem, which in any
>> case is left up to the formatter, it's a word-breaking problem. By default
>> hyphenation is false, so if you've got a long word and not enough space,
>> what else do you do?

> In this case, we at RenderX reduce letter-spacing/word-spacing until the
long
> word fits into the available line length, so that text distribution into
columns
> is always respected. If you only need to pull in a character or two, it
really
> helps (though for a long text like an URL on a very short line, this may
stretch
> the text beyond readability limits).

Hi, Nikolai

Oddly enough this exact same thought occurred to me, too, as soon as I posed 
myself the question "what else do you do?" :-) I don't doubt that for 
borderline situations we will end up borrwing a page from your playbook on 
this one, since it is a sensible approach.

As you suggest, some stuff one cannot handle this way. I was testing out 
columns in FOP some time back, and ran an example that contained URLs, just 
as you cite as an example above. No way would this be readable when
compressed.

At some point, obviously, the formatter has to refuse to handle the problem, 
though, and leave it up to the user to correct the situation and rerun.

Regards, Arved Sandstrom

Fairly Senior Software Type
e-plicity (http://www.e-plicity.com)
Wireless * B2B * J2EE * XML --- Halifax, Nova Scotia


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Current Thread