With the latest release of Adobe Acrobat/Reader XI there is a new feature available for structuring text in rich-text fields in XFA-based forms. You can now add/modify tab-stops in rich-text fields using new UI components. Adding tab-stops in rich-text fields allows for better formatting and table-like structuring of the text, which is a much requested feature from customers and users.
You download the sample file tabstops_richtext_field_dyn.pdf to see how this feature works.
1. Open the sample file in Acrobat/Reader XI.
2. Place the cursor in the large rich-text field.
3. Press CTRL+E on the keyboard to bring up the Form Field Text Properties toolbar.
4. Click the button “More…”
5. You will see the new Tabs dialog where you can create/modify the tabs in the field.
6. From here you can create/modify/delete the defined tab-stops, and change the alignment (Left, Right, Center, Decimal), or the position.
You can now also use the key combination CTRL+TAB on the keyboard to tab between tab-stops in the rich-text field.
The measurement units for the tab stops are inherited from the units defined in the Preferences (Edit > Preferences > Units & Guides > Page & Ruler Units):
When you use the toPS2() method with LiveCyclce ES2 to convert PDF files that contain complex dynamic tables to PostScript, text may overlap in some table cells following a page break.
This issue has been reported with a table structure at the page break as follows:
The following image shows the table in Reader and after conversion to PostScript with ES2:
We have exposed a new flag in the XDP templates that can be used with LiveCycle ES2 SP1 and later versions. Add the following line to the XML for all XDP templates that contain such tables:
<?originalXFAVersion http://www.xfa.org/schema/xfa-template/2.4/ LegacySplitPtCalcOverride:1 v2.8-layout:0?>
After using these flags in the XDP template and converting to Postscript again the table will appear correctly as follows:
The calculation for the page-break placement pushes the data from the first subform also onto the second page, on top of the data for the second subform. When the data from data_field1 would normally fit on the first page, but the data from data_field2 causes a page break, then the data from data_field1 is pushed to the next page and rendered on top of data_field2.
If you are installing Workflow 7.2.2 onto a DB2 database you may encounter the following error during the bootstrapping process:
“A system temporary table space with sufficient page size does not exist”
This is due to the “CREATE TEMPORARY TABLESPACE” command having failed when you created the LiveCycle Database.
This can occur when the DB creation script is invalid, due to missing line breaks, or spaces. Please consult the appropriate LC installation documentation for your version. The script for LC7 is as follows:
CREATE TEMPORARY TABLESPACE ADOBE_TEMP_8K IN DATABASE PARTITION GROUP IBMTEMPGROUP PAGESIZE 8192 MANAGED BY SYSTEM USING (‘C:\DB2\ADOBE_TEMP’) EXTENTSIZE 32 PREFETCHSIZE 16 BUFFERPOOL BP8K;
CREATE REGULAR TABLESPACE ADOBE_DATA_8K IN DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 8192 MANAGED BY DATABASE USING (FILE’C:\DB2\ADOBE_DATA’1000) EXTENTSIZE 16 PREFETCHSIZE 16 BUFFERPOOL BP8K;