Adobe LiveCycle Designer
Version 7.0
|
Readme File |
December 2004 |
Copyright 2004 Adobe Corporation. All rights reserved.
This file contains important information that was not available when the product documentation was written. Review this information before running this version of Adobe® LiveCycle™ Designer.
- PDF Security
- Importing PDF Files Created Using Some Applications Can Be Slow
- PDF File Size Can Increase
- Font Names That Include Underscores Do Not Import Correctly
- Clicking PDF Preview Tab Opens Acrobat When Display PDF In Browser Option Is Not Selected
- Tabbing Order Is Incorrect When Previewing Forms for Acrobat 7.0 Using Acrobat 6.0.2
- Using Acrobat Professional to Edit PDF Forms Created in Designer
- Template Manager Custom Template Folder Is Not Created When Installing Acrobat Professional 7.0
- File Information Does Not Display in Acrobat Document Properties
- Screen Readers Do Not Speak Text for Dynamic PDF Forms
- Screen Readers Do Not Behave as Expected With List Objects
- Screen Readers Do Not Speak Additional Text for Text Objects in PDF Forms
- Documented Known Issues Between Acrobat 7.0 and Screen Readers Have Been Fixed
- Adobe Barcoded Paper Forms Solution May Not Correctly Handle Data from Fields with the Same Name
- Incorrect Message Appears for Drop-Down List and List Box Objects When Paper Forms Barcode Object Is On Form
- Paper Forms Barcode Object Cannot Contain Embedded Image Data in Image Fields
- Occurrence Constrains May Not Be Maintained When Generating Subforms from Imported Schema Files
- Must Browse for XML Schema File When Creating New Data Connection
- When Multiple Fields Are Bound to the Same WSDL Import Operation, Only One Field Is Populated
- Only Data in Bound Fields Is Saved
- Data Binding Options Apply to Form Data Saved to a Data File
International Language Support
- Designer Does Not Support Some Characters for PDF Passwords
- Some Locales Are Not Supported in Acrobat 6.0 Compatible Forms
- Support for Simplified Chinese GB18030 Characters
- Support for Japanese JIS X0213 Characters and the Hong Kong Supplementary Character Set
- Importing InfoPath Templates with Japanese Characters
- Importing a PDF File Containing Multibyte Characters
- Greek Letter Final Sigma Displays as a Diagonal-Crossed Rectangle
- IME Composition Window Shows Korean Characters
- New Date Pattern for Japanese and Korean Locales
- Reserved Words Used in Variable Names or XML Schema Field Names May Cause Unexpected Results
- Embedding PDF Files in an XDP
- Incorrect Warning Appears for Text Objects When Form is Acrobat 6.0 Compatible
- Incorrect Error Appears for Text Field Objects and Numeric Field Objects When Display Pattern Is Unexpected Format
- Text Field Objects Do Not Support Numeric Display Patterns Without a num Prefix
- Pasting Images from Microsoft Word Does Not Work as Expected
- Adobe Product Name Changes
When importing a protected PDF file, Designer asks for the file password. If the permissions password and the password to open the document are different, you must enter the permissions password. If the PDF file only has an open password, then you should enter that password. PDF security permissions are not retained after the PDF file is imported into Designer to create a new form. To protect the original PDF author's security considerations, you can reset the appropriate security options in the PDF Security tab of the Form Properties dialog box.
Importing PDF Files Created Using Some Applications Can Be Slow
PDF files that were created using applications that make use of advanced object background effects, such as DocuWorks and Adobe Illustrator®, cause performance issues when imported into Designer. These issues include long wait times during importing and large XDP file sizes.
The size of a PDF file can increase when imported into Designer and then saved again.
Font Names That Include Underscores Do Not Import Correctly
Importing PDF files that contain fonts with an underscore ( _ ) character in the name causes performance issues. In some cases, the font is not displayed.
Clicking PDF Preview Tab Opens Acrobat When Display PDF In Browser Option Is Not Selected
When the Display PDF In Browser option is not selected in the Preferences dialog box in Acrobat, clicking the PDF Preview tab in Designer will start Acrobat in its own window rather than embedded within the PDF Preview tab.
Tabbing Order Is Incorrect When Previewing Forms for Acrobat 7.0 Using Acrobat 6.0.2
When Adobe Acrobat® or Adobe Reader 6.0.2 is the latest installed version, the tabbing order will not appear correctly in the PDF Preview if the form is not compatible with Acrobat 6.0. You should set the Default File Type For New Forms option to Acrobat 6 Compatible (Static) PDF Form File and save all forms in that format.
Using Acrobat Professional to Edit PDF Forms Created in Designer
Adobe does not provide support for PDF forms created using Designer and edited using Acrobat Professional. Forms created using Designer should always be edited in Designer only.
Template Manager Custom Template Folder Is Not Created When Installing Acrobat Professional 7.0
The Custom Template folder used by Template Manager is not created when you install Acrobat 7.0 Professional.
File Information Does Not Display in Acrobat Document Properties
File information entered in the Info tab of the Form Properties dialog box does not appear in the Document Properties in Acrobat or Adobe Reader for PDF forms. Selecting the Enable Plaintext Metadata option in the PDF Security tab has no effect.
Screen Readers Do Not Speak Text for Dynamic PDF Forms
Some common screen readers have difficulties speaking text on dynamic PDF forms.
Screen Readers Do Not Behave as Expected With List Objects
Some common screen readers do not behave as expected when they encounter list box objects and drop-down list objects on both PDF forms and forms rendered by Form Server.
Screen Readers Do Not Speak Additional Text For Text Objects in PDF Forms
Screen readers will only read the displayed text for text objects on PDF forms. Any additional text specified in the Tootip or Custom Screen Reader Text fields on the Accessibility palette will be ignored.
Documented Known Issues Between Acrobat 7.0 and Screen Readers Have Been Fixed
The Designer Help topic "Design tips for creating accessible PDF forms" lists some known issues between Acrobat and screen readers. Two of these issues have been fixed in Acrobat 7.0. They are still issues for Acrobat 6.0. These are the issues:
- Whenever a drop-down list opens, the form loses focus.
- In certain cases, usually in numeric fields, when a value changes and the user asks the screen reader to read it back, the screen reader reads the old value. Tabbing out of the field and then back in usually fixes this.
Adobe Barcoded Paper Forms Solution May Not Correctly Handle Data from Fields with the Same Name
Adobe Barcoded Paper Forms Solution does not write field Occurrence numbers to the data. If a paper forms barcode object collects data from two or more fields with the same name, the data will not include information to distinguish the fields.
Incorrect Message Appears for Drop-Down List and List Box Objects When Paper Forms Barcode Object Is On Form
When you add a drop-down list or list box object to a form with a paper forms barcode object, the list object displays a message that you should specify a maximum data length or data pattern for the field. This message will disappear when you add a list item or specify a validation pattern. If the list will be populated at run time and there is not an appropriate validation pattern, you can ignore this message. However, you should keep in mind that the paper forms barcode object may be unable to estimate when the form will contain too much data for a single barcode object.
Paper Forms Barcode Object Cannot Contain Embedded Image Data in Image Fields
If you are using the paper forms barcode object, you should not select the Embed Image Data option for image field objects. The embedded image data is larger than the paper forms barcode object can hold.
Occurrence Constrains May Not Be Maintained When Generating Subforms from Imported Schema Files
Occurrence constraints in an XML schema can limit the number of elements for a data node. When a subform is generated from a data node with occurrence constraints, the Min Count and Max options for the subform may not be set to match the data node's constraints. To fix this problem, ensure that the subform's parent subform is set to flow content and enter the appropriate Min Count and Max values in the Object palette.
Must Browse for XML Schema File When Creating New Data Connection
If you are creating a new data connection using an XML schema file, you must use the Browse button in the second panel of the New Data Connection dialog box to select the file. Typing the path to the file will not enable the Finish button in the dialog box.
When Multiple Fields Are Bound to the Same WSDL Import Operation, Only One Field Is Populated
If you have more than one field bound to the same WSDL import operation, only one of the fields will be populated with data when the operation is executed. To populate more than one field with the same data, set the Default Binding option for each field to Global.
Only Data in Bound Fields Is Saved
If some fields on a form are bound to a data source, data in fields that are not bound will be lost when the form is saved in Acrobat. If you want to bind some fields to a data source, all fields that you want to save the data for must be bound.
Data Binding Options Apply to Form Data Saved to a Data File
Options in the Binding tab of the Object palette that are not directly related to creating a data connection apply both to data bound to a data source and data saved to a file when the object is not bound to a data source.
Performance is slow if a font used for a field or text object does not contain the characters in the field or text value. The process of substituting a font containing the correct characters can be slow.
Font Palette Displays Incorrect Font
When highlighting text from an imported form, the Font palette displays the original font used to create the form, not the mapped font within Designer. To see the name of the mapped font within Designer, double-click the text.
Myriad Pro Is Not Installed with Acrobat 6.0
Myriad® Pro is the default font for form objects. This font is installed with Designer and with Acrobat 7.0, but it is not installed with Acrobat 6.0. If you save a PDF form that may be opened by users with Acrobat 6.0, some characters may not appear for Acrobat 6.0 users unless you embed the fonts when you save the form.
International Language Support
Designer Does Not Support Some Characters for PDF Passwords
Designer only supports characters with ASCII values of 32 to 117 inclusive for passwords when you apply security to a PDF form. This range includes letters, numbers, and punctuation on a standard English language keyboard, but does not include accented or multiple-byte characters.
Some Locales Are Not Supported in Acrobat 6.0 Compatible Forms
The Locales Estonian (Estonia), Latvian (Latvia), Lithuanian (Lithuania), and Ukrainian (Ukraine) are not supported in Acrobat 6.0 compatible forms.
Support for Simplified Chinese GB18030 Characters
You must install the Microsoft® GB18030 support pack to correctly display Simplified Chinese GB18030 characters on a Simplified Chinese or English Windows® operating system. You can download the GB18030 support pack from the Microsoft website.
The FormDesigner.ini file controls how Designer handles GB18030 characters. After Designer has run at least once, this file is located in the Documents and Settings\username\Application Data\Adobe\Designer folder. The file contains these lines:
[Language]
Language=EN
AdvancedUICS=DefaultLanguage indicates which language for the Designer interface
AdvancedUICS indicates which character set Designer must partially support. These are the options:
Default This is the default value. Designer decides which character set should be supported. When Designer is running on a Simplified Chinese Windows operating system and MS GB18030 support pack is installed, Designer will use GB18030 characters for certain user interface elements.
Standard Designer relies on the systems font substitution capabilities to render characters in user interface elements.
GB18030 Designer uses GB18030 characters in certain user interface elements. You must use this setting to support GB18030 characters on an English Windows operating system.
To change the default setting, you must modify the FormDesigner.ini file and restart Designer.
Support for Japanese JIS X0213 Characters and the Hong Kong Supplementary Character Set
Designer only supports characters with Unicode values in the range of U+0000 to U+FFFF. JIS X0213 and HKSCS characters outside of this range will not display in the user interface or in form objects.
You can import PDF files into Designer containing unsupported JIS X0213 or HKSCS characters.
Importing InfoPath Templates Containing Japanese Characters
Microsoft InfoPath templates that contain Japanese characters in any of the view names do not import correctly into Designer. You must change the Japanese characters to valid UTF-8 characters prior to importing the InfoPath template into Designer.
Importing PDF Files Containing Multibyte Characters or Symbol Set Definitions
When importing a PDF file that contains multibyte characters or symbol set definitions, some characters and symbols may not convert and may be replaced with question marks (?).
Greek Letter Final Sigma Appears as a Diagonal Crossed Rectangle
The Greek letter Final Sigma (U+03C2) is not displayed correctly if you use any of the Adobe OpenType fonts.
IME Composition Window Shows Korean Characters
Korean characters are displayed at the bottom right of the Input Method Editors (IME) window. This issue occurs with Korean Input System (MS-IME 2002).
This issue does not occur with Korean Input System (IME 2002), the new Microsoft Text Service Framework (TSF), which performs simulations to control the composition window.
New Date Pattern for Japanese and Korean Locales
Designer implements the date symbol letter "G", to represent the imperial year in Japanese (Japan) and Korean (Korea) locales .
For more information specific to scripting in Designer, see the Scripting Readme file.
Drop-Down Lists Omit the Blank Value after a Page Change
When you change pages in a PDF form, blank entries will no longer appear in drop-down lists. You should use a value such as <none> to represent the blank value for the list.
Rotated Text Is Not Available in HTML
Rotated text is not supported in HTML and is not displayed correctly on forms rendered as HTML.
Supported HTML Formats and Internet Browsers
The following table contains a complete list of supported HTML formats and associated browsers. This list supersedes information in the TransformationMatrix.pdf file.
HTML Format
Supported Browser(s)
HTML 4
Netscape Navigator 4.7x
MSDHTML
Microsoft Internet Explorer 5.x and 6.x
CSS2HTML
Netscape Navigator 6.2x/7.0
Opera 7.0AHTML
Microsoft Internet Explorer 5.x and 6.x
Reserved Words Used in Variable Names or XML Schema Field Names May Cause Unexpected Results
Variables and XML schema field names may not be handled correctly by Designer if the name matches a reserved word in Designer. Variables that are named using reserved words such as case-sensitive object property names will not display in the form. XML schema field names can use most object property names, but certain names such as "model" can be confused with the property of the same name at run time.
Embedding PDF Files in an XDP File
You cannot submit XDP files that contain an embedded PDF file that has been signed or certified or that has document security set.
Incorrect Warning Appears for Text Objects When Form is Acrobat 6.0 Compatible
Text objects on Acrobat 6.0 compatible forms display a warning that the Expand To Fit option is not supported and the object may not work properly. This warning, which appears for text objects with the Auto-fit option selected, is incorrect and should be ignored.
Incorrect Error Appears for Text Field Objects and Numeric Field Objects When Display Pattern is Unexpected Format
If you enter a numeric pattern, such as num{9999}, as the Display Pattern for a text field or a text pattern, such as text{9999}, as the Display Pattern for a numeric field, you will receive an error message that the display pattern is invalid and that you should set a valid pattern in object palette.
These patterns can cause unexpected behavior for alphabetic characters; however, the patterns are valid and can be used if required in the form design.
Text Field Objects Do Not Support Numeric Display Patterns Without a num Prefix
Designer 6.0 allowed form authors to enter numeric patterns such as SZZZ,ZZ9.99 as the display pattern for a text field. Designer 7.0 more strictly enforces correct text and numeric field patterns and does not permit these patterns. If you have text field objects formatted to display numeric patterns in forms created in Designer 6.0, you should change the object type to Numeric Field on the Field tab of the Object palette.
Pasting Images from Microsoft Word Does Not Work as Expected
Images from Microsoft Word that contain layout properties other than In Line With Text cannot be pasted into Designer.
Some Adobe product names are changing for upcoming releases. The Designer documentation refers to these products by their previous names
Previous Product Name
New Product Name
Adobe Form Server
Adobe LiveCycle Forms
Adobe Form Manager
Adobe LiveCycle Form Manager
Adobe Reader Extensions Server
Adobe LiveCycle Reader Extensions
Adobe Workflow Server
Adobe LiveCycle Workflow
Adobe Barcoded Paper Forms Solution
Adobe LiveCycle Barcoded Forms
Adobe Document Security Server
Adobe LiveCycle Document Security
Additional Licenses and Copyrights
By installing this product, in addition to the Adobe license terms, you also agree to be bound by the third-party terms provided to you with the Adobe product documentation. Adobe recommends that you review these third party terms.
Copyright © 1998, 1999, 2000 Thai Open Source Software Center Ltd
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)
Copyright © 1988-1997 Sam Leffler
Copyright © 1991-1997 Silicon Graphics, Inc.
Permission to use, copy, modify, distribute, and sell this software [i.e., the TIFF library] and its documentation for any purpose is hereby granted without fee, provided that (i) the above copyright notices and this permission notice appear in all copies of the software and related documentation, and (ii) the names of Sam Leffler and Silicon Graphics may not be used in any advertising or publicity relating to the software without the specific, prior written permission of Sam Leffler and Silicon Graphics.
THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IN NO EVENT SHALL SAM LEFFLER OR SILICON GRAPHICS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Portions © 1994 Symbol Technologies, Inc.
License Language: ICU License - ICU 1.8.1 and later
COPYRIGHT AND PERMISSION NOTICE
Copyright © 1995-2003 International Business Machines Corporation and others
All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, provided that the above copyright notice(s) and this permission notice appear in all copies of the Software and that both the above copyright notice(s) and this permission notice appear in supporting documentation.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization of the copyright holder.
Readme File -- Adobe LiveCycle Designer 7.0 --