Dan Korn

Yes, this is possible. Are you using a font which supports Japanese text?

No. For the purposes of Text Measurement, FusionPro calculates the size of a PDF graphic based on the first page. Other than using two separate PDF graphics, I don't know of any way around this. Nor would I expect any particular changes to the underlying text measurement capabilities, which, quite frankly, weren't really designed for the use case in this thread. No, this is a composition-time issue which has nothing to do with Acrobat. The calculations regarding rotated pages in the background (template) PDF happen in code specific to the Acrobat plug-in, which sets up the parameters for composition, not in the actual composition code where things like graphic scaling and text measurement happen. Exactly how FusionPro "knows" that a page is rotated is via a call to the Acrobat SDK, but further details about the inner workings of the plug-in get into the "no user servicable parts" territory.

Search either this forum or the FusionPro Rules Guide for "SetBodyPageUsage".

You need to create multiple Unused Body pages, each with a different page media assigned (via PPD, JDF, etc. as enumerated in my previous post), and the same variable frames. Then you can use FusionPro.Composition.SetBodyPageUsage() in your OnRecordStart rule to activate the page with the desired media.

Depending on the output format and the capabilities of the press, you can use either VDX page media settings, PostScript command files, PPD settings, or JDF to select media in FusionPro 7.2.

Please create a new thread with your specific question. If you can post an example, that would be great.

Yes, that's correct. You could also do this: text.Rows[0].Cells[0].Rulings.Top.Color = "Red"; text.Rows[0].Cells[0].Rulings.Top.Thickness = "Thin"; text.Rows[0].Cells[0].Rulings.Bottom.Color = "Green"; text.Rows[0].Cells[0].Rulings.Bottom.Thickness = "Thin"; text.Rows[0].Cells[0].Rulings.Right.Color = "Blue"; text.Rows[0].Cells[0].Rulings.Right.Thickness = "Medium"; text.Rows[0].Cells[0].Rulings.Left.Color = "Black"; text.Rows[0].Cells[0].Rulings.Left.Thickness = "Medium";By the way, this entire table API is defined in the Builtins.js file, so feel free to look at the code and see how it generates the table tags. Please do not edit the Builtins.js file, however. Please feel free to suggest improvements to the API as well, since it's still open for enhancements. For instance, in the latest 7.2P1k release, there's a new FPTable.NewRow() function which returns the newly-added FPTableRow object, so that you don't have to remember the row index.

This is called "straddle" in FusionPro. From the original post: These properties correspond to the HStraddle and VStraddle attributes of the <cell> tag, as documented in the Tags Reference Guide.

No, not currently, unless each series has the same number of records. Yes, this will be possible with the new arbitrary chunking feature in FusionPro 8.

Yes. I'll answer in that other thread to keep this one on a narrower topic.

Yes, if you create the OnNewOutput file rule, you can name the output file whatever you want by setting FusionPro.Composition.outputFileName. You can base it on a record number such as FusionPro.Composition.processedRecordNumber, or you can keep your own global counter variable. You can use FormatNumber to pad with zeros.

Generally, bringing jobs made with newer versions of FusionPro Desktop/Designer into older versions of FusionPro is not supported. However, there's probably something in the composition log (.msg) file that's a clue as to what's going wrong.

How are you bringing the data in from Excel to FusionPro? Are you exporting to a flat file, like a CSV file? If so, that's the input to FusionPro, not the Excel file itself. So, what does the data look like in the flat file? You might need to fix something in Excel so that the CSV file has the data in the correct format. But still, you should be able to do this: return FormatNumber("00000", Field("ZIP CODE"));

Assuming the ZIP CODE field contains just the five-digit Zip code in the data, you should just be able to use that field directly in your text frame. I don't think you need to use a JavaScript rule at all.

There's not much more that can be done here in the context of the User Forum to help. Please contact FusionProSupport@PTI.com for further assistance.

Make sure you open ports 12093 and 12083 for UDP, not TCP.

