Dan Korn

FusionPro does support Unicode, such as Japanese, but not color emoji characters. You can use an inline graphic instead in your FP template. Add a resource with a picture of a balloon (or a smiley face, or whatever other emoji picture you want), then make a Graphic rule to return the resource, and insert that rule into the Text Editor. Now, when you mention, "the form," I assume you're talking about the web form in Marcom Portal. That probably should not allow emojis. I would ask your Marcom support representative about that.

We are working on another patch build to fix this. We hope to make it available next week. Sorry for the trouble.

Yes, any character that's not modified by the rule to be in a particular font and size will be in whatever font the text is in nominally, i.e. whatever font and point size was set for the rule in the Text Editor. If you want to specify both fonts in the rule instead, then you can just put another font tag in front of everything, like so: var s = "Mr. and Mrs. John Doe and Family"; return '<f name="Arial">' + TaggedFromRaw(s).replace(/[A-Z]/g, '<span font="Helvetica" pointsize=20>$&</span>'); If you want the point size of the capital letters to be a multiple of the original point size, rather than hard-coded to something like 20 points, then you can do this: var s = "Mr. and Mrs. John Doe and Family"; return '<f name="Arial">' + TaggedFromRaw(s).replace(/[A-Z]/g, '<span font="Helvetica"><magnify factor=200>$&</magnify></span>');

I'm having trouble following which pages of which PDFs you're trying to bring in just from your description. A collected job, or some kind of example, would be worth a thousand words.

Something like this: var s = "Mr. and Mrs. John Doe and Family"; return TaggedFromRaw(s).replace(/[A-Z]/g, '<span font="Courier New" pointsize=20>$&</span>');

This sounds similar to this question from this thread from a few days ago: Though I think, in this case, you could just add the pages from the two FP template PDFs together, into a single template with all seven pages, and just compose that.

Your description of the job is good, but this is still a bit tough to figure out in the abstract. Some files might be helpful to visualize what you want. The most straightforward way to do something like this is probably just to add all the various pages from the multiple PDFs into a single master template, as Unused Body Pages, and use FusionPro.Composition.SetBodyPageUsage in OnRecordStart to pull the pages you want per-record. That said, there is a new feature as of FusionPro VDP 13.0 that lets you bring in pages from other FP templates, with their variable frames, into a job, as repeatable components. This is done by exporting the DIF files from the "foreign" templates, then you can pass the name of each DIF file, and a page number, to the FPRepeatableComponent object, to bring in the page, with its variable frames, into the main job as an inline repeatable component, in a text frame in the master job, overflowing that text frame to Overflow pages, as in the standard multi-page PDF resource example. I might be able to provide an example of this; I have to check whether the one that we did for another customer can be shared.

If you think about it, the total number of records doesn't change per-record, it's a job-level thing. And it has to be calculated ahead of time, in a preprocessing step, and you obviously have to tell FusionPro to do that preprocessing at the start of the whole job. FusionPro doesn't do preprocessing by default, as there is a bit of a time cost to it, but in cases like this, there's no other way to know for sure how many records will be composed. Some things can be examined and calculated at rule validation time, in the Rule Editor, like the values of fields, but other things have no context outside of a composition, like activating pages. The Validate button in the editor is for convenience, to help in the development and debugging of rules, but ultimately, the composed output is what matters. Sure, glad to help. You're part of a great community here.

You can set up a custom imposition sheet background. Duplicate your static background page as a page of type Template, then you can create the "Set Imposition Background Rule" from the Event tab of the New Rule dialog to assign it as the background. Then create another Body page of the 1-up size, and a 3-up FPI file.

Any property of FusionPro.Composition is going to be valid at composition time, but not at rule validation time. Compose the job and the output should be correct.

This is fixed in the 13.1.3 release, which is now available. Apologies again for this slipping through in 13.1.2.

This year just started. There's no official roadmap date for this, but I would say that Yes, I would expect it to be sometime in the next 12 months.

If you want the true number of total records, you can either use the $outputrecordnumber and $totalrecordcount variables in the Text Editor, or create a rule like so: return FusionPro.Composition.outputRecordNumber + " of " + FusionPro.Composition.totalRecordCount; But either way, you need to set the job to do preprocessing to determine the total number of record, in OnJobStart, like so: FusionPro.Composition.forcePreprocessing = true;

Thank you for that confirmation. Hmm, it worked for olllllllo. Are you sure you're referencing the FPI file that you changed? If so, please collect and post a job that reproduces the problem. A patch build is in the works and we hope to make it available soon. Apologies for the trouble.

Okay, thank you for attaching that job. It was very helpful to me in identifying the problem. It's an issue when Infinite Stack is set AND the Stack Count is set to 1. So the workaround is to set the Stack Count to anything other than 1, and Infinite Stack will work again. This will be fixed in an upcoming release.

The 13.1.2 FusionPro app and the Acrobat plug-in on Mac are still Intel executables, and require Rosetta to run on newer Silicon (M1 and M2) chip Macs.

