ScottHillock

PDF and Preflight profile attached. I should have been more specific in my last post, by "it" I mean FusionPro Text and Image Frames. The fact that Acrobat Preflight marks FusionPro frames as errors means the FusionPro frames are not conforming to the PDF standard.(When running the preflight it specifically highlights the frames). I can only assume Pitstop is running a quick check of page content to see if anything is corrupt, or is mis-formatted, and is complaining about the frames also. Again, I'm only running 9.2.31, and I'm not sure how the fixes are implemented in the version that PTI currently has in QA right now. And from your posts it does seem like the errors that Pitstop is reporting no longer appear. And in the new version Acrobat might not be finding errors with those frames either. testfile.pdf New Profile 2.kfp.zip

I'm only using 9.2.31, but I ran an Acrobat preflight on a a FusionPro PDF that has 2 pages. And I get the following errors only on page 2: Page Description Errors > Offending Command. So, it's not just Enfocus that's seeing it as an error. Adobe also sees it as an error. Report.txt attached. report.txt.zip

I've tried jlyt. It does not seem to be an optimized jlyt like you would expect to be produced by HP SmartStream Designer. Instead it seems to be a PDF wrapped in a jlyt. And, will take just as long to RIP on the Indigo as a PDF would.

Try first restarting FusionPro. With FusionPro open deactivate the fonts, then reactivate them. Then in FusionPro, Load New Fonts. Restart FusionPro again, and they should be in there.

A couple of things to try before you send up to support: - make the filename all lowercase, and as short as possible. - copy the files to your desktop and try to export from there. - run disk utility / repair permissions - remove all of the FusionPro preference files I used to have a similar situation where exporting the PDF seemed to do nothing, since it did not auto open. But the PDF was made, just had to manually open it. I was never able to get it solved, where the PDF would auto open after exporting.

To add a little more description. With FusionPro you can define custom Spot Colors, and define a custom CMYK alternative colorspace to it. But, FusionPro does not contain the Pantone libraries to add a Pantone color defined in a LAB colorspace (the default behavior of the Adobe apps/Pitstop, etc.). So when sending your composed files to a Fiery/Freeflow/Creo RIP, the custom CMYK value you defined could be output as: - The same as an InDesign generated file (by allowing the RIP to override the custom CMYK values and use the RIP's Pantone libraries in LAB) - Pretty close as the InDesign file (not allowing the RIP to override the values, but by using a different output colorspace to convert the LAB spot colors than what you had used to define the custom CMYK values) - Completely different than the InDesign file (not allowing the RIP to override the custom CMYK values and specifying a much different breakdown than one would expect - such as DSweet's example) Just be aware of the settings on your RIP, and how it will effect the files you send to it.

Do you have tracking or superscripting applied to any part of the paragraph. That's usually the culprit for me.

Dan, yes most of the issues are new in FusionPro 9.2, and were not there in 8.x. Some fonts used to translate over correctly, while others did not. Now, almost none do. For example, Futura Std Book used to be applied correctly, while Futura Book would not. Now neither does. Also, sometimes correct paragraph leading, space after/before are brought in when paragraph styles are used. If no paragraph styles are used leading is not brought in at all. And if text has paragraph styles overridden, the overridden settings are not used, just the settings from the defined style. Again, for the tabbing, this worked correctly in FusionPro 8.x. In FusionPro 9.2.31 tabbing from one input box shows unexpected behavior. Can you guide me to the best place to reach support. I have tried in the past to submit issues and have received no response. I'm not sure if that's because the issues were actively being worked on and a fix was posted a couple days after, or if the old form on the website was not the correct place (I see it has now been replaced with a simple mailto: link).

Try renaming your FusionPro PDF file to all lower case. There is a weird issue with FusionPro, where if the PDF is stored on a network server that is case sensitive, the filename must be all lower case.

The only issue I still have with fonts is that the names do not translate correctly from InDesign to Fusion. So every new job I need to manually define the fonts for all of the text. Along with the usual stuff that doesn't translate over (ex. paragraph spacing), and settings in InDesign that are not the same in Fusion (ex. Superscript percentages). Also, there's an issue with tabbing between fields in FusionPro dialogs (weird and non existent orders). An example, selecting records to compose, placing your cursor in the first box, and then trying to tab over to the second one does nothing. When editing the superscript percentages, the order of tabbing between input fields seems almost random.

In your imposition set the stack count to 25. And in your compose settings set the output to 500 records per file (uncheck Different number of records in first file).

erling, yes the update is free for all users of 9.x. I just submitted these issues to Support (or at least I think I did. The support form is not finishing the submission process for some reason). If you are not experiencing these issues I would stay on 9.0.3 until the next update. I know PTI has been working hard to get the Mavericks compatibility and new language features pushed into recent updates, and may not have gone through their total QA procedure on the latest updates. I'm using the latest version of Fusion 9.2.26 on OSX Mavericks and I'm having some issues. 1. - When using the Variable Text Editor, the field names are listed in Alphabetical order. Previous versions of Fusion Pro, as well as in other parts of the current version (preview pane, etc.), list the field names in the order that the database has them in. 2. - Last locations are not saved/used. In previous versions when composing a job, if I were to click browse to enter a new file name, the Finder save dialog box would take me to the same folder that is defined. Given this folder structure Job#> Mail files > exportedfolder. Previously, clicking on Browse would take me to the exportedfolder (if it was the last place an output file was saved to). On the current version most of the time I’m taken to the “Mail files” folder. This may be more related to an OSX Mavericks issue? But it does slow down our workflow, and could lead to errors. 3. - Fonts not translating from InDesign to Fusion. In my InDesign document there is variable text that is calling out NissanAG-Regular and NissanAG-Medium. When exported to FusionPro, both instances are looking for NissanAG (according to the Font Usage dialog). 4. - Fonts not loading correctly in Fusion. In the fonts.ini the fonts are not being called out correctly. I might have 3 lines for NissanAG-Regular. One being defined as regular, one as bold, and one as italic. The bold instance is translating to NissanAG-Medium, the italic instance as NissanAG-BoldItalic. Same applies for Condensed, Black, Extended versions. I’m having to edit the fonts.ini to remove all of the bad callouts. I know the Bold and Italic Styling is there to support the tags of <b> and <i>. However, I’d prefer an advanced option of sorts. If I want to use a tag to define a bold/italic style of a font, I can specify the exact font.

The only safe way to open comma separated or tab delimited files in excel is to first remove the extension from the filename. With an extension Excel likes to assume the file format. Then open Excel and tell it to open the file. Here you can specify your delimiters, etc. The important screen is where you can define the "column data format". Select all of your columns and change the setting from General to Text. General will autoformat columns, drop leading zeroes, etc. Changing the format to Text will leave your data as is.

I'm having the same issue with the latest release of FusionPro 9.2.25. It appears to be happening to a lot of otf fonts. I am using FontExplorerX 4.2. And Mavericks 10.9.2 Here is an excerpt of my fonts.ini showing the different styles of a font grouped together