You need FusionPro 7 to generate QR barcodes. FusionPro 7 supports Acrobat 7, 8, 9, and 10.

Yes, you need to have the tray sort done in the data file before composing with FusionPro.

It's everything. By "Suite," Mark was referring to FusionPro Desktop, Direct, and Server, all of which support creation of barcodes in the listed formats, either by using rules ("algorithms") to generate the barcode from some arbitrary data in the job, or by taking some previously-generated barcode data and typesetting it. (FusionPro Expression is not part of this "suite", even though it has FusionPro in its name, as it didn't exist at the time of Mark's post.) In addition to the formats specified in Mark's message, FusionPro 7 and later also generates QR barcodes.

It turns out that the thing to switch off of in a MarcomCentral composition is the IsOnlinePreview() function. Therefore your OnRecordStart rule could look something like this: for (var pageNum = 1; pageNum <= 14; PageNum++) FusionPro.Composition.SetBodyPageUsage("Preview " + PageNum, IsOnlinePreview()); for (var pageNum = 1; pageNum <= 14; PageNum++) FusionPro.Composition.SetBodyPageUsage("Press " + PageNum, !IsOnlinePreview()); Where you've gone into the Page Usage dialog and named all of your pages "Preview 1", "Preview 2", etc., and "Press 1", "Press 2", etc. Although I still don't see why this can't all be done with FP Imposer.

Why not? What exactly do you need to do that FP Imposer can't handle? Did you try using FP Imposer? Did you try right-clicking on the pictures of the pages in the upper right pane and selecting one of the "Rotate" options? Yes, as I said before, you need first need to name all your pages in the Page Usage dialog, then conditionally call the FusionPro.Composition.SetBodyPageUsage function for each page in OnRecordStart. But, as I also said before, exactly how to determine whether MarcomCentral is doing an online preview, in your rule, is something you need to ask about in the MarcomCentral forum.

Ah, this was the context that was missing. Please ask questions specific to MarcomCentral in the MarcomCentral forum. That said, to do saddle stitch output in FusionPro, you don't need to have two whole different sets of pages, one with the "regular" layout and one with the saddle-stitch order. You just need to use FusionPro's built-in imposition capabilities. There's a "Saddled Stitched" option on the Layout tab in FP Imposer which does this. Then you can just check or uncheck the first box on the Imposition tab of the Composition Settings dialog to switch between the two modes. In fact, I believe that MarcomCentral does this automatically, and shows the un-imposed pages (the "end user" view) for preview, but composes using imposition (i.e. the "printer spreads") for press output. But that can be clarified on the MCC forum.

I'm not sure what you mean by "preview" in this context. In FP Desktop, all body pages are previewed. If you mean that you only want to compose a subset of pages, that's done by naming pages and calling the FusionPro.Composition.SetBodyPageUsage function in OnRecordStart. Search this forum or the Rules Guide for SetBodyPageUsage for more information. Also, instead of painstakingly lining up 30 or so frames on multiple pages, you could write a JavaScript rule to dynamically generate tables for the calendar months, with logic such as this. You could reuse the logic and compose the job for different years without having to redo the whole thing each year.

I presume you mean that you have an unknown number of pages to insert. Otherwise, you could indeed just link up frames between the two body pages. You can't have more than one overflow destination frame (with the "Overflow To" box on the Frame Properties dialog checked) on an Overflow page. I can't imagine too many scenarios in which the output document would make sense to a reader with multiple overflows on the same page. Plus, in the case where you have "1 item in A and 300 in B", you'd have a lot of of wasted blank space on multiple overflow pages. You might consider placing the items in a two-column table, which could overflow to a single overflow page. Or use two overflow pages, one for each set of items.

What versions of FusionPro and FP Expression? There were some issues like this which were fixed in more recent versions. If you can collect up a minimal sample job which demonstrates the issue, you can send it to Support, or you can post it here and I can take a look at it.