The attached infinite stack job composes correctly for me in FusionPro 13.1.2 on Mac. Can you please verify whether the attached job works for you? Also, can you please collect up a job which reproduces the problem? PresidioPostcard-infinite-stack.zip

No, so far we have not had enough details about the problem to analyze it, nor a job which reproduces the issue. Is it an issue with the FP Imposer program? That is, is it that saving a new FPI file doesn't have the "Infinite Stack" set correctly? Or is it a composition issue, where if you take an existing FPI file, it doesn't compose correctly?

Nothing was caught in our regression testing, which includes stacked imposition jobs. Can you please post a sample job which reproduces the problem, and a clear explanation of what the expected output is, and how it's different than the actual output? Also, in what previous version of FusionPro did this work differently?

Thanks, I have un-pinned this thread.

You can't have a set height for table rows. The whole idea is that cells will expand as necessary to accommodate their contents, and that each row will expand to accommodate the largest cell in the row. But you can specify a minimum row height, with the minHeight property, and, as long as none of the cells have so much data that they need a larger height, every row will be that minimum size. You would do this not in the Table Style rule that you show converted to JavaScript, but in the Table rule itself. Better yet, don't convert either of those rules to JavaScript. Instead, create a new JavaScript rule to post-process the table, like so: var table = Rule("Table - from data rule: Your Data"); // <- your table rule name here for (var r in table.Rows) table.Rows[r].minHeight = HundredthsOfPointsFromText("1 in"); return table; Make sure this rule has the "Re-evaluate this rule for every text flow" and "Treat returned values as tagged text" boxes checked. Then use this new rule in the output. Also, note that a whole new table UI, with support for minimum height, without having to write any code at all, is in the works for a future version of FusionPro. All that said, I do wonder if a table is the best approach to the job as described, "for a sheet of labels." To me, that description suggests you want to create an imposition job, where the page in your FusionPro template is simply the 2.625x1 inch size, and you create an imposition template (an FPI file) with the FP Imposer tool to output these pages of labels onto imposed sheets. Then you don't need a table or any code or rule to lay them out; the imposition system does it all for you, based on the settings in the FPI file.

So, two separate questions here. For the European numbers, I would create the Choose Phone Format rule so that it returns the number with dashes (format 123-456-7890), then create another rule, a JavaScript rule this time, and have it replace the first dash with a space, like so: return Rule("Choose Phone Format: Phone").replace('-', ' '); And use the JavaScript rule in the output. Note that the main Form rule does NOT have to be converted to JavaScript. The other rule can do the work to tweak the result. The country codes are another story. The current logic behind the Choose Phone Format rule doesn't support multi-digit country codes, nor those variations in the following digits. It's not really designed for international numbers like that. I would assume that such numbers are presented in the correct format in the first place in the data, and that trying to reformat them would possibly be destructive, but you seem to know more about these formats than I do. You could trying Googling for something like "JavaScript format phone number with country code" to see what others have come up with.

Okay, so based on that additional information, there are several ways you can accomplish this. Method 1: Create a series of Unused Body Pages, with names such as "Header 1", "Header 2", etc. Then in the OnRecordStart rule, you can call FusionPro.Composition.SetBodyPageUsage to activate the pages as needed. I can't tell you exactly what the code should be without seeing your job files, or at least the data, but it would be something like this: for (var i = 1; i <= 8; i++) FusionPro.Composition.SetBodyPageUsage("Header " + i, Trim(Field("Header Data " + i)) != ""); Please refer to the sections "How to switch body pages during composition" in both the User Guide and the Rules Guide for more information, or search this forum for "SetBodyPageUsage" for lots of other examples. Method 2: If the job contains only these "Header" pages, and nothing else, you can accomplish this with a single page job, with a single text frame, and some code in OnRecordStart. Again, not having your data file, I have to guess a bit at your field names, but it would be something like: var HeaderData = []; for (var i = 1; i <= 8; i++) HeaderData.push(Trim(Field("Header Data " + i))); HeaderData = HeaderData.filter(String); // remove empty items FusionPro.Composition.repeatRecordCount = HeaderData.length; FusionPro.Composition.AddVariable("Header", HeaderData[FusionPro.Composition.repeatRecordNumber - 1], FusionPro.inputTreatFlatDataAsTagged); Then you can go to the Text Frame, edit the text, and in the Variable Text Editor dialog, type "Header" (without quotes) into the Variable box, and click Insert. Method 3: Use a Repeatable Component with the text frame in it, and insert instances of the Repeatable Component for populated data fields into a Body page text frame, which overflows to an Overflow page. This is a bit more complex; I can provide more information if you want to go this route.

