The Save As Command
Choosing Save As from the File menu
opens the Save As dialog, where you can: save the document
as XML, HTML, or as a text file to a local disk or a remote URI; save
embedded images into the same document directory or a different location; and
transform embedded URIs.
The Save As Dialog
The items in the dialog box, from top to bottom, left to right are used as
follows:
- The Copy Images toggle indicates whether the images
embedded in the current document must be copied along with the document
to the new location. It's generally better to keep this switch on as
otherwise you will not be sure that the corresponding images will be
found when opening the document later. However, switching it off is
useful when you have only changed the text of the document and the
document is stored on the same server. When images are copied, Amaya will
automatically update all SRC attributes to point new
image locations. New locations will be relative URIs.
- The Transform URIs toggle transforms all current URIs
into relative URIs when possible. Of course, if the document is saved in
a local file and URIs point to remote files, URIs will be absolute. This
ensures that all the links in the document remain correct after the copy.
However, if you have several document linked together with relative URIs
and you plan to move them to a remote location, you must disable URI
conversion to avoid referencing the initial locations.
- The Images location field allows you to save images
(if Copy Images has been selected) to a different place
than the HTML file. This field should contain the name of a directory on
the local file system or a location on the remote server.
- Using a relative path, the images are stored at a location relative
to the document directory. For example, if the document location is
http://www.w3.org/pub/WWW/Welcome.html
and the
images location is "Images", an image "W3C.png" contained in the
document is stored at the URI http://www.w3.org/pub/WWW/Images/W3C.png
and the HTML file is modified to reference it as:
<img src="Images/W3C.png">
This is similar in the case of a document location on the local
file system.
- Using an absolute path, the images are stored at this exact
location, independently of the document location. In the previous
example, if the specified images location is
http://pub/WWW/Images
, the image is stored at
http://www.w3.org/pub/WWW/Images/W3C.png
and the
corresponding HTML file is modified in the following way:
<img src="Images/W3C.png">
Several buttons are at the bottom:
- Clicking Confirm starts the process of transforming
the document. A dialog asks for confirmation in both of the following
cases:
- The document has to be saved on a remote server. Amaya displays the
complete URI to be written to for verification.
- The document has to be saved locally and the file already exists.
- When saving to a remote location, check that the http_proxy is not set,
or that the proxy server and the target server are configured
to work with the PUT method.
- Amaya does not currently contact the remote server (in case of an
http://...
destination) to check whether such a document
already exists.
- Clicking Browse lets you select a local directory and
file name:
- The Document directories field shows the
directories contained in the current directory. It should be used to
save a file on the local file system.
- The Files field shows the files contained in the
current local directory.
- Clicking Clear removes the current contents of both
the Document location field and the Images
location field.
- Clicking Change Charset opens a pop-up window that
enables you to change the charset of the document. This option only works
with documents that support the notion of charset, such as HTML and XML
ones. This option is available when saving both remote and local
documents.
- Clicking Change Mime Type opens a pop-up window where
you can select the MIME type of the document. If the MIME type you're
looking for is not listed, you can type it in yourself. This button is
only active when saving a document to a server (local file systems don't
store the MIME metadata information.).
- Clicking Cancel terminates the command.
See also: