Dan Korn

I wouldn't really call that a chart. Those are used to compare multiple values (bars), usually with labels on the X and Y axes denoting what the values mean. Instead of trying to make a chart, I would just resize a graphic frame. Attached is an example that does that. PercentageGraphic.zip

I tried the job and it looks like the curved text is working. Please be more specific. What exactly doesn't work? Do you get an error? Is any output generated at all? If so, how is it different than what you expect? Also, is the output different when composed locally in Acrobat vs. when uploaded and composed in MDSF?

The way to do this is to make a series of empty frames, approximating the shape of the graphic, for the text to wrap around.

I would put the calculation into a function, call it for all 21 locations, and save the results into an array, where each item has the distance and the location. Then sort the array, and just grab the first two items (the lowest values) and insert their addresses. Presuming that the list of these 21 locations is in a secondary data file (XDF), it would look something like this: function DistanceBetween(lat1, lon1, lat2, lon2) { // Modified from: http://www.codecodex.com/wiki/Calculate_distance_between_two_points_on_a_globe#JavaScript // Calculate distance between latitude/longitude points: http://www.movable-type.co.uk/scripts/latlong.html // Radius of the earth: http://en.wikipedia.org/wiki/Earth_radius // Rounding in JavaScript: http://www.javascripter.net/faq/rounding.htm var R = 3959; // Convienient mean radius of the earth in miles. Change to 6371 for kilometers. var dLat = (lat2-lat1)*Math.PI/180; var dLon = (lon2-lon1)*Math.PI/180; var a = Math.sin(dLat/2) * Math.sin(dLat/2) + Math.cos(lat1*Math.PI/180) * Math.cos(lat2*Math.PI/180) * Math.sin(dLon/2) * Math.sin(dLon/2); var c = 2 * Math.asin(Math.sqrt(a)); var d = R * c; // The distance is d. //return Math.round(d*10)/10 + ' Miles'; // Rounds the distance to tenths of a mile. return d; } var distances = []; var recipientLatitude = StringToNumber(Field("Latitude")); // Variable Latitude (Mail Recipient Location) var recipientLongitude = StringToNumber(Field("Longitude")); // Variable Longitude (Mail Recipient Location) var Locations = new ExternalDataFileEx("Locations.txt"); for (var l = 1; l <= Locations.recordCount; l++) { var lat = StringToNumber(Locations.GetFieldValue(l, "Latitude")); var lon = StringToNumber(Locations.GetFieldValue(l, "Longitude")); var distance = DistanceBetween(recipientLatitude, recipientLongitude, lat, lon); distances.push([distance, l]); } distances.sort(function(a, b) { return a[0] - b[0] }); var l1 = distances[0][1]; var l2 = distances[1][1]; var result1 = Locations.GetFieldValue(l1, "Name")) + "<br>" + Locations.GetFieldValue(l1, "Address")); var result2 = Locations.GetFieldValue(l2, "Name")) + "<br>" + Locations.GetFieldValue(l2, "Address")); return "Two closest locations are:<br><br>" + result1 + "<br><br>" + result2; Note that this code was typed "in the blind" and is completely untested.

Thanks for the feedback. After investigation in conjunction with our barcode vendor, we have determined that the updated QR barcode generation algorithm in FP 13.2.5 is sometimes outputting "mirrored" QR barcodes. These seem to scan correctly with most devices and app, including most Android and iPhone apps. However, the mirroring is non-standard and is not supported by many dedicated scanning devices in the field. We have obtained an updated algorithm that does not do the mirroring, which we will be including in a future release. Sorry for the trouble.

By design, inline graphics are set along the baseline of the text, i.e. where the bottoms of the letters go, excluding descenders in lower-case letters like g and p. I would try using superscript and subscript to achieve the effect you want. You can adjust the superscript and subscript offsets in the Paragraph Globals dialog, or with markup tags.

MarcomCentral® is proud to announce version 13.2 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 for Adobe InDesign 2025 (version 20) on both Mac and Windows. Support for OS Version 15, Sequoia. Improves accessibility support in the following ways: Corrects issue where OBJR tag for hyperlinks for variable text in accessible PDF documents is sometimes missing. Adds ID attribute to link tag. Improve wrapping text around picture in non-Legacy leading mode. (Case FP-720). Support for XDF files where data is in more columns than there is data in the first row. (Case FP-730). Support .xlsm extensions for Excel files as data or XDF data files. Support is added for minimal XML log containing only user metadata and record boundaries. Fixed crash on Macintosh when the compare documents feature in Acrobat is activated with the Acrobat plug-in installed. Fix PostScript-based output formats on new Macintosh models. Output fixes include PostScript, PPML, and VPS. FusionPro VDP 13.2 has passed testing on Windows 11, Windows Server 2022, macOS 13 (Ventura), macOS 14 (Sonoma), and macOS 15 (Sequoia). Testing is ongoing with Windows Server 2025. 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.2 release, feature set, and addressed issues can be found in the FusionPro VDP 13.2.5 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.2 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.2 Templates Templates from FusionPro VDP through version 13.2.5 are currently supported in the MarcomPortal application.`

Well, that data certainly could be used to generate a GS1-128 barcode. Or it could be used to generate a different barcode format. It's hard to know what the customer's requirements are without more information. I would start by creating the Linear Barcode rule with the GS1-128 format and that data field.

Hmm, I'm not seeing this at all with 13.1. I can type any number, without the degree symbol, and hit Return, and the value is applied. Can you use the little spin control arrows to the left of the edit box to change the angle?

Can you provide more information? How exactly are you trying to create the barcode, and what specifically is going wrong? Maybe post a sample job that demonstrates the problem?

It doesn't accept the rotation value if you type it into the box and hit Return?

Sorry about that. We are looking into emitting the graphic barcodes with spot colors. (It's a bit tricky because we have to make sure we're not re-defining existing spot colors, which can be a problem if you're using the barcode in thousands of output records.) If you use a text-based barcode instead of graphic, that will be emitted properly if a spot color is selected.

We have tested FusionPro VDP 13.1.11 with macOS 15 Sequoia and determined that it is compatible. We have not explicitly tested 13.0.4, but I expect that it should work in Sequoia.

There are logs generated by the Web Service. These are configured in the FusionProQueue.exe.Config file, located in the same folder as the FusionProQueue.exe executable. The log files are written to the same folder by default. (You can find the folder by opening the Service properties.) The logging settings are in the <log4net> section. Log4Net configuration can be complex; there's some doc here: https://logging.apache.org/log4net/release/manual/configuration.html But your best bet would be to contact FusionProSupport@marcom.com and ask to set up a call to go over this. Regarding your question about versions, there are several different tiers in this system, which all may have different versions from each other: The version of the main Scheduler Web Service itself, the FusionProQueue.exe executable which shows up as "FusionPro Server" in the list of Windows Services. The version of any Target Web Services on your composition machines in a multi-tier setup (the same service on those separate Target machines). The version of the FusionPro.exe composition engine on your Scheduler machine, or on any multi-tier Target composition machines. (This will be the same as the version of the Acrobat plug-in on any Target which also has that installed.) The version of the Dashboard GUI app which is connecting to the Scheduler. The "About" box for the Dashboard is indeed the version of the client Dashboard GUI app, which can be different from both the version of the Web Service API it's connecting to (the Scheduler), and the version(s) of the actual FusionPro.exe composition engine installed on your Target composition machines. If you go into the Activity Monitor tab of the Dashboard, it will show you the version of the Web Service on each Target, though the version of the composition engine on any Target may be different. (A newer version of the Web Service reports both its own version and the version of the composition engine.)

Yes, you can leave out the lindent="1200" attribute if you set the left indent here: