If this toggle is checked, the native file chooser will be used in preference to Java's multi-platform file chooser.
Note that file extension filters are not supported when the native file chooser is invoked by Java™.
Also note that automatically appending the proper extension to the selected save filename (see option "Ensure that a save filename has an extension") is not possible when this option has been turned on.
Default: checked on the Mac, not checked on Windows, disabled (grayed out) on the other platforms.
If this toggle is checked, when opening a document not constrained by a DTD or a schema, white space characters are stripped from elements containing child elements separated by white space.
This heuristic is generally a good one for XML data.
If this toggle is checked, a dynamic, non constraining, pseudo DTD is used for documents not conforming to a DTD or schema.
The pseudo DTD simply remembers all attributes and child elements added to each element during the editing session. Thanks to this pseudo DTD, the pick lists of the Edit and Attributes tools are always filled with sensible values.
If this toggle is checked, xml-stylesheet processing instructions specifying which style sheets to use for the newly loaded document are ignored. If the XXE configuration associated to the newly loaded document specifies CSS style sheets, these style sheets are used instead.
Using this option is useful if
<?xml-stylesheet?> specifies a style sheet for use by a Web browser such as Mozilla and not a style sheet for use by XXE.
Default: not checked.
If this toggle is checked and if the document being opened is modular (that is, contains references to nodes coming from other documents), XXE display a dialog box informing the user that included nodes have been marked as non-editable.
If this toggle is checked, the file containing the document being opened in the editor is automatically locked using an advisory, application-level, lock.
In practice, this means that:
Applications other XXE can open and modify the document being edited in an instance of XXE.
If you try to open in XXE a document being edited in another instance of XXE (run by you or by one of your coworkers), XXE will inform you that the file is locked and will tell you who is locking it. After that you'll be able to open the document but, if you modify it, you'll have to save it to another location.
Caveat: In order to use this facility, you and all your coworkers possibly editing the same files, need to turn this option on. If one of your coworkers forgets to do it, XXE will not be able to detect that the file being opened is locked, and in such case, your coworker may overwrite a document being edited by another person.
|How to forcibly remove a lock|
A lock is implemented by the means of a hidden text file containing information about who has locked the corresponding document.
On Windows, the lock file corresponding to document
On the other platforms, the lock file corresponding to document
Manually deleting the lock file forcibly removes the lock set on the corresponding document. Note that it is harmless to delete such lock files and this, at any time.
Default: not checked.
Unlike the above toggle, this form applies only to files stored on filesystems other than the local one (WebDAV, FTP, Zip, etc).
Specifies the type of lock used for the document being edited, when the underlying document store supports locking. Currently, only WebDAV supports document locking.
Note that the mode specified here is just a wish. XXE will adapt the lock mode to what is actually supported by the underlying document store. For example, if the Shared mode has been chosen by the user and the underlying document store only supports Exclusive locking, the document being edited will be locked using an Exclusive lock.
Specifies a free form string identifying you as the person locking a document. This string is presented to other users wishing to know who is locking a document. It is recommended to specify your email address (example:
Default: empty string which implies
|None||The document being edited in not locked.|
The document being edited is locked using a shared lock.
A shared lock does not prevent you from overwriting a document shared-locked by another author but a least, you are informed that the document is being ``used'' by this other author. (In such case, you'll generally want to contact him to decide what to do.)
The document being edited is locked using an exclusive lock.
An exclusive lock prevents you from overwriting a document exclusively-locked by another author.