If there is anything in particular you would like me to test over the next X days until the trial version is released, let me know. The performance of the new JavaScript needs addressed and am quite confident that Quark will do so. So not needing to create text frames on every page may have something to do with the speed. However, the JS solution is also an "in-line" merge and it all flows into the same text box in ID. JS was about 1/2 the time for the JS merge. Using my "seat of the pants timer," the overall merge process in ID for in-built v. Unlike in Q, I didn't time the individual processing of a merge. In ID, using a JavaScript I have for the merge process took a mere 00:01:05 but the master page elements were already created. That included making a comparable master page. ID took 00.03:30 using its built-in merge facility. ![]() I also didn't try something like an envelope-size of document with just the addressee for the merge nor a sheet of labels with/without return address on it. I didn't give it a try without the master page background and what not but cannot imagine that has an effect other than when Q2018 gets to displaying pages. This feature can be useful when you want to create hundreds of. Could be my bit under-powered laptop and I didn't try on the better-speed of the desktop. You can merge various forms of data including CSV files or TXT files with InDesign documents. The 500 record merge I tested took enough time to make and eat a small lunch (about 45 minutes). Large merges (using the sample letter document) can take a performance hit. JoLetter looks interesting, but I'd rather not plunk down the money if Quark's solution works. Is the Java solution for QuarkXpress, in your opinion, enough for basic jobs? I presently don't really have need for anything beyond simple addressing, labels, etc. It will be used by me, just for other things. Run a script that does some minor changes and then automatically add bookmarks based on a paragraph. And likely I'll keep using it versus the as-shipped mail merge or redo what I would need from this particular sample JS. Data merge all labels like creating a merged document. ![]() Why? Because I need logic, conditional statements, etc. It needs redone.ĩ9% of all my merge jobs are done using Em Software's XTension. And the bugs that were first in it are still there.and one or two more. JoLetter takes this concept a few steps forward and is the bare minimum that ID should be up to after what, 16 years? Data merge hasn't improved one bit in ID since its inception. But really, if it isn't a simple job, who wants a bazillion text frames? Which is why if/when I use ID for merging, I use JavaScript to either do it all or use it to clean up after ID does its native merging. It's fine for mailing labels and a few other simple projects. Mail merge in ID is far too simplistic and is only half as powerful as that in Word. I don't it's a "set it and forget it" feature. Name each output file by column in merge data Each record saved to a unique location and/or file name Export JPG, PDF (. Personally I feel Quark had to begin somewhere.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |