Jump to content

Dan Korn

Administrators
  • Posts

    4,863
  • Joined

  • Days Won

    16

Dan Korn last won the day on February 2

Dan Korn had the most liked content!

4 Followers

Converted

  • Location
    Chicago, IL

Converted

  • Occupation
    Senior Development Engineer

Converted

  • FusionPro Products
    Yes

Converted

  • FusionPro VDP software version
    12

Converted

  • OS
    Mainly Windows 10 Pro and macOS 13

Converted

  • Acrobat Version
    Acrobat DC
  • Homepage
    http://fusionpro.com
  • User Title
    FusionPro Senior Engineer / <b>Forum Moderator</b>

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Dan Korn's Achievements

Grand Master

Grand Master (14/14)

  • Reacting Well Rare
  • Dedicated Rare
  • Conversation Starter Rare
  • First Post Rare
  • Collaborator Rare

Recent Badges

5k

Reputation

  1. I think you can accomplish this in PostScript output by going to the menu FusionPro -> Advanced -> Page Media, and in the Insert Command File dialog, add a file with a stapling command to the first page. Or possibly the last page. You can also accomplish record stapling and other finishing options in JDF.
  2. Well, yes, the template page, which you are presumably setting as the FusionPro.Composition.impositionSheetBackgroundFrontPage in OnJobStart, is named "background," and the content there is indeed in the background, that is, covered up behind the imposed pages, even behind the static background of the imposed pages. So even though you're calling BringToFront on the frame, it's only bringing it to the front of that background page, and it's still behind the imposed page content. Maybe you just need to check the "Suppress static PDF background in composition" box on the Graphics tab of the Composition Settings. Or perhaps some of your frames are filled with a White background color which you need to change to None. As usual, it's hard to be more specific without seeing the job files.
  3. Thanks, I see the problem. I'll make a bug report and we'll analyze this.
  4. Error 1207 is "too much recursion." This is related to a text replacement rule, either a call to FusionPro.Composition.AddTextReplacement() in a JavaScript rule, or one of the "Replace Text" or "Global Replace Text" Form rules, or more likely, a combination of multiple text replacement rules. You probably have one rule that does something like "replace A with B," and another rule that does "replace B with A," and that sets up an infinite loop, or infinite recursion, which never gets resolved. As is my usual mantra, I would have to take a look at the job to figure out exactly where the problem is.
  5. I've been trying to reproduce this but have not been successful. I think it might depend on specifically what your rule is returning. Can you post a minimal sample job which demonstrates the problem? (A collected job WITHOUT the fonts, or, even better, a PDF template with "None" data source.) P.S. The screenshots are helpful, but are pretty downsampled. It might be better to post a cropped picture just of the part of the page in question rather than the entire Acrobat window.
  6. Thanks mailstar. Regarding performance/speed, we do have some enhancements in the works along those lines. That said, any significant architectural changes, such as multi-threading, would likely be targeted towards FusionPro Server and Producer, which run on Windows only, and not towards Creator (on either Windows or Mac). Also, it's a very badly-kept secret that Creator already runs faster on Mac than it does on Windows (though Server and Producer are still faster, especially for high-volume jobs). So I wouldn't expect much to improve for your Mac-based Creator workflow. Things might be slightly faster under native Silicon than under Intel emulation via Rosetta, but again, I wouldn't expect anything significant. Also, in my experience, 99 percent of FusionPro templates which have "many text/graphic frames" have been painstakingly put together by copy-and-paste, and also have dozens of rules to populate all those frames, and often the logic in those rules is very repetitive, which makes FusionPro do much more work than it should to accomplish what you want. Usually these kinds of jobs can be greatly optimized, and made more maintainable, by centralizing all of that logic into just a few rules, using things like the "Re-evaluate this rule for every text flow" setting, repeatable components, on-the-fly frame creation, and other strategies to abstract out the business logic. I would bet that kind of thing could be done with your jobs. I would have to see one of them to offer suggestions, of course, and I can't commit to fully analyzing and optimizing it, but I'm sure I could point you in the right direction. Regarding feature updates, thanks for the feedback about Copyfitting and the Drag and Drop rule. Can you please elaborate about bullet points? You can use the &bull; entity to output a bullet, generally followed by a <t> for a tab. We do have an internal JIRA database of bug reports and enhancement requests. It's not public, but when issues are reported by multiple users, those do count as "votes" of a sort to inform us that they should have a higher priority. Thanks again for the feedback. Please keep it coming! (Feel free to start a new thread about any specific suggestion or issue.)
  7. Thanks for asking. As someone who's worked on FusionPro for a long time, knowing that there's interest like this in the future of the product is heartening. We don't tend to release public roadmaps. Probably the main reason is that plans and timelines can change, based on a myriad of factors, some of which are beyond our control, such as changes that Apple, Microsoft, Adobe, and various standards organizations make that we have to keep up with. I can say that we are actively working on support for native Silicon chips (M1, M2, M3, etc.) on Mac, and that we have several enhancements planned for FusionPro 14 which I think people will be excited about, things that will make template-building easier. Beyond that, we have a lot of longer-term plans and ideas on several fronts, from architectural improvements to new areas of functionality. Sorry I can't be more specific. But just to give a bit of insight, we do get pulled in a lot of different directions. Some of this is the nature of the digital printing/publishing industry. On the one hand, print is far from dead, and printing technology continues to improve and advance, and there is a huge demand for improvements to things like imposition, for finer control over barcodes, charts, and tables, color correction, and other things that go into putting toner on paper or other substrates and fulfilling print orders, including postal sorting and barcodes in different countries, as well as an ever-growing market for label and package printing. On the other hand, there's rapidly increasing demand for digital delivery PDFs, which are primarily viewed online, and which, according to various regulations in different countries (and just because things should be this way), need to be accessible to people with visual impairments, which means they need to conform to accessibility specifications for tagging and reading order, which, when you're merging in variable content with static content from the background PDF, can get complicated. We've also been working for a long with partners around the world, mainly through Ricoh, including our friends in Ricoh Japan, to add typesetting features specific to Japanese, Hindi, Arabic and Hebrew, and many other languages, which have a lot of complex requirements. And we work with many partners on integrations, including with MarcomPortal, EFI DSF, Avanti, RSA's WebCRD, and others. So, there's a lot on our plate, and just prioritizing all of those backlist items is a challenge. The other thing I can say is that feedback here on this forum is definitely taken into account in our planning. Your ideas, suggestions, and even problems you report here do inform our priorities. So... what do you want to see on the roadmap?
  8. ... from what version? What were you running previously? Can you be more specific? What is the failure mode? Does it not recognize any new records at all? Or does it think every line is a record? Can you post a minimal sample job that reproduces the problem?
  9. FusionPro VDP version 13.1.4, which fixes this, is now available at our Downloads page, and is supported in MarcomPortal. Thanks for you patience and sorry again for the trouble.
  10. Thanks. That code looks right for what you're trying to do. Clearly it is working for the preview. So I'm not sure why it's not working for the press file. I wonder if somehow the composition being run for the press version is using a different version of the template, or at least a different .def file without that OnRecordStart rule in it.
  11. Downloaded from where? MarcomPortal? DSF? WebCRD? Some other online system?
  12. Okay, well, as I noted before, we've reached the limit of what I can diagnose by looking at your job through the keyhole of just the rule. I would need to see the entire job in order to figure out what's going on. But I think you should be able to tweak those settings in the OnCopyfit rule, as I also mentioned earlier. Have you tried that?
  13. Just checking, you did go into the Frame Properties for that frame and click Overflow, then clicked the "Adjust text to fit" button, right?
  14. Newlines should work, but you need to include them in a literal string, between quotes, like so: if (Field("Program2") == "") return ""; return "\n" + Field("Program2abbr") + ' Student Sponsorship of Up to ' + val + "\n"; You can also use <br> tags as Alex suggests, but in that case, I would recommend calling TaggedDataField instead of Field, in case the data contains "special" characters such as ampersands, like so: if (Field("Program2") == "") return "" return '<br>' + TaggedDataField("Program2abbr") + '&nbsp;' + "Student Sponsorship of Up to" + '&nbsp;' + val + '<br>'; Though the first version seems simpler. Note also that you don't need the "else" statement after the "return".
  15. I see, this is about the Define HTML Form feature (aka "Web Collect"). Thanks for using this! Glad to know it's still supported in WebCRD by our friends at RSA. So you can create Parent/Child pick list fields, where the selection in the parent forces a selection in the child. And you could mark the child field as hidden (not visible), so that the child selection isn't shown. But there's no way to conditionally hide a field based on another field's selection. The HTML Form Definition doesn't support that level of sophistication, in terms of complex field dependencies. You might need separate forms for each input type to accomplish what you want. Though there may be some other kind of more advanced custom input form offered by WebCRD; that would be a question for RSA. P.S. It's "FusionPro" (no spaces).
×
×
  • Create New...