velocity-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bob Hutchison <>
Subject Re: Anakia html page widths
Date Sat, 06 Oct 2001 19:30:36 GMT

Thanks for the response... However... :-)

I have no doubt I wasn't alone in this problem, I'm pretty recent on this
list and I couldn't find mention of it. Spending time doesn't concern me too

As to the table being responsible, well, let me demonstrate. See the
attached file (notgood.html). This is the paragraph that contains the
example long 'word' I mentioned that I found in the developer guide. I've
removed everything except the enclosing table and the paragraph in question.
Make your browser window narrow to see. I've attached another version that
comments out the table (better.html) -- only the one line will be truncated.

OK, it isn't Anakia, if Anakia doesn't force you into formatting with
tables. This is why I apologised in advance. I don't know and as much as I'd
like to I cannot get into Anakia just now (I have to get Velocity in
production first). I've got a documentation issue looming at which point
Anakia is on my list.


On 01/10/06 2:53 PM, "Jon Stevens" <> wrote:

> on 10/6/01 9:33 AM, "Bob Hutchison" <> wrote:
>> Hello,
>> I've (finally) spent some time tracking down the cause of some formatting
>> behaviour in the developer's guide that I'm not too fond of. The problem is
>> that I cannot conveniently read or print the document without losing the
>> right hand side of the document. The same problem exists in the user guide
>> but it prints in landscape at least (the developer's guide is too wide for
>> that even).
>> It turns out that it is being caused by the use of tables (presumably by
>> anakia) to format text areas that contain very long words. If the long
>> strings are not in tables then you only lose the right hand side of the
>> lines that contain the very long words.
> I'm sorry you spent time tracking down something that we already know about
> and have discussed here in the past. In reality, the problem, it has nothing
> to do with tables. It has to do with the use of <pre> tags to render the
> stuff that shows up in the <source> tag's in the .xml source files.
>> An example of what I mean is
>> 'org.apache.velocity.runtime.resource.loader.DataSourceResourceLoader'
>> OK, so there isn't anything you can do about long strings, but I sure would
>> rather lose part of that one line than the whole document. This is about as
>> far as I am able to take it. Is there anything that can be done in Anakia to
>> solve this problem?
> Use a different .vsl file to render the site. We include a printable.vsl
> file in the jakarta-site2 cvs repo just for this purpose.
>> Sorry if I'm blaming Anakia for something that isn't its fault.
> It has absolutely nothing to do with Anakia. You wouldn't blame XSLT for
> this either.
> -jon

  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message