ThomasLewis

Yes, in the Variable Text Editor. Treat it like any other rule.

Give this rule a shot: return Field("Address").replace(/([0-9])/g, "ᢸ$1;").replace(/\s/g, " "); You will need to turn on "Treat returned strings as tagged text" in the rule and also in the compose window, under the Advanced tab, turn off "Limit processing to Latin-1 text". Note: the second replace is only needed if you have have digits separated by spaces, ie "564 897 S. Street". For whatever reason Fusion pushes the digits together too closely and using non breaking spaces fixes that.

This is hard to test without input file and resources but you may be able to achieve the result you want by doing the following: Go to menu FusionPro / Data Definition / Input Options / Edit Fields then change PDF File Name to Type Graphic Add a blank page in your template before page 1 Create a graphic frame covering that page Set the Field or Rule in the Graphic Frame palette to be PDF File Name Move what used to be body page 1 to body page 3 You probably need to move the small text frame in the upper right to page 1 Open the Rule AlexMarshall and change var pgnbr = 1 to var pgnbr = 2 What should happen is now page 1 will be static on page 1. Page 2 will be your blank. Page 3 and any following pages will be the overflow starting with page 2 of the input PDF.

Attached is "a" way to do this. There are probably dozens of ways to get the end result but this would be my approach. You should be able to just unpack the zip and hit Compose to test it. A couple things to note. There are no conventional text rules in the example. All the magic happens in the two callbacks. There is no input file. It is set to "None". You are only composing one record, it is being repeated and changed based on the external file. ExternalDataFile_Nup.zip

Take a look at the zip file I posted here: http://forums.pti.com/showpost.php?p=15892&postcount=2 Seems like this is what you want. Notice the Stack is set to 1 in the imposition.

That's the method I use for clients who need the ability to edit the addresses. So long as the product is set to just show the Corporate Addresses I'm not aware of any way the end user can overwrite that list. You can use a bit of CSS in your Custom Content Footer to globally change the look of the link. Here's an example: <style type="text/css"> .SelectSavedContentPrompt a { color: #FFF; font-weight: bold; font-size: 14px; background-color:#259542; display: inline-block; padding: 4px 6px; } </style> You can also change the "Autofill Options" wording on the button to something more intuitive using the Portal Editor. Alternatively, if you maintain your customers address list, then a much better method is to use an external data file and point your templates to that. The end user cannot alter the address but often times that's for the best.

This is discussed at length in the announcement topic here: http://forums.pti.com/showthread.php?t=3982 It has been fixed for an upcoming release 9.3.12.

You should be able to just add the optional nonExistOK parameter to the CreateResource function. If if is set to true it should ignore that error. CreateResource(Field("aao_1") + ".pdf", "graphic", true);

What you are looking to do is referred to as arbitrary chunking. You can search the forums for plenty of examples. I've attached a 20 up sample that you should be able to adapt. The key components are two things you need to add to OnRecordStart: FusionPro.Composition.chunksBreakStacks = true; if (FieldChanged("Group")) FusionPro.Composition.StartNewStack(); Where "Group" is whatever field designates a new imposition sheet. arbitrary-chunking-sample.zip

Give this a shot: var mn = Trim(Field("Middle Name")); return [Trim(Field("First Name")),(mn.length == 1 ? mn + "." : mn),Trim(Field("Last Name"))].filter(String).join(" ");

I have not used this so no guarantees here. First make sure the page_width__ field has a lower sort order number than the page_height__ field. Put the following script in the Note part of the page_width__ field. Make sure the doc_width and doc_height numbers are correct for your template. <script type="text/javascript"> var doc_width = 8.5; var doc_height = 11; document.getElementById("page_width__").onblur = calc; function calc() { document.getElementById("page_height__").value = parseFloat(this.value) * (doc_height / doc_width);} </script> This should automatically fill out the page_height__ field when you click out of it. You will likely want to set that field to be hidden before publishing the form. Let me know how it works out.

