You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Jeff Levitt (JIRA)" <de...@db.apache.org> on 2005/05/15 04:02:05 UTC

[jira] Commented: (DERBY-288) JDBC 2.0 Connection Methods Supported table in displays correctly in html but not in pdf form of Reference manual

     [ http://issues.apache.org/jira/browse/DERBY-288?page=comments#action_65416 ]
     
Jeff Levitt commented on DERBY-288:
-----------------------------------

I played around with the attributes for the column, but I cant seem to get it to display correctly in PDF format.  It always looks fine in html, but any transform that goes through the fo xsl files doesnt extend the cell to all three rows.

However, in this case, the information is meant for all three rows in the table, in which case, perhaps it doesn't need to go in the table at all?  Since it applies to everything, what if we were to put the information in the Implementation notes in a paragraph following the table?  Would that be sufficient?  I know it doesn't solve the problem directly, but its probably the proper way of displaying this information anyways, and it can be done easily.

Let me know, I'd be happy to create a patch if no one has objections...

> JDBC 2.0 Connection Methods Supported table in displays correctly in html but not in pdf form of Reference manual
> -----------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-288
>          URL: http://issues.apache.org/jira/browse/DERBY-288
>      Project: Derby
>         Type: Bug
>   Components: Documentation
>     Reporter: Mamta A. Satoor
>      Fix For: 10.1.0.0

>
> Reference manual has JDBC 2.0 Connection Methods Supported table. This table shows up correctly when viewed in html http://incubator.apache.org/derby/docs/ref/rrefjdbc80004.html but not in PDF form. Basically, it does not extend the implementation notes for createStatement to prepareStatement and prepareCall.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira