| IDependencyFileProperties Interface |
Namespace: Sdl.FileTypeSupport.Framework.NativeApi
The IDependencyFileProperties type exposes the following members.
| Name | Description | |
|---|---|---|
| CurrentFilePath |
The current path to the dependency file
| |
| Description |
Optional clear text description of the file. This can be used e.g. to explain
the origin and purpose of the file to other users and developers.
| |
| DisposableObject |
This property can be used to hold a reference to a disposable object,
such as a temp file that should be deleted when it has no more references. (optional)
| |
| ExpectedUsage |
Expected usage for this dependency file (optional)
| |
| FileExists | True if the CurrentFilePath references a file
that exists.
| |
| Id |
Id associated with this dependency file. (optional)
| |
| OriginalFilePath |
The original path of the dependency file (if known)
| |
| OriginalLastChangeDate |
The timestamp (the last change date) of the original dependency file (if known)
| |
| PathRelativeToConverted |
If the file is a direct dependency of the file being converted, and it is linked rather than embedded,
then this property may contain the path to the linked dependency file relative to the .sdlxliff file
that refers to it.
| |
| PreferredLinkage |
Indicates the preferred way of handling this file when writing intermediate
bilingual content. (optional)
| |
| ZippedCurrentFile |
A FileJanitor instance managing the lifetime of a temporary .zip file containing a copy of the file stored in CurrentFilePath.
|
| Name | Description | |
|---|---|---|
| Clone | Creates a new object that is a copy of the current instance. (Inherited from ICloneable.) |
Some examples of dependency files include:
Dependency files are not processed for localizable content.
Information on dependency files is particularly important when moving bilingual documents between systems (or even between different locations on the same system). After saving a bilingual document LinkedDependencyFiles, this contains information on which dependency files (if any) were explicitly linked rather than embedded in the bilingual file.