Adobe Reader Supply Command Line Options

Adobe Reader Supply Command Line Options Free
Adobe Reader Supply Command Line Options Cheat
Adobe Reader Supply Command Line Options List
Adobe Reader Supply Command Line Options Download

This section describes a few of the many available customimzation options. Refer to the Wizard user interface and the Preference Reference for more options.

Tools and tool set configuration¶

Tools appear in two main areas: The Tools tab (sometimes called the “Tools Center”), and in shortcuts in the right hand tools pane. You can configure both via the following options:

User interface: Configure new tools as shown in the screen below.
Wizard: In the Tools pane, check Disable Apps in Tools tab.
Registry: Set a FeatureLockdown preference that maps to the tool’s AppID. For examples, see the Preference Reference.

Use this feature to standardize task-specific tool views, reduce training costs, and improve employee efficiency by grouping related tools into a common view. This feature allows:

Creating or import custom tool sets.
Switching between different tool sets.
Creating and managing tool sets across the enterprise via the Wizard or .aaui files.

Tool configuration files¶

Tool set files reside in these locations:

A local user directory (full access): Files which are stored and imported by the current user are placed in the default current user’s directory. For example: C:Users<username>AppDataRoamingAdobeAcrobat<version>UICustomization<anyname>.aaui
A local, product directory (read only): Files in this directory are visible to any user on the machine. For example: C:ProgramFiles(x86)AdobeAcrobat<version>AcrobatUICustomization<language><anyname>.aaui

You can find a list of tools and their available properties in the .aapp configuration files at %installdir%(productname)AcroApp(languageID). While it is possible to modify these files and leverage their rich configuration options, this technique is not officially supported since such options cannot be tested by Adobe.

Note

If you’re customizing shortcuts in the right hand pane, you can determine the a(index) value to use for cDisabled and cFavorites by looking in the .aapp file. For example, the Create PDF tool is named CreatePDFApp.

Custom tools¶

Note also that custom entries for 3rd party plugins added post deployment are overwritten on the next product update. To assure that your settings remain in place, add them via the Customization Wizard during the initial install. For details, see https://www.adobe.com/go/acrobatwizard.

Example tool set list¶

AccessibilityApp: Create and verify PDF files to meet accessibility standards for people with disabilities
ActionsApp: Use guided Actions to complete PDF tasks quickly and standardize routine tasks
CertificatesApp: Digitally sign or certify documents and validate authenticity
CollectSignaturesApp: Get signatures from others and track results
CombineApp: Combine and arrange files into a single PDF
CommentApp: Add comments with highlights, sticky notes, and mark-up tools
CompareApp: Compare and highlight the differences between two versions of a PDF
CreateCustomUIApp: Create a customized collection of Acrobat features and share with others
CreatePDFApp: Create a PDF from any format
DeveloperApp: Enhance PDF forms and connect to databases with JavaScript
EditPDFApp: Edit text and images in PDF files
ExportPDFApp: Convert PDFs to Word, Excel, PowerPoint and more
FillSignApp: Fill and sign documents and forms electronically
FormsApp: Quickly convert Word, Excel or scanned forms into PDF forms
IndexApp: Index PDF files to speed search across document collections
MeasureApp: Measure distance, area, and perimeter of objects
OptimizePDFApp: Reduce PDF file size, enable fast web view, control image and font options
PagesApp: Delete, insert, extract, or rotate pages
PaperToPDFApp: Turn scans or photos of paper documents into searchable PDFs with selectable text
PrintProductionApp: Preview, preflight, correct, and prepare PDF files for high-end print production
ProtectApp: Prevent others from copying, printing & editing the information in PDFs
RedactApp: Permanently delete sensitive text, graphics, or hidden data
ReviewApp: Automatically collect comments from reviewers in a single PDF
RichMediaApp: Add audio, video, and interactive objects
StampApp: Add stamps such as ‘approved’ or ‘draft’
StandardsApp: Create PDF/A, PDF/E, or PDF/X files to comply with ISO standards
SendAppFull: Send documents, track views and downloads

Preferences Synchronization (DC)¶

