These release notes provide information about new features, fixes, and known problems for IBM Daeja ViewONE, Version 5.0.7.
Online version of the release note: https://www.ibm.com/support/pages/node/1109739
Important: The most current version of the file can always be found online.
IBM Daeja ViewONE, Version 5.0.7, makes it easier for business and IT professionals to view large documents and images in their enterprise content management (ECM) solution or in other custom applications, websites, intranets, and extranets.
To download IBM Daeja ViewONE:
Log in to Fix Central.
In the Product Group list, select Enterprise Content Management.
In the Select from Enterprise Content Management list, select the Daeja ViewONE edition that you want to download.
You must have a license to download this software. The file that you download is a product installer for IBM Daeja ViewONE Virtual. When you run the installer, indicate any add-on modules for which you have a license. The installer then enables only those modules you have purchased.
You must run the installer as an administrative user.
Before you install IBM Daeja ViewONE, Version 5.0.7:
To generate a hardware and software requirements report, see System Requirements.
You can run the installer interactively or silently.
To run the installer silently, update the sample response file that is provided with the image archive before you run the installer.
At a command prompt, change to the directory where you extracted the installation image.
To install the viewer interactively, enter the following command:
DAEJA_VIEWONE_5.0.7_WIN_ML.exe
Alternatively, double-click DAEJA_VIEWONE_5.0.7_WIN_ML.exe in
Windows Explorer.
To install the viewer silently, enter the following command:
DAEJA_VIEWONE_5.0.7_WIN_ML.exe -f fully_qualified_path_of_the_response_file
From version 5.0, the default installation path on Windows is
C:\Program Files\IBM\Daeja ViewONE_Virtual
At a command prompt, change to the directory where you extracted the installation image.
To install the viewer interactively, enter the following command:
./DAEJA_VIEWONE_5.0.7_UNIX_ML.bin
To install the viewer silently, enter the following command:
./DAEJA_VIEWONE_5.0.7_UNIX_ML.bin -f fully_qualified_path_of_the_response_file
From version 5.0, the default installation path on Unix is
/opt/IBM/Daeja ViewONE_Virtual
IBM Daeja ViewONE comes with a Toolkit rich in capabilities that enables advanced integration and customization of the viewer by using HTML parameters and JavaScript API methods. For more information on the developer’s guide refer to:
IBM Daeja ViewONE Virtual Developer's Guide
IBM Daeja ViewONE, Version 5.0.7, provides the following new features:
This version of the product offers a new Design Package option.
The new option follows the IBM Carbon Design System specification,
making the IBM Daeja ViewONE Virtual UI more consistent, intuitive,
and providing a more cohesive user experience.
A new HTML parameter, "designPackage", has been introduced
to allow the system integrators to define the preferred style and
layout.
designPackage
| Value | Description |
|---|---|
| classic | Sets the style and layout to the pre 5.0.7 options (default). |
| carbon | Enables the new Carbon style and layout available as of 5.0.7 version. |
The Carbon style and layout only supports the carbon theme.
The Classic UI remains the default option for this release. That is expected
to change to Carbon in a future version.
Document Viewing
In the Carbon layout, the user can switch the view between the following options:
Page View, Thumbnail View, Page and Thumbnail View.
The position of the thumbnails' panel in relationship to the right or left
side, cannot be changed by the end user. It appears by default to the left side,
unless it's otherwise specified by HTML parameter viewMode [1].
The "viewMode" HTML parameter specifies the initial view mode when a
document is displayed. For Carbon the following values are supported:
viewMode
| Value | Description |
|---|---|
| fullpage | The document is opened with the first page visible only (default). |
| thumbsonly | The document is opened with the thumbnails visible only. |
| thumbsleft | The document is opened with thumbnails on the left and the remaining area displays the first page. |
| thumbsright | The document is opened with thumbnails on the left and the remaining area displays the first page. |
Annotations
The annotation types available within the annotation toolbar are grouped in sets,
offering a cleaner look in the UI. Each set has a primary annotation type which
is available in the toolbar. Clicking twice on an annotation group brings up a fly
out with all types shown of the same group. Once a different type is selected, it
gets promoted to the toolbar for that viewer session.
Annotation types can still be disabled using the parameter
"annotationHideButtons". If all but one annotation type, is disabled
within the predefined groups, the remaining annotation type is always promoted as
a single primary one in the annotation toolbar.
The feature of grouping annotation types in predefined sets is on by default, but
could be disabled by integrators using the html parameter
"groupAnnotationsInToolbar".
groupAnnotationsInToolbar
| Value | Description |
|---|---|
| false | Users no longer see grouped annotations. All enabled annotations are shown in a flat list. |
| true | Any enabled annotations are grouped in predefined sets, if there is more than one in a set (default). |
The default position of the toolbar is on the right. The integrator could decide
the position of the annotation toolbar using the HTML parameter:
"annToolbarMode".
annToolbarMode
| Value | Description |
|---|---|
| left | The annotation toolbar appears at the left side of the screen . |
| right | The annotation toolbar appears at the right side of the screen (default). |
[1] The thumbnail panel and the annotation toolbar are always on opposite sides to
each other. The decision on the position of the annotation toolbar, when specified
using annToolbarMode, takes priority over the viewMode settings when values are
thumbsleft or thumbsright. If both parameters are set to left or right, the
settings will only apply to the annotation toolbar and the thumbs panel will default
to the other side of the screen.
The following annotation types are permanently removed in Carbon: Angle, Ruler and
Transparent Highlight. Documents which include pre-applied annotations of these
types, will still display them. The user should still be able to edit them in Carbon,
however the edit options are limited to move and delete actions.
The circle annotation could be drawn by selecting the oval annotation type and
holding the Shift key while drawing it. The square annotation could be drawn by
selecting the rectangle annotation type and holding the Shift key while drawing it.
Sticky Annotation Mode
Any selected annotation is, by default, only available to be applied once in the
document, unless reselected. The viewer offers the option for the annotation to
remain selected and be applied multiple times without the need to click on the
annotation button again. This is known as sticky annotation mode.
Integrators could set this option using HTML parameter "annotationsSticky".
annotationsSticky
| Value | Description |
|---|---|
| true | The sticky annotation mode is ON. |
| false | The sticky annotation mode is OFF (default). |
When set by the integrator, the sticky mode will remain active, even after a page
change, until the user temporarily exits it. The mouse cursor changes to the
precision select ("cross") symbol while the selected annotation type remains
selected to be reapplied.
During the process of adding multiple annotations of the same kind, a user can exit
the sticky mode by clicking on the "select" action at the top of the
annotation toolbar, or press the "esc" key. When the user temporarily exits
the sticky annotation mode, the cursor changes to the normal select ("arrow")
symbol.
The user also temporarily exits the sticky mode, when editing any existing annotation.
That is achieved by right clicking on the annotation on the page to activate the edit
tools for that annotation, click and keep the depressing the mouse click, or select it
using the "select" action from the annotation toolbar.
Permanent Redaction
The behavior of the annotation toolbar, annotations grouping and sticky annotation mode
is the same as described in the annotation section above.
The Sticky Note annotation type is not available in permanent redaction mode.
If annotationDefaults is not set, all annotations except the notes type are burnable and
will be available in the annotation toolbar when burning to TIFF.
The redaction type is available when burning a PDF and the output is a PDF.
DocBuilder
The Carbon Design Package offers a modern user interface with improved interactions:
Within DocBuilder mode, the ability to apply page level modifications is now extended to
include a drag & drop feature. The user can select using the mouse a single or multiple
pages within the thumbnails panel to move to a new position within the same or different
document.
DocBuilder page manipulation actions are only available when thumbnails are displayed, to
enable the user to get a wholistic view of the page layout of the document and the impact
of the page edit actions.
Cut, Copy and Paste actions are visible within the thumbnails panel and are not available
when a document is displayed in Page View. As a result, when the viewer is launched in
DocBuilder mode with "viewMode=fullpage", display the page edit actions are not
visible. Shortcut keys are also disabled in this view.
This version of the viewer introduces a significant improvement to the Excel rendering experience:
Due to the number of factors involved, it is not possible to provide a solution that can detect and replace annotations
back to the original location. The new pagination code will detect and display a warning message
to a user for any Excel spreadsheet it encounters that has been annotated using the previous version of the Excel render process.
There is an HTML parameter to control display of the warning message:
suppressExcelAnnotWarning
This parameter is a boolean and can be set to 'true' (warning message is displayed) or 'false' (no warning message is displayed).
The default for this parameter is 'true'
* a typical example that causes blank page generation is where, for whatever reason, a single cell way off inside the spreadsheet
was populated with data and yet there is no other data in the many columns and rows between the main data set at the beginning of the spreadsheet
and the 'rogue' cell in a location far removed from the main data. This situation could prior to this change cause the viewer to generate many blank pages
for all cells leading up to the last one causing performance issues and potentially impacting the server itself.
When the document load process takes more than 3/4th of a second, a spinner is shown as a graphical indicator. All available action buttons in the toolbar will be disabled during this phase except for the 'Open File' action button.
Improved the time to display the first page of a PDF document with many pages containing heavy text content. When a document is opened, the text content is formatted before the first page is displayed. This could take some time when lots of text needs to be processed. This processing has been changed to be done on demand when the viewer functionality needs it. The processing delay was noticeable in IE. It had a small overhead on other browsers.
All keyboard shortcuts with ctrl keys now also work with cmd, with a limitation that the information and settings dialog must be opened with ctrl-shift-t.
When saving or printing mixed mimtype PageN documents that contain PDFs via the Embedded Print process, the efficiency of the PDF generation is improved.
The version of Java that is targetted is now Java 8. This means that
the IBM Daeja ViewONE Server will no longer run on a Java 6 or Java 7 runtime.
Please note that IBM Daeja ViewONE has supported Java 8+ only since Version 5.0.
When the new showPrintOptionsDialog parameter is set to false, the options window will be skipped when printing and all pages will be printed in the original size along with any annotations.
The parameter is set to true (displaying the options window) by default.
When the print options dialog is hidden, a parameter 'includeStickNotesSummary' will determine if sticky note summary page will be included. The sticky note summary page will be included if the document has sticky note annotations and the 'includeStickNotesSummary' is set to true.
The annotationDateStyle html parameter now takes 3 values: long, medium, short, and stamps the correct date and time format to the <date> and <dateonly> macros, depending on which value is chosen.
Examples for the 'en' locale with the <date> macro:
Long: August 12, 2019, 15:26:45 UTC+1
Medium: Aug 12, 2019, 15:26:45
Short: 8/12/19, 15:26
By selecting either the medium or short values, the timezone is removed from the annotation stamp.
Users can now download and save locally, to a single PDF document, the page array constructed via PageN mode. In Page N mode, the ability to save locally could be enabled using parameter fileButtonSave=true. This parameter determines whether the toolbar includes the action button required to allow the download and Save. The button is called "Save document" when DesignPackage=Classic and "Download Document" when DesignPackage=Carbon. Upon save, a PDF document is created representing the structure of the Page N document. The downloaded PDF is named PageNSaved.pdf.
Added HTML parameter, thumbsPrefetchSize. This parameter can be used to configure the amount of thumbnail sets that will be retrieved in the
background. The actual number of thumbnails in a set depends on the zoom level.
The valid values for this parameter are the numbers zero (0) to seven (7). A value of 0 means no thumbnails are retrieved in the background
in addition to those already displayed on the screen. The default is 2 which means that 2 sets of thumbnails will be retrieved in the
background, in addition to the set already shown. Those will be ready to be displayed as the user scrolls down in the thumbs panel, making
the interaction seamless.
The HTML parameter clientPrefetchSize can be used to configure the amount of pages that will be retrieved in the background.
When this parameter is set to any value greater than zero, the specified number of pages before and after the current page are read-ahead (prefetched).
The valid values for this parameter are 0 to 7, where a value of 0 means no pages are prefetched. The default is 7.
In IBM Daeja ViewONE Virtual 5.0.6, an optimized printing was introduced for PDF documents.
There were a number of restrictions in the use of this optimized PDF printing that have now
been resolved.
For online documentation, see the IBM Daeja ViewONE knowledge center.
IBM Daeja ViewONE Virtual, Version 5.0.7, includes all fixes and features up to and including IBM Deaja ViewONE Virtual Version 5.0.6 iFix 7.
It provides the following additional fixes:
The document pages do not display.
When the viewer is used within a CORS browser environment, the document is not displayed.
Using the developer tools to view the console logging will show an error stating SEC7120: Origin 'yourdomain.com' not found in Access-Controll-Allow-Origin header
and SCRIPT7002: XMLHttpRequest: Network Error 0x80070005, Access is denied.
Affected users: IBM Daeja ViewONE Virtual 5.0.6 iFix 4,5,6 and 7 users
IO26049 EXCEL REDACTION DUPLICATING ON FOLLOWING PAGES WHEN BURN IN FILENET SYSTEM
When redacting an excel document the redaction is duplicated on at least one of the following pages. This is specific to when the excel document is in Page view mode.
Affected users: IBM Daeja ViewONE Virtual users
IO27212 CALLING JAVASCRIPT SETMAGNIFIERINTERNAL WITH FALSE HAS NO EFFECT
Javascript method call setMagnifierInternal(false) has no effect. This call should hide the internal magnfier.
Affected users: IBM Daeja ViewONE Virtual users
IO27315 EMAIL OPENS BUT WHEN CLICKING ON THE ATTACHMENT THE EMAIL IS SHOWN AGAIN. WORKING IN STAND-ALONE BUT FAILS IN ICN
When clicking on the attachment in the email, the email is shown again. Working in standalone but fails on ICN.
Affected users: IBM Daeja ViewONE Virtual 5.0.6 iFix 2,3,4,5 and 6 users
IO27329 EXCEL DOCUMENTS THAT RENDER TO MANY HUNDREDS OF PAGES CAN CAUSE SERVER RESOURCE ISSUES
If an Excel document contains data in one or more cells that makes the overall size of the sheet huge, the viewer will attempt to render every part of that spreadsheet across a large number of pages. But an Excel spreadsheet that takes up hundreds of pages can use up resources on the server to a point where the render thread shows as hung and other users on the same system may experience a significant performance impact.
Affected users: IBM Daeja ViewONE Virtual users
IO27333 EMAIL DOCUMENT IN ENGLISH RENDERS IN WRONG LANGUAGE (JAPANESE)
An email which renders correctly in any mail client is rendered in the viewer with a lists of non-existent attachments in the mail header and the message text is displayed as a set of Japanese and unrecognized escape characters (square empty boxes).
Affected users: IBM Daeja ViewONE Virtual users
IO27383 EMAIL WITH EMOJIS FAILS TO RENDER
An email containing emoji characters fails to display. These emails will now display, but the emojis are displayed as a ‘?’ characters.
Affected users: IBM Daeja ViewONE Virtual users
IO27358 CONTENT EMBEDDED IN PORTRAIT PAGE CAN BE ROTATED IN MULTICONTENT DOCUMENT
When the problem is seen, the actual content of the page (and not just the page) is rotated inside the page itself - so for example, a content element that is a portrait view remains as portrait view but the content inside it is then incorrectly rotated to be a landscape view. This problem can occur when viewing a multi-content document where there is a mixture of portrait and landscape pages in the different content elements. Whether the issue is seen or not depends on the order in which the multi-content element pages are defined.
Affected users: IBM Daeja ViewONE Virtual users
IO27383 EMAIL WITH SPACE SURROUNDING '=' SIGN IN BETWEEN '<' AND '>' FAILS TO RENDER
Emails with space surrounding equal sign between '<' and '>' fail to render. The following error is displayed; 'Unable to display document: Failed to load document, status: An error occurred while retrieving the requested page'.
Affected users: IBM Daeja ViewONE Virtual users
IO27395 WHEN PRINTING USING KEYS CTRL+P OPTION, WE DO NOT SEE PAGE NUMBERS BY DEFAULT
When the keyboard shortcut, Ctrl + P, is used for printing, the default page numbers are not displayed in the 'Pages to Print' field of the print options dialog.
Affected users: IBM Daeja ViewONE Virtual users
IO27398 FILE HANDLERS ARE NOT CLOSED AND LEFT OPEN WHEN CLOSING DOCUMENT OR EVEN AFTER CLOSING DAEJA
File Handlers are not closed and left open when closing document or even after closing Daeja, Resulting in memory issues as the space occupied by the file handlers are not released.
Affected users: IBM Daeja ViewONE Virtual users
IO27410 MEMORY LEAKAGE OCCURS WHEN THE DAEJA VIEWONE VIRTUAL CLIENT VIEWER EMBEDDED IN IFRAME IS RELOADED
When the user navigates away from the viewer page or reloads the viewer, the amount of memory used by the browser increases. After many reloads the browser needs to be closed in order to recover the used memory.
Affected users: IBM Daeja ViewONE Virtual users
IO27449 Data URIs fail to load when docIdProtype is set
When a docIdPrototype has been set, data image URIs fail to load.
The user receives an error message a follows;
'Unable to Load Document ,failed to load document, Status: Unable to register ds with server'
This may be seen in the Datacap Scan workflow.
docIdPrototype will no longer be applied to any data URI.
Affected users: IBM Daeja ViewONE Virtual users
Local Save of mixed source documents produces incorrect file extension on download.
When using local save on mixed source documents, the extension of the resultant file downloaded from the server may be incorrect, causing some files not to be opened.
Affected users: IBM Daeja ViewONE Virtual users
End user can't view RBR TIF document.
When the showprintoptionsdialog parameter is set the user cannot
view the document and gets the error message
'Invalid Auto Redaction configuration: showprintoptionsdialog'.
Affected users: IBM Daeja ViewONE Virtual users
Microsoft Office documents do not show correct number of pages
When viewing large Microsoft Office documents that have references near the beginning of the document, to pages near the end of the document, the number of pages identified can be incorrect. This typically happens in documents with a table of contents at the start of the document.
Affected users: IBM Daeja ViewONE Virtual users
Cursor reverts to default when drawing sticky text annotations
When drawing sticky text annotations, a crosshair cursor appears to draw the annotation. After drawing the first annotation, the cursor reverts back to the default cursor instead of the crosshair. At this time the annotation is still 'sticky' and more annotations can be drawn.
Affected users: IBM Daeja ViewONE Virtual users
Annotation transparency is removed when a color is applied
The transparency is removed when a new line or fill color is applied to an annotation that has line or fill transparency.
Affected users: IBM Daeja ViewONE Virtual users
When running Daeja ViewONE 5.0.7 as a component inside IBM Content Navigator, the minimum supported version of ICN is 3.0.7, unless stated otherwise by the specific ICN release.
Go to the page at Software Product Compatibility Reports to create a high-level report for operating systems, hypervisors and prerequisites.
When printing PDF documents with annotations, the annotations are embedded in the
downloaded PDF document as native PDF annotations. This reduces the time taken
to print documents, especially large documents.
This process currently only applies to printing PDF documents when 'Print Original Size'
is selected in the print settings. If this is not selected or the printed document contains
other file formats, the print process completely flattens the content of each page.
The time it takes to prepare a PDF with annotations for print using the optimized print
depends on the total number of annotations. In most cases you need to have several hundreds
of annotations in a single document before the time difference becomes noticeable.
With the optimized print any annotations created in IBM Daeja ViewONE Virtual are embedded
into the document as native PDF annotations. Therefore they are recognized as active annotations
when the PDF is viewed by tools that support editing of PDF documents. If this document is
subsequently viewed by IBM Daeja ViewONE Virtual, any annotations will be treated as static
content where loading a document with pre-applied native annotations cannot be edited.
To prevent document or annotation modification appropriate security would need to be set via a
tool that supports editing or via some PDF printers.
Sticky Notes
Sticky Note annotations will appear on top of other annotations regardless of z-order.
Line Width
The maximum line width of native annotations is 12pt and will be limited to this for print output.
Solid Text
If a solid text annotation is set to be semi-transparent the fill background and the text will
become semi-transparent, previous behavior left the text solid and only the fill became
semi-transparent.
Image Stamps
Image stamp annotations will appear underneath any other annotation types regardless of the z-order.
This is due to the fact that they added to the content of the PDF and not as separate native PDF
annotations.
The optimized PDF print does not occur in the following circumstances:
As of IBM Daeja ViewONE Virtual Version 5.0.6 the following annotation types are deprecated:
These annotation types will be removed in a future version of the product.
As of IBM Daeja ViewONE Virtual Version 5.0.3, the default value for parameter emailRenderer is set to '2' which represents the email module that allows for paginated output. See more details for this module below. As of IBM Daeja ViewONE Virtual Version 5.0.6, the ability to switch the email module to the alternative value "1" has been deprecated. The value will be removed as a valid setting for the parameter in a future release.
The email module that produces paginated output is now the default setting for the standalone product. This email module supports the display of EML (MIME RFC 822) and MSG (Microsoft Outlook and Exchange) formats as paginated content, and allows for streaming and redaction of emails. It requires the IBM ViewONE Office Module to be licensed. To redact emails, the IBM ViewONE Permanent Redaction module is also required. When opening emails that have annotations saved using the older email rendering mechanism, the HTML parameter 'emailUseAnnotationDefinedModule' defines the behavior.
The 'emailUseAnnotationDefinedModule' parameter can have the following values:
*always: The default behavior is to always attempt to use the renderer that is defined in the annotation.
*never: The renderer that is defined in the annotation is never used. Instead, the email is opened using the renderer specified in the viewer. This may cause the annotations to move. The user will be notified that 'The annotations on this document were saved with a different version of the viewer. Annotation may have moved and will need checking'. The annotation save button will be enabled and user will be prompted to save before they leave the document unless the 'annotationAutoPrompt' HTML parameter has been set. The 'annotationAutoSave' HTML parameter does not work for this annotation change.
*prompt: The user receives a prompt when annotations were created using a different renderer, giving them the option to open using the renderer defined for the viewer (Yes) or attempt to open with the renderer that is specified in the annotation (No). If the user click Yes they will then be notified that 'The annotations on this document were saved with a different version of the viewer. Annotation may have moved and will need checking'. The annotation save button will be enabled and user will be prompted to save before they leave the document, unless the 'annotationAutoPrompt' HTML parameter has been set. The 'annotationAutoSave' HTML parameter does not work for this annotation change.
The document will be built with the source document as it is saved in the repository. The document is also built by using the annotations that are saved in the repository, unless annotations have been edited. The following scenarios explain the effects of this behavior:
Result: The document currently displayed in the viewer differs from the newly built document in the system. To prevent this issue occurring, the master document should be locked or checked out when it is retrieved for document builder.
Note Versioned documents will not be affected by this issue. This will only affect situations where the document that a URL refers to has changed.
Result: The document currently displayed in the viewer differs from the newly built document in the system. To prevent this issue occurring, the master document should be locked or checked out when it is retrieved for document builder.
When in document builder mode, the option to restore annotations is not supported. The following scenario explains the effects of this behavior:
Scenario 1:
Result: The user cannot reload the annotations from the server. Newly created annotations and edited annotation edits remain.
To restore any newly created annotations, the user must take the following steps:
As problems are discovered and resolved, the IBM Support team updates the Support site. By searching the Support site, you can quickly find workarounds or solutions to problems.
The following links open queries for IBM Daeja ViewONE documents on the IBM Support site:
For information on the supported file formats refer to the tech note below. Please note that this is a live document and might get updated frequently. https://www-01.ibm.com/support/docview.wss?uid=ibm10730429
IBM Daeja ViewONE Virtual is designed to support as many file types as possible. However, the product is not able to render every type of file with the same accuracy as native applications, such as Microsoft Word. The flexibility of the viewer can lead to differences in the way that the documents are displayed between the native application and the viewer. The severity of the differences varies depending on the complexity of the file type. In particular, PDF files and Microsoft Office files are difficult to render with complete accuracy in a universal viewer.
For additional information on IE/Edge limitations, refer to the following tech notes:
Excel spreadsheet load times are impacted based on the size and complexity of the Excel document. In order to improve load times, IBM Daeja ViewONE does support tuning capabilities, such as breaking up the Excel document presentation into multiple pages. Please be aware, as this behavior may not be optimal for your end user viewing experience.
After a document is permanently redacted and the user selects Download, they are
normally prompted to save the document with a file name based on the original
un-redacted document. For instance, mypresentation.ppt will default to
mypresentation.tif. In this version the user might be prompted with a filename
such as 41f96b20b97f431ebd4efd85245f1f72.tif instead. The user can still
change the name to something more meaningful.
If a pageN document is open in the viewer, the user cannot switch to document builder mode. The user remains in the edit mode in which the document was opened. The following scenario explains the effects of this behavior:
Scenario 1:
Result: This switch is not permitted and the user will stay in their current mode.
To enter document builder mode, the user must close the pageN document and then switch to document builder mode.
DocN documents are not supported in conjunction with document builder mode. The combination of these features may result in unusual and/or unexpected behavior.
Document builder is able to support TIFF and PDF files with the exception of email attachments. TIFF and PDF files that are attached to emails cannot be used as source files for a new document.
PDF files with access control flags set by the owner of the document cannot be used as a source document for document building where they require a password to view the document or where the owner has indicated that the content may not be copied.
Annotations that have the semi-transparent property set to true, the transparent property set to true and a fill color set can appear to blend the line and fill colors near the edges.
Annotations that have the transparent property set to true and a fill color set to black are not printed transparent for non PDF documents. When printing PDF documents, with 'Print Original Size' selected, these annotations are printed with transparency applied.
http://www.ibm.com/legal/copytrade.shtml
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Other company, product, or service names may be trademarks or service marks of others.
The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.
Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions: