Configuring AppData for editing documents using a DTD
When you use the edit tools, the tool reads information stored in AppData then exports the document to a check out directory for editing.
When you exit the application you are prompted to save the data in Contenta at which point the data is imported into the database from the directory.
The information that is read from AppData assists the editor when you open fragments of the document—that is, when you open a child object that is within the hierarchy of the full document. When you open these objects in the editor tool, the tool reads the data in the object’s Document Type property sheet field and (in addition to reading the mapping information) it gathers information stored in the following AppData values to build a header.
- DATATYPE
- XMLDECL
- PUBID
If the values are not defined, the following defaults are assumed:
| Name | Default Value |
|---|---|
| DATATYPE | xml |
| XMLDECL | <?xml version=”1.0” encoding=”utf-8”?> |
| PUBID | no default value; this value must be defined |
If the DATATYPE is not set to xml, the XMLDECL value is ignored. If you define DATATYPE as sgml for example, the XMLDECL value (if any) is ignored; in such a case, do not add any XMLDECL value.