When preferences synchronization is enabled (the default), desktop preferences sync across machines where Acrobat and Reader are installed and when the user is signed in with an Adobe ID. This feature allows users to leverage their customizations and streamlined workflows on any machine. Syncing is controlled by the preference:

bTogglePrefsSync disables preference synchronization across devices. This new feature which synchronizes desktop preferences across machines with Acrobat and Reader on which the user is signed in with an Adobe ID.

Preference synchronization across devices¶
Preference	Type	Applications that sync	Settings that sync
Commenting	User Settings	Acrobat & Reader	All the preferences in the UI under Preferences > Commenting
Identity	User Settings	Acrobat & Reader	Everything in the registry under `Identity`
Document Open/Save Settings	User Settings	Acrobat & Reader	All the preferences in the UI under Preferences > Documents
Favorite Apps	User Settings	Acrobat	Everything in the registry under `AcroApps`
Quick tools	User Settings	Acrobat	Everything in the registry under `AVGeneralcFavoritesCommandsDesktop`
Left Hand Panes	User Settings	Acrobat	Everything in the registry under `AVGeneralcDockables`
Convert From PDF	User Settings	Acrobat	Everything in the registry under `AVConversionFromPDF`
Convert To PDF	User Settings	Acrobat	Everything in the registry under `AVConversionToPDF`
Scan & OCR	User Settings	Acrobat	Everything in the registry under `PaperCapturePlugin`
Actions	User data	Acrobat	The files under `%appdata%AdobeAcrobat12.0Sequences`

Corporate fonts & printing¶

You can set printing options via joboptions files. This example shows how to set corporate fonts.

