XMetaL 8 DITA-OT temporary files: Can we prevent renaming of files?

[jpcain429]

Greetings,

We have a primary XML file that references another XML file for references to image files.  In the primary XML file, the image reference is to a print-friendly image file (e.g., eps, indesign, etc).  We have a new transform that generates HTML for online.  Rather than have users manage multiple image file references, our HTML transform simply looks to match a print image file with a similarly named online image file.  This transform works great in a straight-up DITA-OT installation.  However, after configuring this online transform for use within XMetaL, the preprocessing that creates copies of the source files being transformed to a temp folder randomly renames all of the referenced files.  This breaks all of our resulting image file references.  Is it possible to prevent preprocessing from renaming the referenced files?

Thanks,

Jim

Reply

[jpcain429]

Every file, except for the primary file as input to the transform, is renamed.  Is there a way to disable this behavior? 

[echo] All files : C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmpContent_09497.xml;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmprad13659_tmp.xml;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmprad1591C_tmp.xml;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmprad1F58F_tmp.jpg;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmprad214EF_tmp.jpg;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmprad2657A_tmp.xml;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmprad2B006_tmp.pdf;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmprad30B4F_tmp.pdf;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmprad3F3D7_tmp.xml;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmprad4B058_tmp.indd;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmprad4FAF7_tmp.xml;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmprad6D47F_tmp.indd;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmprad7EA1B_tmp.xml;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmprad882F0_tmp.indd;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmprad882FF_tmp.indd;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmprad8AFBD_tmp.indd;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmpradA1FD0_tmp.pdf;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmpradB6CF2_tmp.indd;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmpradC1A5F_tmp.indd;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmpradE23AA_tmp.indd;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmpradED2D7_tmp.xml;C:usersdmadminappdatalocaltemprad304d5.tmpradca4b5_tmpradFDC0A_tmp.pdf

Thanks,

Jim

Reply

[Derek Read]

If you are running the Japanese edition then this behaviour is normal, and should not be altered if your file names are in Japanese (or non-Latin in general) as the DITA OT cannot handle those characters.

If you are not running the Japanese edition this is not normal. The setting for this must have somehow been enabled.

In either case (Japanese edition or standard edition) you can disable this setting:

1. Tools > Configure Output
2. Switch to the Advanced tab and check for this setting: cmd_fs_sandboxing  =  yes
3. Change the value to no

Reply

[jpcain429]

Hmmm, I checked, but cmd_fs_sandboxing is already set to no.  Output options are below.

cmd_always_open_log  =  no
ANT_OPTS  =  “-Xmx256m”
cmd_fs_sandboxing  =  no
cmd_cms_sandboxing  =  yes
cmd_dita_before_14_compatible  =  no
cmd_dita_ot_per_user_version  =  14
_rem_cmd_synchro_mode  =  2

Does anything else look off?  I checked our custom print_local_.xml and cmd_fs_sandboxing is set to no in that as well.

Any other possible ideas?

Thanks,

Jim

Reply

[Derek Read]

These all look normal for version 8.

You mention that changes have been made to the print_local.xml file. That would be where I think I'd concentrate my efforts.
Can you revert that to a default copy and see what happens?

Reply

[jpcain429]

I set cmd_cms_sandboxing  =  no and the referenced files are no longer getting renamed.  Is there other behavior that depends on this config item being set to “yes”?

Reply

[Derek Read]

That command is comes into play if you are using a CMS that has an integration with XMetaL Author Enterprise.
In my testing (without a CMS installed) it does not rename the files.

Reply

[jpcain429]

We are using the Documentum Webtop integration with XMetaL.  The only change that I made was to set cmd_cms_sandboxing = no.  Once I did that, the output files were no longer getting renamed.

Reply

[Author]

Posts