Amaya uses different configuration files to get initial values for global parameters, dialogs, shortcuts, window size and position, user's style sheet, and so on. You can change most configuration parameters with various preferences menus.
Amaya uses a number of default directories to store configuration information.
Amaya stores most of the default values and all of the dialog messages in
the config directory. This directory's parent is the one in which Amaya was
installed (the default is Amaya/config on Unix; see the table
below for the location on Windows).
Amaya stores the user preferences and other user configuration files in a
directory called AmayaHome. An existing directory could be selected by the
user using the system environment variable AMAYA_USER_HOME.
Otherwise Amaya selects a default position.
The following table shows the default position of this directory in different architectures:
Architecture |
AmayaHome Directory Location |
Unix |
|
Windows 95/ Windows 98 |
|
Windows NT/XP |
|
This directory is preserved even when installing new versions of Amaya. It may contain the following files:
Note:
The amaya.keyboard, amaya.kb, and
amaya.css files are loaded at launch time. If you change them,
you must quit and restart Amaya to take the changes into account.
Amaya stores all the temporary files it creates in a directory called the AmayaTemp directory. The following table shows where this directory is stored within different architectures:
Architecture |
AmayaTemp Directory |
Unix |
|
Windows 9x |
|
| Window XP | $HOMEDRIVE\$HOMEPATH\LocaláDocumentsáandáSettings\Temp\amaya by default c:\Documents and Settings\$user_name\Local Settings\Temp\amaya |
Amaya creates files in this directory when browsing or printing a document. The cache is also stored in this directory. You can change the cache directory by using the Cache preferences.
Amaya always tries to delete the temporary files it creates. However, if Amaya crashes, the temporary files are not deleted. This will not impact subsequent executions of Amaya.
These dialogs are found under the Preferences submenu on the Edit menu. Nine preferences dialogs are available: General, Browsing, Publishing, Cache, Proxy, Colors, Window geometry, Annotations, WebDAV.
Each of these dialogs contains three action buttons:
Button |
Action |
Apply |
Validates and stores the options shown in the menu. |
Defaults |
Restores, but does not save, the default values. Use the Apply button to validate the options. |
Close |
Dismisses the menu. |
To open the General Preferences dialog, choose General from the Preferences submenu.
Home Page. Specifies the URI that Amaya will load when
launched or when the user clicks the home page button. An example is http://www.w3.org
Note: A complete URI must be used.
The options below can be toggled on or off by clicking the check box next to an option name. A mark in the box indicates that the option is active.
Enable line-byline paste. This option concerns the
pasting form an external application. When that option is active, Amaya keeps
lines in the source application. If not active, newline
characters are replaced by spaces. This option is immediately effective.
Generate backup files. When that option is active, Amaya generates a backup file for each edited document, after a given volume of modification. This option is immediately effective.
Save geometry on exit. Controls whether the current windows geometry should be saved when the application is exited.
Anti-aliasing. Controls whether anti-aliased fonts are used (better rendering when this option is used).
ISO format for date. Controls whether generated dates are displayed using the ISO format (DD-MM-YYYY) or the American format (YYYY/MM/DD).
Show targets. Controls whether link targets should be shown in all document main views.
Access keys. Specifies the key (Alt or
Control) used to implement the document access keys, or specifies that access
keys defined in documents are ignored.
This section of the General Preferences dialog lets you choose the font zoom level and define the dialogue language used in Amaya. These options are explained below.
Font Zoom.You can zoom in and out, document window by document window. Each document (text and images) displayed within a zoomed window will be displayed larger or smaller than its real size according to the current zoom. This option enables you to change the font zoom for all windows. This change affects only font sizes but not image sizes, and is reflected immediately in all open document windows.
Dialogue language. Specifies the language for all of Amaya's menus and dialogue messages. The default language is American English (en). At the present time, alternate languages are available: French (fr), German (de), Italian (it), Spanish (es), Portuguese (pt), Finnish (fi), Hungarian (hu), Russian (ru), Turkish (tr), etc. When launched, Amaya loads dialogue files according to the current dialogue language: en-, fr-, de-, it-, es-, pt-, fi- or tr-, etc. files. These dialogue files are located in the Amaya/config directory.
This option lets you specify the Alt or Control modifier used to manage access keys of documents, or says that access keys are ignored.
Note: The Alt modifier could not work because it is used by UI widgets.
The Browsing Preferences dialog control loading of pages.
When the user clicks with the right button on a link to a new Web page, this new page can be displayed either in a new tab or in a new window. This option specifies the user preference.
The options below can be toggled on or off by clicking the check box next to an option name. A mark in the box indicates that the option is active.
Load images. Controls whether images should be loaded. This option is immediately effective.
Load objects. Controls whether objects should be loaded. This option is immediately effective.
Show background images. Controls whether background images should be shown. This option is only effective when loading a new document.
Load CSS. Controls whether CSS style sheets should be loaded and applied or not. This option is immediately effective.
Double-click activates link. Since the first version of Amaya, users double-click a link to activate it. This enables you to choose whether to edit a link or activate it. You can override this behavior by deactivating this option.
Enable FTP. Enables Amaya to follow FTP URLs. This support is experimental and is not yet fully debugged. For example, for FTP URLs needing user authentication, the authentication information is not always memorized. Also, pressing the Stop button during an FTP download may crash Amaya. Because of these problems, this option was added to Amaya so that other developers may help to debug it faster. By default, this option is turned off.
Defines the current screen type. This value has an effect when a CSS style sheet specifies a media. This option is immediately effective.
If a document exists in different languages and your server is configured to do language negotiation, you can use this dialog to enter your language preferences (the first one has the highest priority). Try browsing this press release, which is available in French, English, and Japanese versions. By changing the language negotiation to the ISO codes for the above languages (fr, en, or ja) you can transparently request any of these versions.
The Publishing Preferences dialog lets you set preferences for ETAGS and preconditions, whether to verify each PUT command with a GET, set the default name for URLs ending with a slash, and enable PUT redirections on specified domains. These options are explained below.
Defines the charset used for new documents.
The options below can be toggled on or off by clicking the check box next to an option name. A mark in the box indicates that the option is active.
Use the application/xhtml+xml MIME type for XHTML documents. This option, if enabled, associated the new, official XHTML MIME type to all new XTHML documents that are published on the Web. This option is disabled by default because not all servers can handle this MIME type at the time of this release, Note that this requires also a change in your server configuration, if it's not storing somewhere the metadata associated with each document. This option does not modify the MIME type of existing documents: the MIME type that is received is the same one that will be used when saving the document, except if you do a SaveAs operation, of course.
Use ETAGS and preconditions. HTTP/1.1 introduces new headers that avoid the lost updates problem when publishing. With this option, you can detect conflicts when two users are publishing the same document.
Verify each PUT with a GET. If you don't trust your server, this option tells Amaya to retrieve each document as soon as it has been published and compare it with the copy stored in your workstation. If the documents differ, Amaya will warn you.
Export CR/LF. This option, if enabled, precedes each line feed by a carriage return (DOS format).
An HTTP server usually associates URLs that finish in '/' with a default name, for example, Overview.html. This option enables you to specify the default name that Amaya should use when publishing such a URL. Ask your Webmaster for the default name for your server.
According to the HTTP/1.1 specification, PUT operations should not be
automatically redirected unless it can be confirmed by the user, because this
might change the conditions under which the request was issued. You can avoid
having Amaya prompt with a PUT redirection warning by entering the name of
the server's domain to which you are publishing. You may specify one or more
domains, each separated with a space, e.g., www.w3.org
groucho.marx.edu.
Amaya provides a cache through libwww. The cache is enabled by default and is stored in the AmayaTemp/libwww-cache directory. This menu also provides a Flush Cache button for erasing the cache directory.
The options below can be toggled on or off by clicking the check box next to an option name. A mark in the box indicates that the option is active.
Enable cache. Activates or deactivates the cache.
Cache protected documents. By default, documents which are protected by a password are stored in the cache. Use this option to override this behavior.
Disconnected mode. Always retrieves documents from the cache.
Ignore Expires: header. Does not expire cache entries.
Identifies the parent directory for the libwww-cache directory. Changing this directory does not erase the contents of the previous one. You must remove it yourself.
Note: File protection mechanisms prevent the use of NFS (Network File System) directories for the cache directory as NFS allows reuse by multiple processes or users. Use a local directory for the cache.
Gives the size, in megabytes, of the cache repository.
Gives the maximum size for a cache entry.
This button allows you to flush the current cache.
You can use this dialog to specify a proxy and a set of domains where the proxy should or should not be used.
HTTP proxy.Identifies the proxy to be used for HTTP requests. You must specify the full name of the server. If the server is running in a port other than 80, then, like in a URL, you need to add a ":" char to the proxy name, followed by the port number. The table below provides two examples.
HTTP Proxy Entry |
Result |
áá groucho.marx.edu ááááááááááá |
Declares a proxy called groucho.marx.edu running at the default port 80. |
áá groucho.marx.edu:1234 ááááááááááá |
Declares a proxy called groucho.marx.edu, running at port 1234. |
Lists space-separated domains where you want to use your proxy. Use the switch buttons to specify if the proxy should or shouldn't be used with this domain list. For example:
harpo.marx.edu zeppo.marx.edu chico.marx.edu
ááááááááá ^----------------^----> space separated entries
This dialog lets you select the default foreground and background colors for documents. It enables you to control the colors used by Amaya to display the current selection.
All these colors may be selected by name, hex code, or RGB format:
You can also select colors with the associated color palette.
Note: Color changes will be effective when you open a new document window.
This dialog enables you
Note: These changes take affect when you open new document windows.
The author of the annotation. By default, Amaya uses the login name of the user. This field enables you to change your user name to something more meaningful.
This setting defines the server to which the annotations are posted. Local annotations are always saved to the local repository, and by default, this setting is empty. The post server is not automatically included in the list of servers, so you should enter the post server name in both places.
A list of servers Amaya should contact when looking for annotations. You
can specify one or more servers. The reserved server name
localhost tells Amaya to search the local annotations, but
does not necessarily mean that a local annotation server is running (or it
would show a complete URL ).Under Unix, the annotation servers are specified
as a space separated list. Under Windows, you can add a new server name by
clicking in the Annotations servers list, pressing the Enter
key, and then typing the server name . By default, this list is initialized
to localhost.
Tip: To temporarily disable an annotation server, add a "-" char before its URL. Amaya will ignore it.
The options below can be toggled on or off by clicking the check box next to an option name. A mark in the box indicates that the option is active.
Autoload local annotations. Whether Amaya should request local annotations automatically every time you browse a new Web page. If it is not checked, then you can manually choose Load annotations from the Annotations menu.
Autoload remote annotations. Whether Amaya should request remote annotations automatically (by querying the annotation server) every time you browse a new Web page. If it is not checked, then you can manually choose Load annotations from the Annotations menu.
Note: You may experience a delay when Amaya loads remote annotations in resolving the DNS name of the annotation servers.
Disable remote autoload at each startup (for offline work). Whether Amaya should reset the autoload remote annotationsoption at launch time. This option can be useful if you are working offline, but still want to autoload the local annotations as well as the remote ones.