Open the PDFMaker’s settings panel (method varies by the software product you are using to access it.
Choose Advanced Settings.
Add your font to the Always Embed list.
Save the settings as a new joboptions file.
Distribute the file:
- Predeployment: Use the Customization Wizard’s distiller feature: https://www.adobe.com/devnet-docs/acrobatetk/tools/Wizard/distiller.html
- Post deployment: Distribute the file to C:Users<username>AppDataRoamingAdobeAdobe PDFSettings and set the default joboptions file to use for the PDF printer and Distiller in the Registry. You will need to set the JobOptions registry entry for each PDFMaker used by specific software as well as for Distiller. For example:

Browser integration¶

Acrobat and Reader ship with browser plugins that enable viewing and creating PDF files in a browser. However, behavior as well as customization options vary across browsers.

Note

For manual browser configuration details, see https://www.adobe.com/go/pdfinbrowser.

Internet Explorer add ins¶

Disable the IE PDF viewer add-in via one of the methods below.

For more detail provided by Microsoft, see:

IE config on the command line¶

You can use the command line property DISABLE_BROWSER _INTEGRATION to prevent the installation of (or uninstall) the PDF Viewer ActiveX control.

IE config via the registry¶

Create the following preference if it does not exist, and set its value to 1.

Chrome PDF viewer extensions¶

Registry configuration options for Chrome include:

Disable the Chrome PDF viewer

Disable the first time startup screens that prompt for the Chrome extension install

Note

For Chrome details about the end user experience and associated UI, see https://helpx.adobe.com/acrobat/kb/open-in-acrobat-reader-from-chrome.html

PDF Maker extensions¶

When installing Acrobat, block the installation of PDFMaker’s browser extensions for Firefox and Chrome with the Wizard’s Features panel:

WebMail¶

Features include support for:

Sending PDFs as email attachments using any mail account that supports SMTP/IMAP protocols. In addition to existing desktop email clients, users can now configure these mail accounts by providing User Name, Password, IMAP and SMTP details.
Gmail and Yahoo mail accounts (Yahoo mail accounts that end with yahoo.co.jp are unsupported).
Using Webmail in various Acrobat workflows like Shared Reviews and Forms Distribution. Users can send emails for inviting participants to a Shared Review or distribute PDF forms using the above-mentioned Webmail or other mail accounts. Users can also retrieve their contacts list while composing the mail (Gmail only).

For configuration details, see the Preference Reference or the Wizard Guide.

AATL and EUTL certificate download¶

As part of the Adobe Acrobat Trust List program, Adobe periodically pushes vetted trust anchors (certificates) for use in digital signature workflows. In the Wizard, use the Load trusted root certificates from Adobe drop down list to specify how trusted root certificates are loaded:

Enable & Ask before installing
Enable & Install silently
Disable

Alternatively, set this preferences manually:

Custom file deployment¶

Custom files are one of the primary ways an enterprise can improve business efficiency and lower the Acrobat’s total cost of ownership. This feature is often under utilized, and workflow owners may find it beneficial to review the list below as well as the directories under the product’s root install location. Some of the customizable files include:

Files that improve workflow efficiency such as those for Actions, combining files, eEnvelopes, Quickbooks templates, forms templates, etc.
Files that customize application behavior such as JavaScripts and plugins.
Digital signature files: digital IDs, trusted identities, LDAP server list, custom signature handlers, certificate revocation lists, etc.
Printing and Distiller files.
Document backgrounds, headers, footers, watermarks, stamps.
Document security files, redaction codes, custom security handlers, etc.
Multimedia skins, navigators, preflight, color swatches, and many more.

Deployment options¶

IT can deploy custom files before or after product installation.

Deploy files with initial installation

Prior to product deployment, IT typically uses the Customization Wizard to add files to any requisite directory or to set configure the registry to scan custom, shared directories. To do so:

Use the Wizard’s Files and Folders feature to add files to the requisite locations.
Save the modified installer and deploy normally.

Deploy files using Group Policy Objects

Admins that use GPO and Active Directory deployments can use their standard methodologies for deploying files and custom registry settings. At a high level, the steps include:

Do one of the following:
- Create a Group Policy which runs a file copy script at system log on or log off or at a scheduled time.
- Place the files on the target machines via UserConfigurationPreferencesWindowsSettingsFiles or UserConfigurationPreferencesWindowsSettingsFolder.
Verify the files are copied to the standard product or user directory so that Acrobat can find the files.

Platform considerations

Most files are applicable to both Windows and Macintosh. Except for the root path, file locations are identical under the product install directories. Where registry or plist preferences provide file-related configuration options, corresponding registry preferences can typically be used on Macintosh by specifying equivalent plist settings in /Library/Preferences/com.adobe.Acrobat.

Refer to the Preference Reference for registry and plist details.

Plug-ins¶

Many organizations use plug-ins to customize workflows for particular needs. The Customization Wizard allows you to specify custom plug-ins for automatic installation. You can use plug-ins from third-party suppliers or develop your own using the Acrobat Software Developers Kit (SDK). For more information, see the Acrobat Developer Center: https://www.adobe.com/devnet/acrobat/.

JavaScripts¶

JavaScript can be used to add and remove items from menus, automate Actions, and perform an almost limitless variety of other tasks that can improved workflow efficiency. You can use scripts from third-party suppliers or develop your own using the Acrobat Software Developers Kit (SDK). For more information, see the Acrobat Developer Center: https://www.adobe.com/devnet/acrobat/.

10.1.1 introduced changes that affect the use of global variables and user scripts. If you are migrating to a newer version, refer to the Application Security Guide for details.

Custom Actions (macros)¶

Actions provide a way to reduce repetition, automate common tasks, and enable batch processing on one or more PDFs. Actions are similar to macros in other popular software applications and lower Acrobat’s total cost of ownership by increasing business efficiency. They also allow organizations standardize document preparation, minimize errors, reduce training costs, and improve employee efficiency by combining repetitive multi-steps tasks into guided Actions. Actions provide a way for the enterprise to:

Improve compliance by guiding end users through a set of tasks ensuring that no step is missed.
Simplify and speed up document preparation by optimizing the user experience.
Centrally distribute and update Actions.
Increase value and flexibility by integrating guided Actions with local and hosted repositories.

Integration with other products¶

Actions are integrated with PDFMakers so that they can be invoked from other applications. For example, when saving a file as a PDF in Microsoft Word, the PDF tool bar now displays a Create PDF and Run Action button. The drop down list of Actions show all the available Actions that the product can find. The list is populated from these directories:

The default Actions user directory.
The default Actions product directory.
Any custom directory IT has configured the product to scan for action files.

Action file locations¶

Action files can be stored in three locations:

A local user directory (full access): Actions which are stored and imported by the current user are placed in the default current user’s directory. For example: C:Users<username>AppDataRoamingAdobeAcrobat<version>SequencesMyAction.sequ.
A local, product directory (read only): Files in this directory are visible to any user on the machine. For example: C:ProgramFiles(x86)AdobeAcrobat<version>AcrobatSequences<language>MyAction.sequ.
A shared directory (read only): Custom Actions that are created for and shared across the enterprise can reside in any location visible by the product. Deployment should include configuring the product via registry preferences to look for the files that reside in any non-default location.

Shared directory configuration¶

Deploy custom Actions before or after product deployment. After creating custom Actions as described in the Help documentation, configure Acrobat to read action files from one or more shared folders in addition to the installed Sequences folder and the user-level Sequences folder.

To do so:

Deploy the action files to some shared location.
Use GPO or some other method to push new registry settings across your organization that enable the product to scan the custom action directories. To specify directories that should be scanned for action files, configure the registry as follows:
Navigate to [HKEY_LOCAL_MACHINESOFTWAREPoliciesAdobeAdobeAcrobat<version>FeatureLockDowncWorkflowcBaseFolders].
Create new keys under cBaseFolders. The names of the keys must follow the sequence c0, c1, c2, etc.
Create two REG_SZ values according to the specification in the table below.

Registry setting for directories to scan for Actions

Key values for specifying folders to scan¶
Name	Type	Description
tDIPath	REG_SZ	The device-independent path of the directory. The path should follow the syntax for absolute file specifications documented in Section 3.10.1 File Specification Strings in the PDF Reference, version 1.7 or later. The path may not contain the sub-string, “..”. If it does, Acrobat will ignore the folder.
tName	REG_SZ	A unique, case-sensitive alias for the directory. The names “install”, “transient”, and “user” are reserved. If one of the reserved names is used, Acrobat will ignore the folder. If the same name is listed more than once, Acrobat will use only the first occurrence.

Preferences format for caching action information

The following preferences are product-generated and are described for informational purposes only.

For each action that Acrobat finds when it scans the standard and administrator-deployed action directories, the following values are cached under the [HKEY_CURRENT_USERSoftwareAdobeAdobeAcrobat<version>WorkflowcRegistered] key.

Note

Although you can add and update such cached action information by hand, it is not necessary nor advisable. Acrobat can overwrite the information at any time.

Key values for caching action information¶
Name	Type	Req?	Description
aID	REG_SZ	No	A unique identifier for the action. If this entry is missing, Acrobat generates a GUID.
tBaseFolderName	REG_SZ	Yes	An alias referring to a particular folder. The two standard values are “install” and “user”, which refer to the application-level Sequences folder and the user-level Sequences folders, respectively. The name can also refer to an administrator-specified folder, as described in the above section.
tDescription	REG_SZ	No	A description of the action that is shown in various places in the UI.
tFileFormat	REG_SZ	Yes	The two valid values are “11” for an Acrobat 11-format .sequ file or “pre-11” for an Acrobat 10-or-earlier format .sequ file.
tRelativeDIPath	REG_SZ	Yes	The path relative to the base folder path. The path should follow the syntax for relative file specifications documented in Section 3.10.1 File Specification Strings in the PDF Reference, version 1.7 or later. Typically, it is just the name of the .sequ file; for example, `MyAction.sequ`.
tTitle	REG_SZ	No	A cached title for the action. If this entry is missing, Acrobat will get the action’s title by reading it from the action file (or from the filename of the action file for pre-11 Actions).

Offline Help access¶

The Reader Help system is only available online. If the product does not have online access, configure installs to point to a local version on your Intranet.

To configure local access to Help:

Download the Help in PDF format.
Install it in some accessible location.
Place the JavaScript in in the JavaScripts directory of each installed client. For example, (C:ProgramFilesAdobeReader<version>ReaderJavascripts). This script replaces the existing Help link with your custom link.

Note

The easiest way to place this file prior to deployment is by using the Customization Wizard’s Files and Folders feature. The Wizard allows you to create an MST file that will modify the installer with any of your customizations.

Help menu JavaScript

Accessing Help behind a proxy¶

The online help system can be made accessible when users are behind an authenticating proxy by setting the following preferences:

32-bit: [HKLMSOFTWAREAdobe<productname><version>FeatureState]'3179427'=dword:00000001
64-bit: [HKLMSOFTWAREAdobe<productname><version>FeatureState]'3179427'=dword:00000001

EMF and XPS conversion to PDF¶

The December 2018 Acrobat release disabled XPS and EMF file conversion to PDF.

At Adobe, we build security into our products and we implement numerous security processes and controls to help us comply with industry-accepted standards, regulations and certifications. Some examples of overall security improvements specific to Acrobat and Reader include: sandboxing (Protected Mode and Protected View), fuzzing high value targets like the broker process, finding memory corruption bugs via ASAN/GFlags, and running continuous static analysis on the codebase. Additionally, as an added security measure, where we see features with low usage, like XPS and/or EMF to PDF conversion, we disable these features. However, if you trust the document origin, you can enable the feature by creating and setting the following preferences:

Customization Wizard overview¶

The Adobe Customization Wizard tunes the Acrobat and Reader installer prior to mass deployments. The Wizard is a free utility designed to help IT professionals take greater control of enterprise-wide deployments.

Download the Wizard to:

Modify the installer via a transform file (MST file) without altering the original download.
Optimize installer and installation workflow by including silent installation, pre-serialization, reboot, multilingual, and custom setup choices, including suppressing the EULA, registration prompts, and the Getting Started window.
Customize application preferences such as collaboration, security settings, Acrobat.com integration, printing, and most other features.
Leverage existing installations by drag and dropping registry settings and files from existing installed applications.
Prevent users from modifying certain preferences by locking them.
Feature configuration-Registry: Install and configure the application to suit your environment and the use the Wizard to leverage you changes. Many application preferences and directories do not exist until the code is exercised from an installed application. While you could build the paths and add the values manually, simply configuring an installed application and using it as a template does most of the work for you.
Files and Folders: Many template files won’t exist unless you have installed and configured the application. For example, the easiest way to create a directory server file is via the application’s GUI. Use the Wizard to add these files to the installer.

Although many tools such as Orca and Admin Studio can be used to customize Microsoft transform (MST) files, Adobe only supports the Adobe Customization Wizard.

A typical workflow which uses an existing reference install could include the following:

Configure the application via its user interface. In particular, go through the menus under Edit > Preferences. Product UI configuration provides a simple way to configure features.
Use the Wizard’s Registry feature to drag and drop the configured template registry to the installer.
Use the Wizard UI to configure application preferences not already configured manually.
Lock down features so that settings can not be changed by end users: You can use the Wizard’s UI or the manually set lockable preferences.
Use the Wizard’s Files and Folders feature to drag and drop your enterprise files to the installer.
Save the installer changes to an MST file and install the customized product.
Use MSI and Adobe properties to further modify the install during deployment.

TeXnicCenter can be configured and customized in many different ways to suit theneeds of the user. The following configuration categories are available:

Output profiles define how the printable output is generated from the LaTeXfiles. The output can be in several formats, including device-independent(DVI), PostScript (PS), and portable document format (PDF).
Options allow you to modify the behaviour of TeXnicCenter.
Customization allows you to modify the graphical user interface, including themenu structure, the toolbar, the short cuts, the editor and the general lookand feel.
Advanced configuration provides instructions for configuration changes notavailable directly from within TeXnicCenter.

Output profiles¶

The LaTeX files are just simple text files. To get a printable output they haveto be compiled. Current TeX distributions support several formats like theTeX-specific DVI-format, PostScript or the very widely used PDF-format.

Where other editors can only produce one format as output, TeXnicCenter allowsthe user to select any of these output formats. It can even be extended toinclude other formats available in other TeX distributions or through the use ofadditional filters.

For each output format used an output profile has to be defined first. You canadd as many profiles as you want. Output profiles specify answers to a number ofquestions:

Is a (La)TeX compiler necessary to generate the output? If so, what is thepath to it? What are the command line arguments to pass to the compiler?
Is a BibTeX compiler available for the specified format? If it is, what isthe path to it? What are the command line arguments to pass to the compiler?
Is a MakeIndex compiler available for the specified format? If so, what isthe path to it? What are the command line arguments to pass to the compiler.
Which additional tools (postprocessors) have to be started after or instead ofthe TeX compiler to generate the desired output?
Which application is used to view files in the desired format? What are thecommands needed to display an output file? What are the commands needed toperform a forward search? Is it necessary to close the output before thecompilation starts? If it is, what is the command to do so?

Output wizard¶

The Output Wizard leads through the configuration of some basic output profilesstep by step. If MiKTeX or TeX Live is installed the Output Wizard can configurethe profiles almost without user interaction.

Invoking the output wizard¶

After TeXnicCenter has started it checks to see whether output profiles arealready defined. If this is not the case TeXnicCenter will then start theOutput Wizard automatically.

To start the Output Wizard manually, please select the menu itemBuild ‣ Define Output Profiles... and click on the buttonWizard in the next dialog.

Using the output wizard¶

At first the Wizard will look for an installed LaTeX distribution. If eitherMiKTeX or TeX Live is found the Wizard asks for permission to configureTeXnicCenter accordingly or to use another distribution.

To configure TeXnicCenter to use MiKTeX the wizard will perform the followingsteps:

It will look for the TeX compiler. If no compiler can be found, the path tothe compiler can be entered in a dialog.
Afterwards the Wizard will look for the registered DVI-viewer. If theregistered viewer is YAP, TeXnicCenter will be configured to YAP as defaultviewer. If another viewer is found, command line parameters to start theviewer, to view documents and to perform a forward search, can be enteredin a dialog.
Now the wizard will test if dvips (a tool that convert DVIdocuments into PostScript files) is installed. If dvips is found,the path for command-line arguments can be entered in a dialog.
Finally the Wizard will test if PDFLaTeX is installed. If this test issuccessful, the Wizard will look for the viewer registered for PDF files. Ifthe viewer is the Adobe Acrobat Reader, the wizard will do the configuration,otherwise the path and the command line arguments for a different PDF viewercan be entered in a dialog.
Now TeXnicCenter will create the following output profiles:

LaTeX –> DVI (only if latex has been found)
LaTeX –> DVI –> PDF (only if latex and dvipdfmhave been found)
LaTeX –> PDF (only if pdflatex has been found).
LaTeX –> PS (only if dvips and latex have beenfound)
LaTeX –> PS –> PDF (only if dvips and latexhave been found)
LuaLaTeX –> PDF (only if lualatex has been found)
XeLaTeX –> PDF (only if xelatex has been found)

If one of the above output profiles already exists, the wizard will askpermission to overwrite or to keep the existing one.

To check what the wizard has created open the dialogManual configuration.

Manual configuration¶

To create new output profiles or to edit existing ones, choose the menu itemBuild ‣ Define Output Profiles... The dialogProfiles is displayed:

The Profiles list shows all profiles already defined. The fourbuttons at the bottom of the list provide the following actions:

Add: Adds a new output profile to the list.
Copy: Copies the selected output profile to a new profile.
Rename: Changes the name of the selected output profile.
Remove: Removes the selected output profile from the list.

Use the other buttons to perform these actions:

Wizard: Starts the Profile Wizard that will help generating new output profiles.
OK: Stores the changes and closes the dialog.
Cancel: Ignores the changes and closes the dialog.

To edit an output profile select a profile in the list and modify the settingson the three tabs.

(La)TeX tab¶

The (La)TeX tab allows to define:

which LaTeX or TeX compiler to use;
which BibTeX compiler to use;
which MakeIndex compiler to use.

The meaning of the different controls:

Run (La)TeX in this profile: Choose this option, if the specified (La)TeX compiler should be called whenbuilding output with this output profile.
Path to the (La)TeX compiler: Specify the full path of the (La)TeX compiler to use in this profile.
Command line arguments to pass to the compiler: Specify the command line to pass to the (La)TeX compiler. Use place holdersfor dynamic arguments.
Do not use BibTeX in this profile: Choose this option to prevent BibTeX from being started, when using thisprofile. If this option is not checked, BibTeX will start or not depending onthe project settings.
Path to the BibTeX compiler: Specify the full path of the BibTeX compiler to use in this profile.
Command line arguments to pass to the compiler: Specify the command line arguments to pass to the BibTeX compiler. Use placeholders for dynamic arguments.
Do not use MakeIndex in this profile: Choose this option, to prevent MakeIndex from being started, when using thisprofile. If this option is not checked, MakeIndex will started or notdepending on the project settings.
Path to the MakeIndex compiler: Specify the full path of the MakeIndex compiler to use in this profile.
Command line arguments to pass to the compiler: Specify the command line arguments to pass to the MakeIndex compiler. Useplaceholders for dynamic arguments.

Postprocessor tab¶

The Postprocessor tab page allows to define tools, which should be runafter the (La)TeX compiler, i.e. to convert the file generated by the compilerto another format.

Adobe Reader Supply Command Line Options Free

The meaning of the different controls:

Postprocessors to run after the (La)TeX compiler

Lists all tools to run after the compiler has been executed. The tools arelisted in the order of the execution.

Use the button New at the top of the list to add a new tool.
Use the button Remove to remove the selected tool from the list.
Use the buttons Up or Down to change the execution order.

Executable

Specifies the full path of the currently selected tool’s executable file.

Adobe Reader Supply Command Line Options Cheat

Arguments

Specifies the command line arguments to pass to the tool. Use place holdersfor dynamic arguments.

Input redirection

Specifies where the selected tool retrieves its input data from. If nothingis specified here, the tool will retrieve its input data from the standardinput device (normally the keyboard). Otherwise it will retrieve its inputfrom the specified file.

Use placeholders for dynamic arguments.

Output redirection

Specifies where the selected tool should write its data output to. If nothingis specified here, the tool will write its output to the standard outputdevice, which normally is the console, the tool has been started from (i.e. aDOS box) or if TeXnicCenter started the tool the output window. Useplaceholders for dynamic arguments.

Adobe reader supply command line options cheat

Using input and output redirection allow to use tools, which do not interpretcommand line arguments, but retrieve their data input from the tool’s inputdevice and/or write their data output to the tools output device.

An example of such a tool is tth which is used to convert LaTeXdocuments into HTML documents. To start up tth use

When using this tool with TeXnicCenter use file.tex as input andfile.html as output redirection. The command-line of this tool has to beempty.

Viewer tab¶

The Viewer tab page allows to define the applications used to view thefiles generated by this profile.

The meanings of the different controls:

Executable path: The full path of the application used to view the files generated by thisprofile.
View project’s output: Command executed to view the project’s output. This command will be executed,if the menu item Build ‣ View Output is chosen and no opendocument in TeXnicCenter. This command can be either a command line or aDDE-command (see below).
Forward Search: Command executed to view output file, corresponding to the paragraph in thesource file the text cursor of the editor is currently placed on. Thiscommand will be executed, if the menu item Build ‣ ViewOutput chosen and is no open document in TeXnicCenter. This command can beeither a command line or a DDE-command (see below).
Close document before running (La)TeX: Specifies the command executed to close a previously generated output fileopen in the viewer before generating it a new one. This command will beexecuted, if the menu item Build ‣ Build Output is chosendirectly before the build process starts. Specify this command only if theviewer used opens files exclusively, so that no other application can accessthe output file with write access, while opened in the viewer (e.g. AdobeAcrobat Reader works that way). If the compiler tries to generate a new outputfile, it will fail because the file can not be overwritten. Specify a commandhere to close the file in the viewer before the compiler is executed. Thiscommand can be either a command-line option or a DDE-command.

Adobe Reader Supply Command Line Options List

All the commands can be either command-line options or DDE commands.Command-line options will be passed to the application during its start.

Adobe Reader Supply Command Line Options Download

The meanings of the fields for a command are:

Command line argument: Choose to specify a normal command line.
DDE command: Choose to specify a DDE command.
Command: Enter the command line to pass to the executable here, if the option Commandline argument was chosen or enter the DDE command to send to the viewer, ifthe option DDE command was choosen. You can use place holders to specifydynamic arguments.
Server (only available for DDE command): Specify the server name used to connect to the DDE server (the viewer). Formore information please refer to the manual of the viewer.
Topic (only available for DDE command): Specify the DDE topic the DDE command belongs to. For more information pleaserefer to the manual of the viewer. Most applications are expecting the topicSystem here.