How are DependencyFiles folders created and are they updated during the project cycle? |
Here is what happens in the DependencyFiles folder every time FTS segments a files, saves it, exports it as WSXZ package or imports it back as Return package back to SDL Worldserver: 1- Segmentation: A new dependency folder is created at segmentation for each file/task. This also mean that if a Task fails with an autoerror at the Segment Asset step, if you complete the error, a new DependencyFiles folder will be created. At segmentation, a folder is created with a random name consisting of characters and numbers, for instance F69858 This folder will always contain a copy of the source file. For Office 2010-2016 files (docx, xlsx, pptx) or for XML files, the actual file name is preserved with a random combination of characters and numbers added in front of the file name. Example: file name: this is a test.docx file name in DependencyFiles folder will be similar to : DF7218_this is a test.docx For Office 2003 files (RTF, doc, xlsx, ppt), the file name will be completely random and the source file name is not preseved. Example: file name: this is a test.doc file name in DependencyFiles folder will be similar to : DF7256_0f40xock.doc Note: in WorldServer 10.4.x, the DependencyFile folder for Office 2003 files (doc, xls and ppt) will contain 2 copies of the randomly renamed source doc file and one tmp file, also randomly renamed). The DependencyFiles folder for PPT contains a copy of the source PPT and a tmp file. 2- Save (manually or as an Automatic step, including Save target): Any Save action does NOT change the folder or its content or time stamp. 3- Export of WorldServer Studio package (*.WSXZ): no change of the DependencyFiles folder created during segmentation. No creation of a new DependendencyFiles folder. 4- Import of WorldServer Studio package (*.WSXZ): no change of the DependencyFiles folder created during segmentation. However, for every import, a new DependencyFiles folder with unique folder name is created, containing again a copy of the source file with changed name, as explained in #1 and #2 |