Adobe LiveCycle Designer
Version 8.0
|
Readme File |
October 2006 |
Copyright 2006 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(R) LiveCycle(R) Designer.
Tabbing order cannot be altered on forms that were originally created in Adobe Designer 6.0
The tabbing order cannot be altered on forms that were originally created in Adobe Designer 6.0. This issue specifically applies to forms that contain radio buttons and exclusion groups. LiveCycle Designer 8.0 does not retain the old tab order. Attempting to change the tab order causes unexpected results.
Inserting a table into a cell that is set as a subform does not automatically resize the table to fit the cell
If you want a table cell to act as a subform and contain more objects (such as a button and a nested table) and you want the nested table to automatically fit inside the cell, insert a subform outside of the main table, create the table inside this subform, and then click and drag the subform containing the table into the cell. The parent table will automatically resize to fit the contents.
Row shading and using the instanceManager.removeInstance method
If you have set row shading and you have a script that removes rows using the instanceManager.removeInstance method, the row shading does not get recalculated after a row or set of rows is removed. To fix this issue, you can copy the row shading script from the Script Editor and paste it after the script that removes the rows. To locate the row shading script, select the row. The script should appear in the Script Editor if Events With Scripts is selected in the Show list.
Note: To improve performance, avoid using row shading in a dynamic table.
Table column width not defined when a PDF file is imported
When you import a PDF file that contains tables, the column width is not defined. This may cause the table to spill out of the page. If the table is displayed incorrectly, open the PDF file in Adobe Acrobat(R) Professional or Acrobat Standard,and use the View>Navigate Tags>Tags command to remove the tags from the PDF file, and then save the file. You can then import the PDF file into LiveCycle Designer.
Locking field objects applies to the Layout Editor
Selecting Edit > Lock Fields prevents you from selecting, moving, or modifying field objects while working in the Layout Editor. After locking the fields on the Layout palette, you can still select an object from the Hierarchy palette and change its properties.
Syntax for typing ( ) after Arabic function names
In English, the correct syntax for typing values after a function name is to enter opening and closing parentheses ( ). In Arabic and Hebrew, which are languages that read from right to left, typing '( )' prohibits the user from entering further values after the function name. To solve this problem, type the function name, and then begin the subsequent phrase with the Arabic or Hebrew ‘)’ and close with the English ‘)’. For example, typing ‘function name ))’ will result in ‘function name ( )’ when using Arabic or Hebrew characters in the function name.
Documentation for the Specific Item Values property is incorrect
The following topics in LiveCycle Designer Help state that the default values will be sequential integers starting at "0" for the first list item:
However, the default value starts at "1".
- Drop-down list properties in the Binding tab
- List box properties in the Binding tab
- To specify list item values for a drop-down list or list box
Connecting to a WSDL using HTTPS
LiveCycle Designer 8.0 does not support secured web services. If you try to create a data connection to a WSDL using HTTPS, you will get an error message.
Relative bindings when nodes defined at different levels in the dataDescription share the same name
When LiveCycle Designer generates a form from a schema, it should put "$." in front of relative dataRef SOM expressions to ensure that scope matching does not occur. This is necessary in the case where a schema defines optional elements with the same name at different places in the hierarchy. This can result in scope matching during data binding that finds the wrong element. For example:
<xxx> (bound to subform)
<name> (bound to field)
<yyy> (bound to subform)
<name> (bound to field)
In this situation, the fields should have “$.name” to prevent scope matching finding and binding to the wrong <name> element. If a schema defines data in this way and there are resulting problems, the form author can manually add “$.” in the XML Source View to the relative bindings. For example, the form author might change the source as follows:
<bind match="dataRef" ref="name"/>
to
<bind match="dataRef" ref="$.name"/>
Restore default objects in the Library palette does not restore objects in the Standard tab
If you remove the Standard group from the Library palette, and then select Restore Default Objects for All Groups, the Standard group folder will be restored but it will contain no objects.
Clicking the Preview PDF tab opens Acrobat when the Display PDF In Browser option is unselected
When the Display PDF In Browser option is not selected in the Edit > Preferences > Internet dialog box in Acrobat, clicking the Preview PDF tab in LiveCycle Designer starts Acrobat in its own window rather than embedded within the Preview PDF tab. By default, the Display PDF In Browser option is selected.
Preview PDF and new forms
By default, LiveCycle Designer displays a new (unsaved) form as a static PDF form. To display an unsaved form as a dynamic PDF form, you must change the Tools > Options > Document Handling > Default File Type for New Forms setting to Adobe XML Form File <XDP>. You must also change the File > Form Properties > Defaults > XDP Preview Format setting to one of the dynamic form options.
Preview PDF and imported forms
When you import a PDF form as artwork, LiveCycle Designer retains the original format of the form. If you want to preview the form in a different format, you must save it in that format and then preview it.
The New Form Assistant in the English version of LiveCycle Designer does not support characters for other languages such as Arabic, Hebrew, Thai, and Vietnamese
The New Form Assistant window does not support characters from other languages.If you are creating a form for another language, use the respective language version of LiveCycle Designer. If you want to set up a specific object for a different language, you can create the form using the New Form Assistant, and then change the font later by selecting the object and selecting a locale on the Field tab of the Object palette.
Fonts used to create a form using LiveCycle Designer 8.0 are substituted when opened in Acrobat
Not all fonts that are installed with LiveCycle Designer 8.0 are installed with Acrobat 7.0.5 and Adobe Reader 7.0.5. When you open a form in Acrobat that uses fonts that are not installed, the missing fonts are substituted and the layout may be different from LiveCycle Designer 8.0. You can install the missing fonts or select Embed Fonts to embed the form fonts in the saved PDF form.
Greek small letter final sigma (U+03C2) appears incorrectly
The U+03C2 character appears as the crossed rectangle in static text objects when the font is Myriad(R) Pro. To avoid this problem, you must embed the form fonts when you save the form. Select File > Save As, and then select the Embed Fonts save option.
Japanese text incorrectly displayed in the XML Source tab and the Script Editor
The default font in the XML Source tab and the Script Editor is currently set as Courier New. As a result, Japanese text is incorrectly displayed in both locations. To display the font correctly, select a font that supports Japanese characters such as MS Gothic. Select Tools>Options>Workspace, and then select FormCalc Syntax Formatting or JavaScript Syntax Formatting to set the font in the Script Editor or select XML Source Syntax Formatting to set the font in the XML Source tab.
Documentation for choosing fonts
In LiveCycle Designer Help, the topic “Choosing fonts for performance” incorrectly describes fonts that are always available with Adobe Reader. The correct wording for the topic is as follows:
The following fonts are always available in Adobe Reader and do not need to be embedded to prevent font substitution:
- Adobe Pi Std. Adobe Sans MM, Adobe Sans MM, Adobe Serif MM
- Courier Std, Courier Std Bold, Courier Std Bold Oblique, Courier Std Oblique
- Minion(R) Pro Bold, Minion Pro Bold It, Minion Pro It, Minion Pro Regular
- Myriad Pro Bold, Myriad Pro Bold It, Myriad Pro It, Myriad Pro Regular
- Symbol (Type 1)
The Phone Number-International custom object is now called Phone Number - UK
The Phone Number - International custom object is now called Phone Number – UK. In LiveCycle Designer Help, the topic "Using LiveCycle Designer > Working with Objects > Using objects > Using custom objects > About custom objects, incorrectly lists the object as Phone Number – International.
Tooltip value is ignored when screen reader precedence is set to Custom Text or another non-tooltip setting
If the screen reader precedence is set to a value other than tooltip, that other value is used as the tooltip in the saved PDF form and the tooltip value in LiveCycle Designer 8.0 is ignored.
Signature Handler verson documentation
The Signature Handler tab does not contain a version option. LiveCycle Designer Help incorrectly displays topics about a signature handler version setting. The following topics contain information about the version setting:
- handler
- Signature Handler tab (Document Signature Settings/Sign Data and Submit Settings dialog box)
Converting PDF names to valid variable names in LiveCycle Designer
When importing PDF documents, LiveCycle Designer replaces invalid characters in a variable name with an underscore (_). If the first character of a variable name is not valid, it prepends an underscore (_) to the name. If other characters are invalid, they are replaced with an underscore (_). For example, "My[Var" becomes "My_Var" (substitution of an invalid character), and "1MyVar" becomes "_1MyVar" (prepending of an underscore (_) because digits are not valid as a first character), "[MyVar" becomes "__MyVar" (prepending of an underscore (_) because the first character ([) is not valid as a first character and subsequent substitution of the "[" character because it is not valid in any position in a variable name. Note that variable names that differ solely by their first character (that is, "]MyVar" and "[MyVar") will end up with the same name "__MyVar" if the first character is not valid.
Barcodes and Paper Forms Barcode Object
Static PDF417, QR Code, and Data Matrix barcodes transform into Paper Forms Barcode
Whenever you add a custom script to a static PDF417, QR Code, or Data Matrix barcode, the barcode automatically becomes the dynamic barcode of the same symbology. That is, the barcode transforms into Paper Forms Barcode of PDF417, QR Code, or Data Matrix symbology, respectively. Once such a transformation occurs, you cannot change the barcode back to a static barcode. You must redraw the static barcode.
Barcode Scanning Method setting in LiveCycle Designer 7.0 form defaults to Custom in LiveCycle Designer 8.0
If a LiveCycle Designer 7.0 form contains a barcode with the Scanning Method set to either Document Scanner, Hand-held Scanner, or Fax Server and you open it in LiveCycle Designer 8.0, the Scanning Method setting will default to Custom.
A paper forms barcode object may not correctly handle data from fields with the same name
Paper forms barcode objects do not write field occurrence numbers to the data when the data is encoded in XML format. If a paper forms barcode object collects data from two or more fields with the same name, the data does not include information to distinguish the fields. If a paperforms barcode will encode data from like-named fields, use tab-delimited format for encoding the data.
Incorrect message appears for drop-down list and list box objects when paper forms barcode object is on a form
When you add a drop-down list or list box object to a form that contains 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 disappears 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 barcodes of some sizes designed in LiveCycle Designer 8.0 do not display correctly in Acrobat 7.0.3
If you author a paper forms barcode in LiveCycle Designer 8.0 and open this form in Acrobat versions earlier than 7.0.5, the paper forms barcode may not be visible even if the form has been saved as Acrobat 7.0 compatible. This can happen when a paper forms barcode is larger than the older version may support. Try to reduce the size of the paper forms barcode field and test with the older versions of Acrobat to make sure the paper forms barcode is visible.
Paper forms barcodes designed in LiveCycle Designer 8.0 and viewed in Acrobat or Adobe Reader versions earlier than 7.0.5 display two captions
If you author a paper forms barcode in LiveCycle Designer 8.0 and open this form in Acrobat versions earlier than 7.0.5, you will see two captions for the barcode. You can remove the caption if it is not required for your form.
Paper forms barcodes designed in LiveCycle Designer 7.0, saved as a dynamic PDF form, and then viewed in Acrobat 8.0 or Adobe Reader versions 8.0 display two captions.
If you save a LiveCycle Designer 7.0 barcoded form as a dynamic PDF form and open it in Acrobat 8.0 or Adobe Reader 8.0, you will see two captions under the paper forms barcode. In LiveCycle Designer 8.0, try saving the form as an Acrobat 8 (Dynamic) XML Form File (*.pdf). Or, in LiveCycle Designer 7.0, try saving the form as a Static PDF Form File (*.pdf). Note that you do not have to save a form as dynamic to make it a fillable form. Both static and dynamic forms are fillable PDF forms.
When paper forms barcodes have more data than they can handle, they show as white spaces in Acrobat versions 7.0.1 through 7.0.3
In Acrobat versions 7.0.1 to 7.0.3, a LiveCycle Designer form with a paper forms barcode in it may display the barcode as white space instead of a gray box when it contains too much data.
Barcode capacity
You must test your forms to the full capacity in both Adobe Reader and in Acrobat to ensure that barcodes are large enough for all required data to be captured in full by both applications. This can be done by filling each field with realistic entries of maximum length and ensuring that the barcode does not turn gray. Reader testing should be performed on documents that have had the LCRE Barcoded Forms right applied to them.
Acrobat and Adobe Reader requirements for forms containing different 2D dynamic barcode symbologies
End users filling a form that contains a QR Code or DataMatrix barcode require Acrobat 7.0.5 or later, or Adobe Reader 7.0.5 or later. Do not save the form as "Acrobat 6 Compatible" or "Acrobat 7 Compatible." This is true for forms created in LiveCycle Designer 8.0 and also for the Acrobat forms imported into LiveCycle Designer.
In addition, end users filling a form that contains a PDF417 barcode require Adobe Reader 7.0 or later, or Acrobat 7.0 or later to fill the form. Do not save the form as Acrobat 6 (Static) PDF Form (*.pdf).
Code QR renamed to QR Code
The barcode Code QR now appears as QR Code in LiveCycle Designer 8.0. The documentation currently refers to Code QR incorrectly. Forms created using previous versions of LiveCycle Designer will also display the barcode as Code QR in LiveCycle Designer 8.0.
The target web page does not open inside the current document when using the gotoURL method
Acrobat ignores the param2 parameter of the gotoURL method, which appends the resulting pages to the current document. Instead, the document is always opened by the URL in a new document.
Custom Screen Readers do not read custom text for static text objects in PDF forms
When you specify custom screen reader text for a static text object, LiveCycle Designer does not warn you that the custom text will not be read aloud in Acrobat.
Format loss of imported forms
When you paste a text object into a form design, the object does retain the text formatting. The formatting is restored once you save, close, and then reopen the form.
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 2006 Adobe Systems Incorporated. All rights reserved.
Portions based in part on the work of the FreeType team.
Portions (C) 1994 Symbol Technologies, Inc.
This software is based in part on the work of the Independent JPEG Group.
Portions (C) 1995-2002 Jean-loup Gailly and Mark Adler.
Copyright (c) 1998-2000
Dr John Maddock
Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Dr John Maddock makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.
Copyright (c) 1994
Hewlett-Packard Company
Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and
this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.
Copyright (c) 2001 by Andrei Alexandrescu
This code accompanies the book: Alexandrescu, Andrei. "Modern C++ Design: Generic Programming and Design Patterns Applied". Copyright (c) 2001. Addison-Wesley.
Permission to use, copy, modify, distribute and sell this software for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation.
The author or Addison-Welsey Longman make no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.
"The contents of this file are subject to the Netscape Public License Version 1.1 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.mozilla.org/NPL/
Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License.
The Original Code is Mozilla Communicator client code, released March 31, 1998.
The Initial Developer of the Original Code is Netscape Communications Corporation. Portions created by Netscape are Copyright (C) 1998-1999 Netscape Communications Corporation. All Rights Reserved.
Copyright (c) 1988-1997 Sam Leffler
Copyright (c) 1991-1997 Silicon Graphics, Inc.
Permission to use, copy, modify, distribute, and sell this software 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.
ICU4J license - ICU4J 1.3.1 and later
COPYRIGHT AND PERMISSION NOTICE
Copyright (c) 1995-2001 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.
ICU License - ICU 1.8.1 and later
COPYRIGHT AND PERMISSION NOTICE
Copyright (c) 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.
All trademarks and registered trademarks mentioned herein are the property of their respective owners.
The Apache Software License, Version 1.1
Copyright (c) 1998-2000 The Apache Software Foundation. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment:
"This product includes software developed by the Apache Software Foundation (http://www.apache.org/)."
Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.
4. The names "Xerces" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org.
5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.
THIS SOFTWARE IS PROVIDED ''AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, International Business Machines, Inc., http://www.ibm.com. For more information on the Apache Software Foundation, please see <http://www.apache.org/>.
Copyright © 1991-2005 Unicode, Inc. All rights reserved. Distributed under the Terms of Use in http://www.unicode.org/copyright.html.
Permission is hereby granted, free of charge, to any person obtaining a copy of the Unicode data files and associated documentation (the "Data Files") or Unicode software and associated documentation (the "Software") to deal in the Data Files or Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Data Files or Software, and to permit persons to whom the Data Files or Software are furnished to do so, provided that (a) the above copyright notice(s) and this permission notice appear in all copies of the Data Files or Software, (b) both the above copyright notice(s) and this permission notice appear in associated documentation, and (c) there is clear notice in each modified Data File or in the Software as well as in the documentation associated with the Data File(s) or Software that the data or software has been modified.
THE DATA FILES AND SOFTWARE ARE 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 THE DATA FILES OR 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 these Data Files or Software without prior written authorization of the copyright holder.
Unicode and the Unicode logo are trademarks of Unicode, Inc., and may be registered in some jurisdictions. All other trademarks and registered trademarks mentioned herein are the property of their respective owners.
Copyright (C) 1995-1997 Eric Young (eay@mincom.oz.au) All rights reserved.
This package is an SSL implementation written by Eric Young (eay@mincom.oz.au).
The implementation was written so as to conform with Netscape’s SSL.
This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution including RC4, RSA, lhash, DES, etc... The SSL documentation included with this distribution is covered by the same copyright terms except the holder is Tim Hudson (tjh@cryptosoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed.
If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgement: "This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
The word 'cryptographic' can be left out if the routines from the library being used are not cryptographic related :-).
4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publicly available version or derivative of this code cannot be changed; i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License.]
Readme File -- Adobe LiveCycle Designer 8.0 --