In the imposition file, try setting your bleed to 10" and under layout, your horizontal spacing to negative 20". You wont see the left page because it's covered with the bleed grid but it will show up on the output. For what it's worth, this bug plagues me as well. Fortunately this bleed workaround seems to work a lot of the time.

I seem to be having this issue as well. It happens when an imposition is applied. This was tested by creating a blank PDF, input file set to none, record range set from: 1 to 1. Composed with an imposition, locally and to the API. Both versions append a 1. Turn the imposition off and the 1 goes away.

Select the text frame you want to apply the wrap to. Click the button in the properties palette shown in the attached image.

Maybe I'm misunderstanding, but you might consider putting the imb in its own text frame then copyfitting an address frame directly above it.

There's an example of how to do this on the last 2 pages of the PDF posted here: http://forums.pti.com/showthread.php?t=373

The only way I am aware of how to do this is posted here: http://forums.pti.com/showpost.php?p=15225&postcount=9 Just set your page count in the imposer to 1.

The span tag has a Shading attribute. If you want to change everything globally you can do something like this in OnRecordStart: for (var f in FusionPro.Fields) { var text = '<span color="PANTONE ###" shading="50">' + FusionPro.Fields[f] + '</span>'; FusionPro.Composition.AddVariable(f, text, true) } It's probably bad form because the span tag is wrapping paragraph tags, but it seems to work okay. Sources: http://forums.printable.com/showthread.php?p=10580 http://forums.pti.com/showpost.php?p=1819

It certainly appears the imposition is applying clipping to the entire document, slipsheets included. Fortunately it includes bleed. So by adding a 10 inch bleed to the document and then discarding it on the layout itself, it opens up the clipping path to a large enough area to show the entire slipsheet. Obviously this is not a fix, but it does work in this one case where the file didn't actually have bleed. Attached is the revised imposition file so you can see what I mean. And yes, I realize this is an insane way to get around it. Slipsheet_Test_Imposition_bleedfix.fpi

I'm having the exact same issue as indicated in the original post. I'm attaching a sample numbering job (no input file needed) where the slipsheet should be inserted every stack of 10. Instead of showing the entire sheet, it clips the artwork to the trim size indicated in the imposition file. I would love to know if there is a workaround for this.Slipsheet_Test_FP.pdf Output Sample.pdf Slipsheet_Test_Imposition.fpi

When you click the text box to open the Variable Text Editor you will see a "Tabs..." button. Make sure you select all the text or the whole line the rule is on. With it highlighted, click the button and you can change the settings in there. You can also do it programmatically by using the paragraph <p> tag which is outlined in the TagsRefGuide PDF under markup tags.

You can add multiple non breaking spaces in succession but you might consider just setting up a tab. It will give you more control over the exact positioning. return "such as divorce<br> and child custody"; vs return "such as divorce<br><t>and child custody";

I had the same issue. You can add a JavaScript redirect to the Home Page custom text. <script type="text/javascript"> window.location = 'https://marcomcentral.app.pti.com/*****/*****/catalog.aspx?uigroup_id=*****'; </script> Replace the asterisks with your store info.

http://i.imgur.com/TKYDihU.png This screenshot was just taken on 9.2.30 running Windows 8.1, Acrobat 11.0.08, and Pitstop 11 update 2. For me it is always triggered when I go to compose, locally or to the API. Clicking OK once does not clear it. I usually have to OK it like 10 times or so, I just hit enter rapidly until it goes away. It is also almost always triggered if I have preview turned on and I click save. Turning preview off does seem to help most the time and I don't get the error. This same problem exists on another Windows 7 workstation where FP Designer is installed along with Pitstop 11. Is 9.2.35 available for the PC?

This same error occurs with Pitstop 11. I've used FP 7, 8, and 9 with Pitstop 11 and only encounter the error with FusionPro 9. It's clear that the issue is coming from Pitstop as it has the icon for it in the error prompt. The odd thing here is that it is not triggered by earlier versions of FusionPro (at least on the 2 machines I tested it on). I'm hoping it goes away when 13 comes out as it is extremely annoying to deal with on a constant basis.