Feature request: Make automatically created "publish" folder optional

[FrameMaker-dk]

I have created a feature request for FrameMaker.

When using Publish, FrameMaker will automatically create folder for the published output. While the can be practical, it is not ALWAYS practical, so I suggest making it optional.

If you want to vote for it, please find the request here: https://tracker.adobe.com/#/view/FRMAKER-12438

[LinSims]

Done. I've hated this "feature" since it first appeared. It's reminiscent of Microsoft's attitude of "we know better than you do what you want to do". 

[Winfried Reng]

When you create your PDF via Save as PDF, then FrameMaker will create the PDF in the same folder as your book or your FM file without any additional folder. This is the same as Publish to PDF.

Or do you mean something else?

[FrameMaker-dk]

There is a difference though. Using Save as pdf does not give you access to to the settings dialogue. Using Publish you will get access to add/remove Distiller from the pdf generation. Which can make a big difference. Why anybody would want a pdf that is "almost good" rather than having a good one, made using Distiller is a mystery, I think.

[Be.eM]

Why anybody would want a pdf that is "almost good" rather than having a good one, made using Distiller is a mystery, I think.

Because any PDF created using Distiller is an RGB PDF, because it relies on the RGB based Windows Postscript engine. That's why there's an option without Distiller (since FrameMaker 10) and and it's the only way to get proper CMYK output for printing. Which for my use is the "gooder" version.

And, as already stated, "Save as PDF" uses the currently loaded sts file from the publishing pod. Just load a different one to get different output via "Save as PDF", including Distiller based output.

[Matt-Tech Comm Tools]

Save As uses the currently active Publish Settings, so once you set your Publish options, so that's a good option.

However, I'd still rather have the Publish panel prompt for file location, or put it in the directory of the processed doc, per StudioSM's suggestion.

I actually don't agree with the "good one, made using Distiller" premise, but that's another thread or two (or 50)

[frameexpert]

The main problem with taking Distiller out of the process is that you can no longer use Postscript text frames to pass pdfmark commands to Distiller. And Microtype's Timesavers requires Distiller to do its magic. I used both Postscript text frames and Timesavers with a lot of projects to make custom bookmarks, buttons, and form fields, etc.