APP .3d files with Arbortext Editor + PE

[lbisson-read]

Currently the way to create .3d files is to use Arbortext Editor with Styler, select File > Print Preview, then from the APP Print Preview window select File > Save APP File.  When publishing with PE, the preview result is returned in a PDF Preview window instead of the APP Print Preview.  This means that if users have Arbortext Editor and are using PE to publish, they are not able to generate an APP .3d file. 

The recommended enhancement is to (1) enable the APP Print Preview window with Arbortext Editor + PE.  What would be even better for more robust tool integrations would be (2) a File > Publish > APP .3d File menu option and (3) XML to APP.3d being a supported output type when making PE server requests.

[ChrisWestern]

Hello Lisa,

So i understand fully, if you have AE, AS and PE but not APP why do you need to save APP native .3d document files if you cannot open them directly?

Best regards

Chris

[lbisson-read]

Hi Chris,

You are close, customer has AE, AEw/S, PE, and APP Desktop.  There will be exceptions where doc formatting will need to be hand-tweaked using APP Desktop with .3d files.  The .3d files are used by the product during the formatting process when publishing XML using the APP engine but they are not too easy to get at.

Lisa

[ChrisWestern]

Hi Lisa,

I presume they are creating the stylesheet with styler (not APP native desktop) and wanting this saved after the comp process as a 3d.

You might be able to save out the stylesheet as a 3f template file, then tweak the scripts inside and/or PE config to always save a 3d output post formatting, and then plug it back in to the stylesheet again.Just a thought!

But a feature to enable this without custom tweaking might also be nice.

Regards

Chris

[GarethOakes]

I suspect you could use PE Interactive to generate the .3D file but as you say not user friendly. Ideally you could "Compose to 3D" just like you currently "Compose to PDF".

[SimonTaylor]

Hi

I know this is old, but I've been going back over these ideas in light of Version 12.

This one has been delivered a long time ago - print config files allow you the option of saving out APP files at different points as part of the debug hooks.

Simon