Jump to content

mhilger

Registered Users - Approved
  • Posts

    327
  • Joined

About mhilger

  • Birthday March 19

Converted

  • Location
    Chicago

Converted

  • FusionPro Products
    No

Converted

  • Acrobat Version
    Acrobat 9.x

Recent Profile Visitors

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

mhilger's Achievements

Community Regular

Community Regular (8/14)

  • First Post Rare
  • Collaborator Rare
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

5k

Reputation

  1. Hello, Windows Server 2008 isn't officially supported for FusionPro Server at this time but the team is actively working on it. While some customers have been using 2008 with some degree of success, there are some known issues that our development team is aware of and looking to address in the FusionPro product. Regarding your font loading issue, one way around this might be to look at your workflow itself. I assume you are using FusionPro Desktop on Mac or Windows machines and those users perform a "Collect" on their template which is then sent over to the FusionPro Server machine. In the collect process, the Desktop user has the option to collect fonts from their Desktop machine along with the job. This makes the Assets.data file in the collect process. Just make sure that the Assets.dat file collected for a job resides in the same location as your .dif template file for the FP Server composition. FusionPro will detect the Assets.dat for that job, decrypt/uncompress the font data inside of that file, and use that exact font data for the composition. So, using Assets.data will negate the need for FusionPro Server to use any locally installed system fonts on that machine. hth.
  2. Mac, Hmmm.... Do other jobs compose for you? Perhaps open one of the FusionPro tutorial jobs like the Cellphone job (located in the FusionPro Tutorials folder) and try composing it. Does it give a 1096? If it does give a 1096, I would say do a re-install of FusionPro as it looks like a deeper issue. If that job does work, try exporting a simple blank page from Illustrator to PDF using the same method you used to export the original template. In Acrobat, use the FP data-def wizard to chose data source of "None". Draw a simple text frame. Now try composing. Is that throwing a 1096? If so, it might be something with the way the PDF is generated from Illustrator that's causing the issue. In any case, our support team is probably the best option for you at this point. I would send an email to fusionProSupport@printable.com which goes directly to the FusionPro VDP support team (Jeff can assist as well but his focus is mainly on the MarcomCentral application). If
  3. Hello Mac, The 1096 error is a general abort error that FusionPro can throw when an unexpected error occurs. We've seen this error be thrown when there are read/write issues with the composition process including read-only files/folders or lack of disk space. Do you see this error immediately when the composition starts, or does it happen part-way through the composition? Now there's a number of things you can try here to resolve this. Hopefully one of the following items will resolve this issue for you: 1) Make sure you have sufficient free disk space. 2) Make sure you have read/write permission to the folders where the base template files reside as well as the requested output folder. Even if your user account has admin privileges, check to make sure the folders themselves have read/write set on them. 3) (Assuming this is a FusionPro Desktop composition vs. a FusionPro Direct or Server composition) Delete any files in the folder where your PDF template resides that have extensions of .dif, .def, and .cfg. These are FusionPro files that are generated automatically when you compose with FusionPro Desktop based on the template and composition information located inside the PDF template itself. They will be regenerated on the next composition. 4) Try re-saving your PDF template in Acrobat to a new PDF file name via a "Save As". Acrobat will re-write the PDF template to disk and this sometimes can clean up bogus corruption data in the PDF itself. 5) If all the above fails, try and re-export your template from InDesign/Quark. You have 2 options here: - Option 1 -First, make a backup of your PDF template. Then, follow the steps that user rpatrick mentioned in an earlier post: "Open Indesign, make change, export out using the FP plugin, replace your FusionPro pdf that has all the variable done to it, when the pdf opens in Acrobat, click "NO," you do not want to replace the work that has been done. and re-import the FusionPro template information from your original files (the data definition info as well as the template layout)." - Option 2 - Short of re-doing all the work to design your template again, this method allows you to import all the FP settings from your original template. First, recrete the static PDF background (via an InDesign/Quark export to a new PDF or other means you use to make the PDF background). Then, you can import the data definition using the data definition wizard (3rd option on the first screen of the wizard) where you point to the .def file from your original template. This gives you the association to the data input file, the rules, and the resources of the original job. Next, you can import the FusionPro variable frame layout by going to FusionPro -> Advanced -> Import. Here, you point to the original PDF template file itself. This gives you, among other items, the frames with their settings and content.Finally, if you get this far and are still seeing the 1096, please contact our support team for further troubleshooting. hth.
  4. Hello, We were able to recreate this issue here as well. A bug has been entered into our isue tracking system and sent to our development team for analysis. Unfortunately, it appears that the only resolution for this issue is to remove FusionPro from the Acrobat plug-ins folder. We hope to resolve this in an upcoming release of the FusionPro product and appologize for the inconvenience.
  5. Hello everyone, Starting with the FusionPro v6.2 release, a change has been made to the FusionPro Direct and FusionPro Server products which users of those products should be aware of. FusionPro Direct and FusionPro Server v6.2 or greater will no longer attempt to compose FusionPro templates created with a NEWER version of the FusionPro Desktop product. For example, FusionPro Server 6.2 will not compose a template created with FusionPro Desktop 7.0 (a forthcoming release). FusionPro Server 7.0 will not compose templates created with FusionPro Desktop 7.1. This change has been made to prevent situations where templates that utilize new enhancements to the FusionPro template format (or even underlying template format changes that are not apparent to the user) are attempted to be composed with older versions of the FusionPro Direct or Server product which has no knowledge of this new functionality. The end result of such a configuration is quite unpredictable and can include crashes at composition time or missing/incorrect variable content. While this change will not affect any user for the time being (since v6.2 is the current version of FusionPro at the time of writing of this post), this is something that FusionPro Direct and Server customers should be aware of once the FusionPro v7.0 release is made available.
  6. I see a number of other folks have voted in this poll. Some really great information! Looks like we have users fairly well dispersed across all the major DFE's out there. Of course, with 10 VDP output formats in FusionPro, that shouldn't be a big surprise I guess. Thanks again to all that voted!
  7. Hello everyone, As you have hopefully already heard, Printable has released some significant enhancements to FusionPro Links. These enhancements are based off of continual feedback from our customers and represent many of the most sought-after new pieces of functionality in the product. Here's an overview of the new functionality: Personalized URLs with Personalization in Front of URL - In addition to personalization at the end of the URL (vip.domain.com/JohnSmith), a Campaign can now be generated with Personalized URLs at the beginning of the URL (JohnSmith.domain.com) Secure HTTPS Option for Campaigns - Campaigns can now utilize SSL encryption for Microsite visitors Include Form Response Data in Notification Emails - An option to include form response data in notification emails has been added Microsite Example to Pass Data to Subsequent Pages - A sample Microsite that shows the ability to collect form data, record that as a form response, and make that form data available to a subsequent page in the Microsite is now available Campaign Grouping By Status - All campaigns in the "View/Create Campaign" and "Response Overview" pages are now grouped by their status - Draft, Active, or Ended Campaign Notification Emails with HTML Formatting - All campaign activity notifications are now HTML emails as opposed to plain text. This allows for some extensive customization of the appearance of the notification emails Campaign Sorting in Response Overview Screen - Campaigns in the "Response Overview" page can now be sorted by name, create date, start date, or end date Microsite Variables with %%variable%% Notation - In addition to the <[variableName]> variable notation, variables can also be entered using %%variableName%% notation Links Menus Visible When Following Notification Link - When the link to the FusionPro Links system provided in an email notification is followed, that user will now see the FusionPro Links menu system after logging in Notifications Section UI Changes - Some slight UI changes to the Notifications section have been made Reporting Infrastructure Improvements - Reporting backend improvements have been made to improve the speed of report generation. Current customers will be able to take immediate advantage of these new features by simply logging into the FusionPro Links interface. In addition, the FusionPro Links help content (accessible via the "Help" link in the upper-right of the FusionPro Links UI) has been updated to reflect the new functionality. So to all FusionPro Links customers out there - enjoy the new release!
  8. Hello Paul, In fact, we are currently looking at stroke on text as an upcoming enhancement. We do have a number of other commitments that we have to meet in our 2010 delivery schedule but I can say that this is certainly one of those enhancements that is in the top 10 of what we are looking at implementing. As soon as we have more info on availability, we'll let everyone know. Thanks.
  9. Great question, Stack. As you may have heard, Adobe has said that the next release of their Creative Suite will not support PowerPC Macs either. Read about it here on the Adobe website. While I do not have any knowledge of when CS5 will hit the streets, analysts are predicting that Adobe will stick to its 18-month release cycle. So, we may be looking at CS5 in late Q1 or early Q2 of 2010. Supporting both Intel-Mac and PowerPC adds considerable overhead to our development, QA, and Support efforts. This overhead takes time away from core feature enhancements to the VDP product family that our users have requested over the years. You should see my whiteboard which has a number of VDP enhancements under consideration that I'm certain will resonate quite well with the users of the VDP products. As a Product Manager, I need to balance the delivery timeframe on that list against our support of a hardware platform hasn't been sold for 4 years.... While we do still support PowerPC, we eventually will likely drop this support in the future. We haven't made an official decision on this yet nor do we have a timeframe in mind. However, I can promise that WHEN we do decide to drop PPC support, there will be ample warning to our user community so you can best prepare. Thanks for bringing this up, Stack!
  10. Hello everyone, As you may have heard, Printable has announced our 10th VDP output format - AFP. This will be an add-on module to our FusionPro Direct and Server products as well as the MarcomCentral Web to Print offering. Unlike the other VDP output formats, which are quite device INDEPENDENT, AFP is a device DEPENDENT output format. Different printing systems that utilize AFP require different "flavors" of the AFP printstream with variance on such elements as DPI of elements in the print file (e.g. 240dpi vs. 300dpi) and color/B&W settings. It it Printable's intention to support the vast majority of AFP printing systems in our market but to do so, we need your help. We have validated our AFP with a partner-supplied viewer and we've successfully tested the output on a number of devices already. However, we would like to expand this testing to include other devices. If you are willing to assist us with this effort, please reply to this post letting us know or shoot me a message here in the forums. We'll be in touch with some questions about your device and will be able to supply some AFP output for you to test with. Thanks in advance for those willing to help us perfect this important new feature in our offering!
  11. Hi all, Printable is curious to know which version of the Mac OS you use with FusionPro Desktop. Sorry Windows folks - this poll only applies to those users of FusionPro Desktop on the Mac platform (and don't worry - we WILL support Windows 7!). Thanks all!
  12. Hi all, A couple users reported issues with the appearance of the FusionPro Intelligent Mail Barcode that is installed with the FusionPro Desktop product. This font is called "IDAutomation4State". Users have reported that they have to tweak the typesetting of the barcode so it passes Merlin with the USPS. Printable has reviewed the specifications of the Intelligent Mail Barcode from the USPS RIBBS website. In particular, this document outlines the requirements for this barcode: https://ribbs.usps.gov/intelligentmail_mailpieces/documents/tech_guides/SPUSPS-B-3200E001.pdf We did see that using the standard JS command to generate the barcode as well as the pre-built templated text rule we include (called "OneCode Barcode Rule"), that the barcode was outside of the bars-per-inch requirement (26 bars/inch vs the required 22+-2 bars/inch). Note: Our barcode font is typeset at 10pt. Any other point-size for this font will fall outside of the other requirements for the barcode appearance. To resolve this bars/inch issue, tracking of 5% can be applied to the typesetting of this barcode (again - at 10pt). You can apply tracking from the Paragraph Settings in the Variable text editor. Alternately, you can set tracking right in your JS rule using the <tracking> tag. Here's a sample script (using dummy data for testing) that shows this being used: return '<tracking newsize="5.00">' + MakeOneCodeBarcode("01234567094987654321", "012345678", null, null, null, null);For those of you who use the pre-built templated rule "OneCode Barcode Rule", we have created an updated version of this rule. See the attached .zip file to this post. To install, unzip the file and locate the .xml file. Next, navigate to the "\Plug-ins\TemplateXML" folder to see the other templated rules for FusionPro. Back up the existing file "OneCode Barcode.xml" to a safe place and then put this new "OneCode Barcode.xml" file in this folder. Restart Acrobat and see the new rule appear in the Text rules area. Opening this rule will show the new default tracking value of 5% as follows: http://forums.printable.com/picture.php?albumid=3&pictureid=20 OneCode Barcode.zip
  13. Thanks for the votes on this poll, everyone. Curious as to what type of solution you are using to send email. Are these in-house solutions where you have the software/hardware and perform the sends? Are they hosted solutions where you go to a site and send the email and that service sends them for you?
  14. Hi all, A recently added feature to FusionPro Server is the ability to generate JPEG output from a composition. For those FP Server customers looking to utilize this capability (for example, to make a JPG preview for a custom Web to Print system), here's the documentation on how this can be accomplished. At the end of the composition, a JPEG image of any page in the output PDF document can be created without having to invoke a separate conversion process. This feature is only available in batch FP Server compositions using the PDF output format. Note: In addition to this JPG output feature, FusionPro Server also ships with the PDF2IMG utility. PDF2IMG can be used to programatically create image file formats in BMP, EPS, GIF, JPG, PNG, or TIF. Unlike the native JPG output capability of FusionPro Server, PDF2IMG is called as a separate process after FusionPro Server has fully created a PDF output file. FusionPro Server customers can find the PDF2IMG utility in the PDF2IMG sub-folder in the FusionPro installation location (default is C:\Program Files\Printable\FusionPro\PDF2Image). Full documentation on PDF2IMG is also located in this location. There is a series of new CFG (job) file settings to enable native JPEG output from FP Server: JPEG_Output_Enabled=[true/false]. Enables JPEG output for the job (it must be using PDF output). Defaults to false. This must be set to true for any of the other settings to be interpreted. All other settings are optional. JPEG_Output_StartPage=[one-based page number]. Specifies the starting page of the output PDF to be output as JPEG. Defaults to 1 (one). (A value of 0 [zero] will also use page 1, but otherwise page numbers are one-based.) JPEG_Output_NumberOfPages=[number]. Specifies the total number of pages, starting at JPEG_Output_StartPage, to be output as JPEG. Defaults to 0 (zero), which specifies a single page with the specified file name (see JPEG_Output_BaseFileName). Any other non-zero value will cause output JPEG file names to include the page number. A positive number specifies the total number of pages, starting with JPEG_Output_StartPage, to be output as JPEG. A value of -1 (less than zero) will cause all pages in the output PDF, starting with JPEG_Output_StartPage, to be output as JPEG. JPEG_Output_Quality=[number]. Specifies the JPEG quality (compression) level to use, as a percentage. Valid range is 1 to 100. Defaults to 100 (percent). JPEG_Output_Resolution=[number]. Specifies the resolution of the JPEG, in DPI. Valid range is 36 to 1200. Defaults to 72. JPEG_Output_Scaling=[number]. Specifies the scaling factor to use when converting the PDF page(s) to JPEG, as a percentage. Valid range is 10 to 1600. Defaults to 100 (percent). May be superseded by JPEG_Output_MaxWidth or JPEG_Output_MaxHeight. JPEG_Output_MaxWidth=[number]. Specifies the maximum width of the output JPEG, in pixels. Defaults to 0 (zero) to use the original width of the PDF page. JPEG_Output_MaxHeight =[number]. Specified the maximum height (depth) of the output JPEG, in pixels. Defaults to 0 (zero) to use the original height of the PDF page. JPEG_Output_PDFBoundingBox=[string]. Specifies the PDF bounding box of the page(s) to be converted to JPEG. Valid values are "ArtBox", "BleedBox", "CropBox", "MediaBox", and "TrimBox". Defaults to "CropBox". JPEG_Output_BaseFileName=[string]. Specifies the base file name of the JPEG file to output. A fully-qualified path is recommended. If empty or not specified, the path and file name of the PDF output file with the extension changed to ".jpg" will be used. See JPEG_Output_NumberOfPages about page numbers being inserted into the file names for multiple JPEG files. Note on width and height specifications: If neither JPEG_Output_MaxWidth nor JPEG_Output_MaxHeight are specified, then the original PDF page size will be used, subject to the JPEG_Output_Resolution and JPEG_Output_Scaling factors. If both JPEG_Output_MaxWidth and JPEG_Output_MaxHeight are specified, the image will sized as "best fit" for the specified dimensions (sized to fit within both dimensions). If only one of the two is specified, then the output size is adjusted to match it. In all cases, the aspect ratio of the original PDF page is maintained. The simplest usage of this feature is to turn it on with this CFG file entry: JPEG_Output_Enabled=true This will output the Crop Box of the first page of the output PDF as a JPEG graphic, at 72 DPI, 100 percent scaling, and full quality. The JPEG file will be in the same location and have the same name as the output PDF, except that the file name extension will be changed to ".jpg". To output all pages of the PDF as JPEG, this line can be added: JPEG_Output_NumberOfPages=-1 This will append the page number to each JPEG output file, before the extension. For instance, if the PDF output file name is "report.pdf", then the JPEG files will be named "report-1.jpg", "report-2.jpg", etc. The JPEG output file names can be customized like so: JPEG_Output_BaseFileName=\\sharename\foldername\preview.jpg Note that a fully-qualified path is recommended. If JPEG_Output_NumberOfPages is not specified, this will be the exact path and file name of the JPEG file. If JPEG_Output_NumberOfPages is specified, then the page number will be appended to each JPEG file name, before the extension. In this example, the JPEG files will be named "\\sharename\foldername\preview-1.jpg", "\\sharename\foldername\preview.jpg-2", etc. Other options work in a similar fashion as in the Img2Img.exe utility.
  15. Hi all, In looking to further solidify client relationships, many traditional Print Service Providers have looked to expand their service offerings beyond print. With enterprise marketing folks looking to decrease costs, alternative channels to reach customers and prospects have seen some impressive growth in the past 12-24 months. A continued hot-growth area is the use of email marketing which, in many cases, is supplanting print campaigns due largely to the low cost of delivery. Printable has been following this trend closely and would like to see what plans our customers have regarding offering email marketing services to your clients. Please feel free to reply to this thread with your own thoughts and observations about email marketing, the shift of some away from print marketing towards email, and your plans regarding offering this to your customers.
×
×
  • Create New...