Welcome to Adobe® Reader® 7.0.5 ReadMe file. Adobe Reader is the free viewing companion for Adobe applications that produce Adobe Portable Document Format (Adobe PDF) files. To create, enhance, review, edit, and share information in Adobe PDF files, learn more about Adobe Acrobat 7.0 Professional and Adobe Acrobat 7.0 Standard by visiting www.adobe.com/products/acrobat.
Click the following links to learn more about Adobe Reader 7.0.5:
Make sure that your system meets the minimum requirements to run Adobe Reader 7.0.5 for Linux®:
Choose the installation method you prefer, as described below.
2. Enter the root password when prompted and click OK.
3. Click Continue in the Complete System Preparation dialog box.
2. Click Install Package with YaST.
3. Enter the root password when prompted and click OK.
By default, Adobe Reader is installed at /usr/local/Adobe/Acrobat 7.0. You can, however, specify a different location.
2. Use the cd command to switch to the directory where the RPM package resides.
3. Run the following command as an administrator or root:
rpm -i AdobeReader_enu-7.0.5-1.i386.rpm
To uninstall Adobe Reader 7.0.5, run the following command as root:
After installing Adobe Reader, you will be prompted to install the browser plug-in (see See To install the browser plug-in: for instructions).
2. Use the cd command to switch to the directory where the Tarball archive resides.
tar -zxvf AdobeReader_enu-7.0.5-1.i386.tar.gz
4. In the newly created AdobeReader directory, run the
INSTALL
script.
5. Add
<adobe_install_dir>/bin
to the
PATH
environment variable to allow browsers to launch Adobe Reader, where <adobe_install_dir> is the installation directory of Adobe Reader 7.0.5.
Note: To install in a pre-defined directory, use
--install_path=<dir>
.
By default, Adobe Reader is installed at /usr/local/Adobe/Acrobat 7.0. You can however, specify a different location.
To uninstall Adobe Reader, simply delete the directory where it was installed.
Run the acroread script, which resides in the <adobe_install_dir>/bin directory, where <adobe_install_dir> is the installation directory of Adobe Reader 7.0.5.
Adobe Reader 7.0.5 comes with a browser plug-in that allows you to view and use PDF files in a browser window. The plug-in is compliant with the Netscape Gecko API and works with all browsers that support Gecko (including Firefox 1.0 and Mozilla1.7.3 and 1.8).
You need to install the browser plug-in after installing Adobe Reader. It is not automatically installed with the RPM installer. Before installing, please read "<INSTALL_PATH>/Browser/HowTo/<language>/Browser_Plugin_HowTo.txt" for details.
If you want to install the plug-in for a particular browser, make sure that you have write permissions to the browser's directory.
2. Enter the following commands to run the install_browser_plugin script:
This version of Adobe Reader supports the entry and display of Hebrew, Arabic, Thai, and Vietnamese text. This version contains options for controlling the right-to-left languages Arabic and Hebrew in forms and digital signatures:
Enabling right-to-left language options displays the user interface elements for controlling paragraph direction, digit style, and ligature:
Note: Right-to-left language options are enabled by default under Arabic and Hebrew regional settings (when either the locale or the keyboard layout is set to one of these languages).
2. In the Preferences dialog box, select International Categories and select Enable Right-To-Left Language Options.
If you experience problems when running Adobe Reader 7.0, this section may help you to determine their cause. For general product information and additional troubleshooting information, visit the Adobe Product Support Knowledgebase at www.adobe.com/support, or choose Help > Online Support in Adobe Reader.
Unable to open Policy Server secured documents.
If the Policy Server certificate is not installed, a message displays indicating that there was a problem communicating with the service. To solve this problem, install the server certificate using the command line
acroread -installCertificate <URL> <PORT>
as shown on the console.
MIME type registrations and icon associations are not reflected after installation. Restart your desktop session for the changes to take effect. Please note that this feature is only available for installations done using root privileges.
Help and How To windows are not available when you open Adobe Reader from within a web browser. To access the Help button or the How To window from a task button, start Adobe Reader from outside a web browser.
Command-line RPM installation fails on SuSE 9.2.
Using the
rpm -i AdobeReader_enu-7.0.5-1.i386.rpm
command to install Adobe Reader 7.0.5 on SuSE 9.2 does not succeed and reports a failed dependency on
libcurl
. To solve this problem, install Adobe Reader using
rpm -i --nodeps AdobeReader_enu-7.0.5-1.i386.rpm
.
Chinese, Japanese, and Korean bold characters appear blurred. If the text was created in an application that used synthetic bolding, white areas or breaks in the text may appear when the text is magnified. To avoid this problem, enable the Smooth Text and Use CoolType options in the Page Display preferences.
The Find command doesn't locate Unicode characters. Before searching for Unicode characters in a PDF file, add "\u" before the Unicode character in the search dialog box. For example, to search for the Unicode equivalent of the ASCII letter A, type \u0041 in the dialog box.
Unable to create comments or bookmarks using the Hong Kong character set. Because the Hong Kong character set is not part of the standard system fonts, you cannot comment or create bookmarks using those characters. To solve this problem, install the Chinese Traditional Language pack (the Honk Kong character set is an extension of the Chinese Traditional set).
Adobe Reader doesn't run correctly.
Adobe Reader 7.0.5 needs access to the
pwd
command. As a result, Adobe Reader does not run correctly from a directory where the
pwd
command fails. To solve this problem, make sure that the
pwd
command runs in the
bin/
directory of the Adobe Reader 7.0.5 installation directory.
Adobe Reader retains the preferences of a previous version. Before you run Adobe Reader 7.0.5 for the first time, you may want to remove the directory $HOME/.adobe, where $HOME is the user's home directory. Removing this directory ensures that Adobe Reader used the default preference settings when you launch it for the first time.
Adobe Reader can't open recently viewed files. Opening recently viewed files requires that the files remain in the same location and have the same names. If you open a file in a session using an automounter and the automounter quits unexpectedly, attempting to reopen the file by selecting it in the File menu will display an error message. This error also occurs when the file is moved or renamed, or if Adobe Reader is run from a different computer that does not have the same file system mounted. To solve this problem, either repoen the files using the File > Open command, or make sure that the volumes on which the files reside are mounted and accessible to Adobe Reader.
Temporary files appear in the list of recently viewed files.
To prevent temporary files (such as files opened from the web) from appearing in the list of recently viewed files in the File menu, set the mailcap entry as follows:
application/pdf;acroread -tempFile %s
.
Adobe Reader preferences are not retained. If the directory containing Adobe Reader preferences is not writable, the preferences cannot be saved. To solve this problem, make sure that the $HOME/.adobe directory, where $HOME is the user's home directory, is writable.
Password-protected PDF files cannot be printed to PostScript from the command line. Even though password-protected files can be printed from Adobe Reader, you cannot print the files to PostScript from the command line.
PDF files don't print.
When you print a PostScript document using the
1p
command, a symbolic link is created from the spool file to the file being printed; the link saves space on the file system, but causes a problem when printing from Adobe Reader. To solve this problem, include the
-c
option (copy) with the
lp
or
1pr
command in the Print dialog box. This forces the
pd
process to copy the file to the spool area instead of making a symbolic link.
Adobe Reader search is slow and doesn't find files. To create full text search indexes that can be reliably used across platforms, you must use the ISO 9660 file naming conventions for the indexed files (8.3 uppercase, restricted character set). Otherwise, Adobe Reader attempts to guess what the UNIX file names are, which causes delays in searching and may result in files not being found.
Unable to submit forms from web browsers. You cannot submit forms on the web if the web browser warns that a lock file has been found, meaning that another instance of the browser is running. To solve this problem, make sure that only one instance of the browser is running. If a lock file is left after a browser crashes, simply delete the file.
Error message appears during startup. If the message "Error while loading shared libraries: libJP2K.so: cannot restore segment prot after reloc: Permission denied" appears, libraries are being blocked by SELinux because of insufficient permissions. Either run the script <INSTALL_PATH>/Reader/Patch/selinux_patch with root permissions to set up the file contexts properly or, if the problem persists, turn off SELinux by typing the command "setenforce 0" under root permissions
Third party applications do not launch when running Adobe Reader 7.0 using 32-bit emulation on a 64-bit machine. When running the reader in 32-bit emulation mode on 64-bit machines, the various applications that the reader interacts with also need to be 32-bit binaries running in the emulation mode.
Adobe Reader 7.0 crashes during launch on SuSE 10.0 and Asianux 2.0 IA32. This problem exists because of the presence of a conflicting version of libscim (Smart Common Input Method Library). This is a documented issue on Novell's bugzilla (https://bugzilla.novell.com/show_bug.cgi?id=85416). The workaround is to perform 'export GTK_IM_MODULE=xim' before launching acroread.
Read Out Loud Menu Options are disabled.
Adobe Reader supports gnome-speech-0.3.1 version and later. For earlier versions, the menu options are disabled (grayed out). Check the version of gnome-speech installed on your machine by running the following command:
rpm -qa | grep -i gnome-speech
. If the gnome-speech version is compatible with reader, run '
test-speech
' command. If you can't select and play through a speech server install a compatible speech server to gnome-speech.
Read Out Loud does not work after upgrading gnome-speech.
Test using '
test-speech
' command if the gnome-speech is upgraded correctly. Afterwards, make a link to the installed libORBit-2.so.X, libgnomespeech.so.X, libbonobo-activation.so.X and libbonobo-2.so.X in <INSTALL_PATH>/Reader/intellinux/lib with the names 'libORBit-2.so', 'libgnomespeech.so', 'libbonobo-activation.so' and 'libbonobo-2.so'.
GB18030. If you paste the CJK-A character U+3400, U+3500, U+3600, or U+3700 into the search field and perform a search, the search fails even if the character exists in the PDF document you're searching. Type the character in the search field instead of pasting it.
Adobe Reader fails to launch on Red Flag Linux 4.1 because of a problem in GLib. This failure occurs when trying to load accessibility-related modules. Upgrading to a later version of GLib solves this problem.
Scripting between the HTML page and Adobe Reader does not work when embedded inside the browser. This issue exists because of the limitation of the browser. Upgrade to a browser version that supports scripting from plug-ins to solve the problem.
PPKLite.api fails to load. PPKLite requires the installation of the OpenLDAP package and fails to initialize in its absence. If you get this error when acroread starts, you need to install the LDAP libraries (OpenLDAP package). If PPKLite still fails to load, make a link to the installed libldap.so.X and liblber.so.X in <INSTALL_PATH>/Reader/intellinux/lib with the names 'libldap.so' and 'liblber.so'.
Some system fonts do not appear in Document/Properties Window/Toolbar.
Adobe Reader searches for system fonts in the directory list specified in the
PSRESOURCEPATH
environment variable, in addition to some predefined system directories. If your system has several additional font directories that Adobe Reader may not be searching, you can add those directories to the
PSRESOURCEPATH
environment variable before launching Adobe Reader. If the required fonts are not embedded in the document, checking the Document > Use Local Fonts option, Adobe Reader picks up the fonts from the system as specified by the
PSRESOURCEPATH
variable.
Stretching or skewing of page text on some systems. This problem can be resolved by going to Edit > Preferences, clicking the Page Display tab, and setting Custom Resolution to the currently displayed System setting.
Search does not complete for socket files.
If the specified search path contains a socket file (typical paths are
/tmp
or
$HOME
), the search does not complete. Make sure that the specified path contains only regular files and no socket files.
Trouble sending mail using Mutt.
If a terminal window flashes and disappears when the selected email client is mutt, add the line
set autoedit=no" to $HOME/.muttrc
to enable sending mail using mutt.
Evolution crashes when sending mail. This issue happens with earlier versions of Evolution. If Evolution crashes on sending mail (when Evolution is the selected Email client), try keeping Evolution running in the background. If it still crashes, upgrade to Evolution 2.0 or later. You might need to keep it running in the background.
Accessibility is not active.
Adobe Reader checks the gconf registry to find if accessibility support is enabled on a system. If gconftool-2 is not available on a system, accessibility support is disabled. If your system does not have gconftool-2 and you wish to use the accessibility features of Adobe Reader, change the line
ACRO_AT_ACTIVE="false"
to
ACRO_AT_ACTIVE="true"
in the file <INSTALL_PATH>/bin/acroread, in the block
if [ "$IS_GCONF_TOOL" = "no" ]
near the end of the file.
To enable accessibility, using gconf-editor or gconftool-2, set the key /desktop/gnome/interface/accessibility to true. Then, enable the keyboard selection cursor (F7 toggles the cursor. It can also be enabled by choosing Edit >Preferences, clicking the Accessibility tab and selecting Always Display the Keyboard Selection Cursor. Finally, check the option by choosing Edit > Preferences, clicking the Reading tab and make sure that Enable Document Accessibility is selected.
Adobe Reader does not have access to the
pwd
command.
Adobe Reader does not run correctly from a directory where the
pwd
command fails.
Writing the preferences file. Adobe Reader does not warn the user when the preferences file cannot be written. Make sure that '$HOME/.adobe' is a writable directory if you wish to save preferences.
Printing password-protected PDF documents. Users cannot print password-protected PDF documents to PostScript from the command line even though they are able to print the files from Adobe Reader.
Unable to open PDF file with long file names. When operating in a heterogenous network environment using Novell servers, avoid giving PDF files long names (greater than 32 characters). A Novell server displays the long file name on a Macintosh computer, but Mac OS prevents Adobe Reader from opening the file. This is not a problem on Windows.
Menus and tabs appear inverted in Arabic and Hebrew locales. In Arabic or Hebrew locales, the menus, tabs and other UI elements appear inverted, displaying right-to-left instead of left-to-right. This issue is due to the design of the UI toolkit.
Press Alt to access the menu bar, then use any of the following shortcuts:
CTRL+L to show or hide full screen
SHIFT+CTRL+ + to rotate clockwise
SHIFT+CTRL+ - to rotate counterclockwise
SHIFT+CTRL+F to open Search Panel
Document Information and Preferences:
CTRL+D to display document summary dialog box
© 2005 Adobe Systems Incorporated. All rights reserved.
Adobe Systems Incorporated and its licensors. All rights reserved. Adobe, Acrobat, the Acrobat logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Distiller, Adobe Type Manager, ATM, Illustrator, PageMaker, and Photoshop are trademarks of Adobe Systems Incorporated. Sun, Sun Microsystems, the Sun Logo, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the United States and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.
UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. X Window System is a trademark of the Massachusetts Institute of Technology. Linux is a registered trademark of Linus Torvalds. Novell is a registered trademark of Novell, Inc. Macintosh and MacOS is a trademark of Apple Computer, Inc., registered in the United States and other countries. NCD and PC-Xware are trademarks or registered trademarks of Network Computing Devices, Inc. in the United States and other countries. STSong? is a trademark of ChangZhou SinoType Technology Co., Ltd. All other trademarks are the property of their respective owners. The contents of this file are subject to the Mozilla 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/MPL.This file has not been modified by Adobe and Source code may be found at http://www.mozilla.org/source.html. The Original Code is Mozilla Communicator client code, released March 31, 1998. All Rights Reserved.
Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA.