ScottHillock

The v_field is a variable array. So it should only include values separated by a comma. The concatenation with the + is not needed, as that is handled later on. So I would change it to: var FirstLast = Field('First Name') + " " + Field('Last Name ') + ", "; var v_field = [FirstLast, Field('Credentials') ].filter(String); This way we can modify the FirstLast later if needed, while still using the rest of the code.

Based off of Dan's and Step's code here on the forum. //Field names var v_field = [Field('First and Last Name'), Field('Cert1'), Field('Cert2'), Field('Cert3'), Field('Cert4')].filter(String); //Font var font_name = "2Volkswagon Heavy-K"; //Font Size var v_size = "12"; //Frame Width in inches var v_frame = "3"; var var1_n = '<f name="' + font_name + '">'; var var1_s = '<z newsize="' + v_size + '">'; var var2 = v_field.join(', '); //combine fields var var3 = v_frame*72; //get frame width in points var var4 = var1_n + var1_s + var2; var tm = new FusionProTextMeasure; tm.CalculateTextExtent(var4); var tmwidth = tm.textWidth; if (tmwidth < var3*100){return var4;} //if no scaling needed return without magnify var factor = Round(var3 / tm.textWidth * 10000, 0) - 1; if (factor >= 85){return "<magnify type=setwidth factor=" + factor + ">" + var4 + "</magnify>";} //if scaling is above 85% return with scaling if (tmwidth < var3*200){return var4;} //if it can fit 2 lines without scaling return //error Message Print ("the maximum number of characters has been exceeded"); return "Certifications exceed the allotted space"; The line that contains "if (tmwidth < var3*200){return var4;}" might need the 200 value adjusted lower. Since some text breaks at different points.

Remove the slash / from the filename so it is "2016 General Proposal ASKNO ASK.pdf". The slash is being treated like a directory separator, and is being replaced with the Mac seperator ":", on composition. Usually I try and keep file names as simple and short as possible, and all lower case.

var Var1 = ""; if (Field("Description 1")){Var1 += Field("Description 1");} if (Field("Description 3")){Var1 += ", " + Field("Description 2");} else{if (Field("Description 2")){Var1 += " and " + Field("Description 2");}} if (Field("Description 4")){Var1 += ", " + Field("Description 3");} else{if (Field("Description 3")){Var1 += " and " + Field("Description 3");}} if (Field("Description 4")){Var1 += " and " + Field("Description 4");} Var1 = Var1.replace(", "," ").replace(", , ",", "); return Var1; This should work ok'ish. There's a few cases where it won't (like 1 being empty or 2 empty but 3 or 4 populated).

Create a javascript global with: var DupeArray = []; Create an OnRecordStart with: if (DupeArray.indexOf(Field("[color="Red"]bg[/color]")) > -1 ){ FusionPro.Composition.composeThisRecord = false; } else{ FusionPro.Composition.composeThisRecord = true; DupeArray = DupeArray.concat(Field("bg")); }

Yup. They changed the way it works, it seems mostly to prevent Acrobat from hanging if you try to preview a job while already composing a job. On Acrobat DC the behavior is even worse. You can't even really work on any other job whatsoever while it's composing. Support's suggestion is to buy additional licenses or purchase Producer. From what I've gathered they will not change on this behavior. It worries me that if they are removing functionality from the product, what are they going to remove next? Will we be limited to the number of records we can output before having to upgrade or purchase an additional license. Will we have to pay to use javascript rules in the future. Will Imposition be an upcharge? I know this was sort of an undocumented feature. But still shocking that it was removed with no warning. One of the main benefits over other solutions was that fusionpro did not stop your workstation from being able to get work done. Others won't let you use InDesign while it's composing, and fusionpro is taking the same route now. We have 3 fusion desktop licenses, and will likely never upgrade now.

I don't think there's a way to do it easily. The closest I ever got was using a mix of repeat record count and set body page usage. Unfortunately this ends up taking 4 times as long to compose, and it ended up being quicker using Preps or PDF snake.

Does this happen with all fonts, or just one? It could be that the font is not loaded "all the way" (enabling and re-enabling and a few restarts of Acrobat and fusion might fix it). Or it could be that your Acrobat settings are not set to "Use local fonts". The rest of your issues are definitely a result of incompatibility between fusion and the latest versions of Acrobat and OSX.

It might be that your fusion document is looking for Filename.pdf and your file is named FileName.PDF. This can happen if your files are on a network share that has a case sensitive file system. I've seen it primarily with netatalk on Ext4. Also leads to the issue where your fusion document must be all lowercase.

These are the steps I take on a daily basis to get a font to "load" in fusion (even when it was previously working less than a week ago with no changes to what fonts I have loaded, and no restarts of the OS). Quit Adobe Acrobat Quit fusion Reopen fusion Deactivate and reactivate the font 5 times Quit fusion Reopen fusion Open Adobe Acrobat Deactivate and reactive the font once In fusion perform load new fonts Quit fusion Quit Adobe Acrobat Then, reopen your fusion PDF. The font should now be loaded. If not, repeat...

Yes it is possible, but you'll need to compose the file twice. Once for the single page records, and again for the 2 page records. In your FP file you'll want to create an OnRecordStart rule that checks if it's a 1 or a 2 page record, and then either composes or does not compose that record.

Use your non-rotated version and compose to PDF. Then import the PDF into a rotated graphic frame. It's a two step process for composing the job, but at least it gets done.

