A file type group may be assigned via an extension of the existing file type configuration in the project type or AIS property. The value of the file type configuration in the project type or AIS property is either a file type configuration or a file type group.
A file type group can only be applied to a directory in the AIS. It is not possible to assign a file type group to an individual asset via the AIS property.
File type and file type configuration resolution
When filtering, WorldServer tracks the MIME type based on the source asset, but obtains the value of the file type configuration in the project type or AIS property from the target asset. This section describes in detail how WorldServer determines which file type configuration and file type to use for an asset.
When a file type is requested by the system to filter from a source asset
S to a target asset
T, both with MIME type
M, the following process will be used to find the correct file type and file type configuration:
- The MIME type configuration for
M is consulted to obtain a base file type
F and file type configuration
C. If no further configuration is found elsewhere, these will be used.
- The file type configuration in the project type or AIS property for
T is examined.
- If the project type or AIS property has no file type configuration value assigned,
F and
C are used.
- If the project type or AIS property value is a file type configuration that is valid for
F,
F is used with the file type configuration specified by the property.
- If the project type or AIS property value is a file type group, the file type group is searched for an entry that contains MIME type
M. If one is found, the file type and file type configuration in that entry are used. If not,
F and
C are used.
Use of
"Not Translatable"
A file type group also allows a MIME type to be designated as having a file type of
"Not Translatable". If the file type resolution process finds that a MIME type is set to
"Not Translatable", it treats assets of that MIME type as not translatable.
This behavior is the same as if the MIME type configuration listed the given MIME type as “Not Translatable”.
Configuring multiple file types for a single MIME type
With file type groups, it is possible to use a different file type for two files with the same MIME type. For example, say you have several files with the MIME type
text/properties, and one of these files requires a custom file type, while the others can be processed with the Java Properties Filter. You could create a file type group for the file requiring the custom file type, and configure the project type or AIS property for that file's directory to use this file type group.
The other properties file would have to be in a different directory, and could default to the Java Properties Filter, based on their
text/properties MIME type.
Assigning multiple file type configurations to a single AIS property value
You can use a file type group to effectively assign multiple file type configurations, using the project type or the AIS
Change Properties dialog. If your project has a combination of different types of documents, with some that use a non-default file type configuration, you might have a file type group
ABC_Project with the following entries:
| MIME Type
|
File Type
|
File Type Configuration
|
| application/dita+xml
|
OASIS DITA XML File Type
|
Default
|
| application/xhtml+xml
|
XHTML 1.1 File Type
|
Default
|
| text/xml
|
Any XML File Type
|
My XML Config
|
Then, when you select the directory in which the files to be filtered reside, you can select the appropriate file type group from the file type configuration drop-down list in the "Change Properties" dialog.
The effect of deleting custom MIME types, file types, or file type configurations
WorldServer lets you configure and use special MIME types, file types, and file type configurations to match your specific requirements.
Note: You cannot delete system defaults.
When you delete a custom
MIME type, the delete confirmation dialog displays any possible impact on configured file type groups. For each MIME type marked for deletion:
- The list of file type groups in the system is examined to see if the MIME type is referenced.
- If at least one file type group references the MIME type, a warning is issued listing all file type group references.
If you click
OK to delete the MIME type, each file type group that references that MIME type is modified. The file type group entry for that MIME type will be deleted.
When you delete a custom
file type, the delete confirmation dialog displays any possible impact on configured file type groups. For each file type marked for deletion:
- The list of file type groups in the system is examined to see if the file type is referenced.
- If at least one file type group references the file type, a warning is issued listing all file type group references.
If you click
OK to delete the file type, each file type group that references that file type is modified. Each file type group entry that references the file type is set to “Not Translatable” and its file type configuration field is cleared.
When you delete a
file type configuration, the delete confirmation dialog displays any possible impact on configured file type groups. For each file type configuration marked for deletion:
- The list of file type groups in the system will be examined to see if the file type configuration is referenced.
- If at least one file type group references the file type configuration, a warning will be added to the delete dialog that lists all file type group references.
If you click
OK to delete the file type configuration, each file type group that references that file type configuration is modified. Each file type group entry that references the file type configuration is set to use the default file type configuration.
The effect of deleting a file type group
If you delete a file type group that is used by one or more project types or AIS property assignments, the assignments remain, but the values of the assignments become empty. This changes the affected region of AIS to the default file type and file type configuration values defined by the MIME type configuration.