MarcomCentral® is proud to announce version 13.1 of the FusionPro® VDP Suite! This release is a follow-up to our FusionPro VDP 11 launch, which introduced some major new functionality, as well as a new subscription pricing model. The FusionPro® VDP product suite includes both Mac and Windows releases of FusionPro VDP Creator, as well as the Windows-based FusionPro VDP Producer and FusionPro VDP Server. With the new subscription model for FusionPro 11, FusionPro VDP Creator will now include FusionPro Expression for no extra charge. New features and improvements include: Support Adobe InDesign 2024 (Version 19) on both Mac and Windows Converted barcode rules to generate graphics which can be resized with great precision. Added support for ink spread on most 1-demensional barcodes to support printing on porous substrates. Added ability to insert graphics rules inline in text frames. Modified FP Imposer GUI to show more of the side menu at a time and reduce the amount of scrolling needed. Added support for auto updating of rules and other components so that fixes can be distributed without a full install. Added support to accessibility, where PDF files that have accessibility features are properly imported into a PDF output stream, retaining their accessibility tree structure. Added support to begin a new FusionPro template within FP GUI. Create a new blank PDF to build a template on inside FusionPro. Added option to delete a page from a PDF background using FusionPro GUI. FP Designer record to compose is synchronized to the record being previewed. Record being previewed is synchronized to the record being viewed in the Building Blocks dialog in the rule editor. Added feature to log the location of every graphic found, indicating the folder where the graphic was found. FusionPro v13.1.2 has the following fixes: Fixed occasional crash on Macintosh when accessing job log via FP Producer Monitor Fixed error of not being able to insert registered trademark and other symbols in Drag and Drop rule editor. Fixed issue where the background of an imposed sheet is sometimes cut off. Fixed issue in FP Imposer where the removal of bleed between rows or columns is incorrect on stacked imposition. (Case FP-407) Fixed issue in FP Imposer GUI where double-clicking on a file does not fully populate the properties in the FP Imposer GUI. Improved handling of fonts with errors so they correctly load. Resolved speed issue with large number of fields (over 300) on Windows. Improved error messages when attempting to register software with a serial number that has already been used the maximum number of times. Resolved case where setting to “treat field values as tagged” was ignored for Secondary Data Sources (case FP-668) Resolved issue where Change Text Case affects special characters not displaying in the variable text (base FP-530) Fixed issue where square box character appeared in Ruby Rule in some fonts Fixed issue where external formatted text resources default to left alignment when loaded into text frame When Tate Chu Yoko is enabled, vertical alignment is disabled. All font files created by FusionPro are now be removed after uninstall Fixed issue where when copyfitting, the magnification level of character width and height is reversed when dealing with vertical text If the bleed when exporting from InDesign is set to 0, sometimes a default bleed value from the print driver is inadvertently applied (Case FP-541) FusionPro v13.1.3 has the following fixes: FIxed infinite stack. Fixed crash when accessing Chart Properties on Mac. Allow installation of plug-in for InDesign 2024 point release 19.0.1. Show Auto Updater UI in selected FusionPro language. FusionPro v13.1.4 has the following fixes: Change page name sometimes crashes Cannot make new rule if language is Italian Improvements to Italian translations of Imposer GUI Black was not appearing in color dictionary on export from InDesign 2023 and 2024 Add/Remove Programs GUI had wrong uninstall version listed on Windows FusionPro v13.1.8 adds support for Adobe Acrobat Pro 2024 on Windows and Mac. FusionPro VDP 13.1 has passed testing on Windows 11, Windows Server 2022, macOS 13 (Ventura), and macOS 14 (Sonoma). More information about new FusionPro features and pricing can be found at: https://fusionpro.com/faq/ Look for even more new features in upcoming releases! Additional information about the FusionPro VDP 13.1 release, feature set, and addressed issues can be found in the FusionPro VDP 13.1.8 release notes as well as the FusionPro VDP Software Version History page. Upgrades and New Licenses FusionPro VDP customers can download the version 13.1 release from the FusionPro VDP Software Download page. Existing FusionPro VDP 11, 12, and 13 subscription customers can upgrade to FusionPro VDP 13.1 for no extra charge, with their existing FP11, FP12, FP13, or FSUB serial number. (If you are not sure whether your serial number is subscription, please contact Support.) If you are using FusionPro Creator versions older than FusionPro v11, please read our FAQs on information regarding FusionPro v11 and 12. FusionPro VDP Producer/Server and MarcomPortal customers who are active on their maintenance are entitled to an upgrade of their FusionPro VDP software. FusionPro VDP Producer/Server customers can obtain their upgrades by contacting the FusionPro VDP Support team while MarcomPortal customers can contact their MarcomPortal Support representative to inquire about the upgrade. Please note that pricing and upgrade eligibility may change at any time. MarcomPortal Support of FusionPro VDP Creator 13.1 Templates Templates from FusionPro VDP through version 13.1.4 are currently supported in the MarcomPortal application.

It sounds like you want to use Overflow pages. Please refer to the section "Overflow Text" in the FusionPro VDP User Guide, and to the installed Statement tutorial.