I've sent a video of the imposition setting not sticking to support again (I had also done it previously). As for the queueing issue I'm having I'm really hoping I'm reading your statement wrong and you are not saying you're removing a feature (even if it was unintentional). It was a blind queue where you couldn't see what was next, or pause, or shuffle jobs in the queue around. This difference and the fact that FP Direct is a server product differentiates the products enough that I don't think you should be removing functionality to nudge us into upgrading.

Do not recommend updating yet. Wait for the next release.

Well, that'll teach me for assuming a release has less bugs than the previous. One machine I was testing on with Acrobat DC will not compose at all. FP locks up, with no status in the message box of the composer window. The other machine with Acrobat XI I cannot compose multiple jobs and expect them to "queue" up like previously. And the imposition issue I had 11 months ago is still there. I sent an email to support this morning, and have heard no response yet. I seriously am lost at this point with FP. [support did get back to me, they changed email addresses though to @marcom.com and my spam filter assumed it was junk].

Having the files would definitely be helpful, but here's something that should work. It's not the most elegant but it's pretty simplistic. FusionPro.Composition.SetBodyPageUsage("Phone+Fax",false); FusionPro.Composition.SetBodyPageUsage("Phone-or-Fax",false); FusionPro.Composition.SetBodyPageUsage("EmailOnly",false); var Var1 = 0; if (Field("Phone") !="" && Field("Fax") != "") { FusionPro.Composition.SetBodyPageUsage("Phone+Fax",true); Var1 = 1; } if (Field("Phone") =="" && Field("Fax") == "") { FusionPro.Composition.SetBodyPageUsage("EmailOnly",true); Var1 = 2; } if (Var1 == 0) { FusionPro.Composition.SetBodyPageUsage("EmailOnly",true); }

I just sent to support a video of the bug with

Yes you can do that. Here is the javascript I use for it:

I'm not sure where this behavior is being controlled from, but if you hit the back button in the Finder dialog, you're taken to the folder that you would expect as with 8.x. So maybe there's something in OSX that is overriding FusionPro's action? We compose a lot of our files both 1up, and 2up. So the usual process goes compose the 1up versions, then compose again for the two up versions, but select the imposition file. If we view any extra tabs, or make any changes, the job is composed without the imposition file we selected. Opening the composition window again shows the imposition field is now blank. Seems to only work on jobs that were created previously. We keep some job options as variables in the Javascript Globals. Making a change to any of these variables does not take effect until a rule is added or deleted. Changing any rules does not "refresh" the javascript global variables we have set. It's more the logic behind the fonts.ini that is being a pain. I know for PC, and some scripting having the option of using bold/italic tags, styling, etc. is beneficial. But it seems like FusionPro assumes too much about what is a bold/italic version of a font. Here's an easy example, since we all have access to Myriad Pro. Myriad Pro Black Italic Myriad Pro Black MyriadPro-BlackIt Black Italic 0 1 W OpenType PostScript /Library/Preferences/PTI/FusionPro/Fonts/MyriadPro-BlackIt.bfk /Library/Preferences/PTI/FusionPro/Fonts/MyriadPro-BlackIt.pfa /Library/Preferences/PTI/FusionPro/Fonts/MyriadPro-BlackIt.otf /Library/Preferences/PTI/FusionPro/Fonts/MyriadPro-BlackIt.ufk Myriad Pro Black Italic Myriad Pro Black It MyriadPro-BlackIt Black Italic 0 1 W OpenType PostScript /Library/Preferences/PTI/FusionPro/Fonts/MyriadPro-BlackIt.bfk /Library/Preferences/PTI/FusionPro/Fonts/MyriadPro-BlackIt.pfa /Library/Preferences/PTI/FusionPro/Fonts/MyriadPro-BlackIt.otf /Library/Preferences/PTI/FusionPro/Fonts/MyriadPro-BlackIt.ufk This causes conflicts, and odd behavior. If I assign text the font Myriad Pro Black Italic, in the Variable Text Editor it does not appear italic, until I hit the Italic styling icon. I'm used to InDesign where it does not have styling of fonts, and even in Quark the mantra has always been do not use the fake styling of fonts. So, to get the behavior that I expect I end up having to delete the first entry in my fonts.ini Unfortunately this is one of those hard to reproduce bugs. I'm not sure how to make it happen again. When I noticed the error I reassigned the text from the db field to the rule field and all was ok. If it happens again, or if I can find the job that it happened to me on this morning I'll send to support.

esmith those are all issues I've come across. 9.3.6 is much buggier than 8.x I also have these issues: -Imposition selection in compose window does not "stick", if after selecting a file you select another tab -Javascript globals sometimes do not work -2D datamatrix barcodes are broken -Font naming for me is a major pain, almost every other font I need to edit the fonts.ini for -And I had the error message pop up again today that has to do with rotated frames and enfocus pitstop. -Rules with the same name as a database field sometimes are not applied instead of the db field

The newest version of FPImposer 9.3.6 does not fix this issue.

Font handling seems to keep getting worse and worse. Is it possible to share what priority it is on the "enhancements" or "bug fixes" list?

-To get more than one space you need to use a non breaking space character " " -Instead of trying multiple space, just use a tab character "<t>" and set your tab stops in paragraph settings so they all left align. - I'm sure there's a way to calculate the width of the text and apply specific tracking with the FusionProTextMeasure function, there''s a couple examples on the boards here.

You're more well versed in PDF standards and conformance than I am. I just assumed since running a Preflight on a FusionPro PDF specifically calls out FusionPro frames, it might have a parallel with PitStop's error messages.

Your Advanced Ordering is saved in the fpi file. If you reopen the file though, and open the Advanced dialog again, the values will resort to defaults.