Opens a configuration, replacing the currently active one within upCast.
Saves the current configuration of upCast to a file. You can retrieve this state later anytime by opening it again.
Saves the current configuration in BCF format.
Use this to easily create a BCF template from your current filter configuration. You can then edit the <source> and <file> elements appropriately. Also, you'll see quickly which parameters are supported by some custom filter or hidden parameters of the standard filters.
Opens the upCast logfile (as it is at that very moment) in a new window. This window is not 'live', i.e. entries appended to the log file will not show in the window until it is closed and re-opened.
Writes the special configuration preferences.plist to disk and then exits the application.
In Swing (the graphical user interface class library upCast relies on), the concept of pluggable look and feel is utilized. This means that you can choose the look and feel of the application's graphical user interface from a variety of predefined styles. Select via a sub menu among the look and feels upCast has found installed on your machine. The setting will be remembered in the upCast Preferences file.
This will install the WordLink component. This means that from this point on, if you're running upCast on Windows 95/98/2000/NT/XP and have a working installation of Word 97 or later, you can also convert Microsoft Word binary (*.doc) files directly.
For this to work, a little bridging application needs to be installed on your machine. You can check this in the system information window under .
You only need to perform this step once after installing upCast or upgrading to a more recent version. It doesn't hurt to try to re-install WordLink if you find it got broken somehow or it is not listed as being available on the System Information… window.
WordLink functionality is only available on machines running the Microsoft Windows operating system. Therefore, this menu entry is always disabled on other platforms.
This will install components into the system that facilitate interfacing with upCast from VisualBasic for Applications.
You only need to perform this step once after installing upCast or upgrading to a more recent version.
VBA interfacing functionality is only available on machines running the Microsoft Windows operating system. Therefore, this menu entry is always disabled on other platforms.
This lets you set the XML Catalog file upCast uses. The change takes effect immediately and is saved in the preferences and in configuration files.
This lets you setup a default catalog configuration that will let you validate upCast DTD XML files without active internet connection.
Use this when you experience strange validation problems or your computer tries to establish an internet connection when validating XML (upCast DTD) files. You may also use this to generate a template file set to be augmented by custom DTDs, e.g. for XHTML or DocBook.
Use this to quickly update the local copies of the upCast DTD placed on your machine using the command without touching the (possibly modified) catalog file.
Displays a dialog for setting the Timed Execution feature's parameters. See the description of the Timed Execution feature (Section 3, “Element Reference”).
This item is only available when using a license with the Batch feature included.
Displays the End User License Agreement (EULA) for the application.
Shows a message on how to buy upCast und takes you to the appropriate page on infinity-loop's web site, if you have a web browser installed.
Opens the Registration Details window, where you can review registration details, clear the current registration (effectively unregistering upCast) and import a license from a license file.
For details on how to license your copy of upCast with the license key sent to you via email, see Section 3, “Supplying a License file”.
When checked, very detailed debug information is written to the log file. This can be handy for determining the cause if "something goes wrong" and when our support team here at infinity-loop requests that information for tracking down problems.
This switch receives its initial state from the Java system property de.infinityloop.debug, which can be set to false or true also on launching the application.
Toggling this menu item toggles the Log4Java logging level of the de.infinityloop logger between DEBUG (checked) and INFO (unchecked).
Displays a window with information about the upCast application you are running.
When you are running an evaluation version, the remaining evaluation period is also shown (in days).
Launches your default web browser and points it to infinity-loop's web site, where you'll find up-to-date information on the upCast product line, available downloads and support information.
Displays a window with information about the system environment where you are running upCast. This information can be useful for tracking down problems or checking whether WordLink is available and working. You can save the contents of this window as a file for submitting it to infinity-loop Technical Support easily.
The System Information window also lists all loaded export filters (and where they were loaded from) and available character encodings.
Checks with infinity-loop's version information server if a newer version of the software is available.
No private or personal data is transmitted using this feature, but merely a version description document is requested via HTTP from infinity-loop's server and the contents is compared to the currently running application's version. When the information in the version document indicates a newer verison is available, an appropriate dialog is displayed.
The version document currently is requested from the following URL: http://www.infinity-loop.de/versioncheck/upcast5.plist
Displays the upCast documentation in a new browser window using the default web browser on your system.
If you are choosing this menu item for the first time, upCast copies help information from its JAR file into the {Documentation Folder}.
If you want to provide specific help for your users, you may provide customized help by replacing {documentation root file} with your own one.