• Content count

  • Joined

  • Last visited

About MikeW

  • Rank
    Idiot in Training

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

582 profile views
  1. AD cannot do a data merge. Affinity Publisher, for which it may make more sense for a data merge, will also not have the capability for data merging for some time after its release...whenever that may be.
  2. Dunno which application the request is for...But the current AD has this in the Text menu. At least using the Windows version:
  3. I often use pdfToolbox to convert type to curves. I find I need to do this often with ad submissions, especially with InDdesign's PDFs. Sometimes I do rip to an image format (also using pdfToolbox or Acrobat) just so any transparency issues are avoided. But other than that, there is little reason for me to open for editing a PDF. If I need to modify a PDF, I'll often use either XDP or CD. Both of which deal with PDFs and embedded fonts well. XDP will generally just use the embedded subset, CD gives a choice of live type of convert to curves. CD uses Ghostscript in the background to do this, which would be a good option for Serif. But once pdfToolbox converts the type to curves, it can be opened just fine in anything that can import a PDF, including AD or APhoto. Mike
  4. I was using Adobe as a for instance, not as a role model. I will agree re third-party applications in so far as they help production. APhoto, of course, can use .8bf Photoshop filters, but that is still short of specific plug-ins and other models that PS does support. AD, of course, really should get third-party support plug-in and scripting. Serif will never be able to do everything, which is why third-party developers exist in other eco-systems. This all would apply to APub, too. However, none of that is to say that what is important as regards playing nice with other applications is top-quality export. I can accept that Serif seemingly wants a closed system incapable of third-party support. I don't agree with that sentiment. But it isn't my playground and I don't make the rules. So as long as I can create assets for use in other applications, I can/will use Serif applications' export capabilities. I see that as no different than I currently do. So regardless of Serif's ultimate decision regarding third-party developers, I will use AD when it makes sense to. I'll use another application if AD doesn't make sense. And like I do with XDP, CD,AI, etc., I sometimes take things X far along in the design and port it into something else to finish it off. The same will apply to APub for years to come. I have no idea what capabilities APub will have out of the gate, but I seriously doubt it will be of use to me for all but a small portion of the types of things I do in a layout application.
  5. AI's format is largely unexposed as well. Some applications like CD, and for older AI files, XDP, works fine. But it is still a closed file format and there can/will be some gotchas. As is ID's native file format and if IDML wasn't a viable alternative, no one would be able to transport them to say QXP or Viva Designer. And one needs, in the of QXP, to purchase an Xtension to do so. Viva's IDML import is fairly OK, but that application cannot handle large documents well and is certainly missing things for my work. The same does/will apply to Serif's applications: Export to a format as the final use PDF or another format for use in other applications. What is any different than Adobe?
  6. I don't think it is the file format per se that is holding up APub. I think it is programming hours. Serif has long been looking for good programmers who both can do the work and would be a good fit.
  7. Great. It can be a pita to work in one application but need to turn over in another format and use a PDF to interchange between the applications. It can be done, as you see, but there are often things that need fixed/changed once the next application opens that PDF. Some of those issues can be mitigated by using discrete layers, removing any effects in say AD and adding them in CD, etc. Mike
  8. No. One can make a text frame be a shape that would have a "cut-out" portion. But it would need updated anytime the image size is made smaller/larger or the "wrap" distance needed changing. Mike
  9. Using the More button, uncheck the Use Advanced Features checkbox that is located clear at the bottom of the dialog box one gets when clicking the More button. You will need to scroll down all the way. And if you also have CD, I would recommend using the PDF for Export type. This has the Use Advanced Features already turned off.
  10. And by "print," is it a PDF you are needing to use? If so, what type of PDF does the print establishment want? So if the print establishment wants a PDF/X-1a file type, then exporting to that type will convert your RGB colors to CMYK according to the document CMYK profile or to a different CMYK profile as found using the More button. Mike
  11. Exporting to a given file type that supports it and choosing to use CMYK should do it. For instance, choosing a PDF profile that uses CMYK as the color type will convert all RGB to CMYK according to the output profile. What is it you are wanting to do/accomplish? Mike
  12. The compatibility between Adobe applications and the Serif applications use two differing definitions of the word compatibility. With Serif applications is is complete file compatibility in all that means. Serif applications can open for editing each others files. That will extend to APub. Adobe applications, and to limit the scope to the pertinent application, InDesign, is limited to placing files of mainly two of Adobe's other applications, PSD and AI files. But it isn't truly compatibility the way it is defined for Serif applications. It is the mere placing of those file types. That placement of those two file types is also not directly comparable between them. PSD support in ID is pretty good as regards turning certain layers off/on, but that is it. With AI, the only portion of the AI file that can even be imported is the PDF portion and one cannot do anything in ID with it, really. Mike
  13. I downloaded the first one listed. It is a tiny file. Yep, AD does a couple things it likely shouldn't do. It either reads the page size incorrectly, hence the page showing at the top and the right. AD also rasterizes the area around the logo and so once removed, there is missing vector stuff. But that is because an EPS file cannot have transparency and there is a circle making up part of the logo at the bottom right that uses transparency and so AD is making a bitmap out of it and every vector "grain" of wood it touches. The white background is simply the page--it isn't an artboard that can optionally be shown with a checkboard to indicate transparency. The file is of a small physical size because someone took a photograph of wood and auto-traced it. Which results in a bazillion pieces and a resulting a gazillion nodes. They kept it small in order to manage this. Opening that file in AI and resaving as an AI with PDF copy (the default in AI) fixes these issues. The page size is described correctly, the logo with transparency comes in on its own layer and maintains the circle part of the logo with the correct opacity and as vector objects. Oh, and the AI version is 1/3 the size. If you have the option of a PDF, that may have been correctly made and would then bypass the listed issues. If there is an AI version and they saved it with the PDF copy (again, the default setting) it may come in correctly. But AD needs AI files saved with this option because that is actually what AD is opening, the PDF portion of an AI file. I imagine the second file is similar. But I didn't download it. I have used some wood plank photos in my work in the past. I have always gone for the largest size of the image formats. Such a thing when made as vector is rarely needed, even for the large format work I do. As vector, dealing with the slowness just has never been worth it to me. And there are large bitmap images of such a thing freely found on the Internet. Mike
  14. Sean, Futura T Bold is inside of that TTC font. There are 5 instances (different weights and style) in that font and Bold is one of them. Even though this has been resolved by using a modern version (the OTF), should the Affinity products work with a TTC (TrueType Collection) font or not? That's the question. I do believe windows does (or until Win 10) shipped with TTC fonts. Mike
  15. Likely other applications will work, too. I believe Windows still ships with TTC files. While I have not read widely here on the forum, I cannot recall anyone bringing up TTCs not working. So like I wrote, Serif needs to look at this. I would encourage you to make a new post in the Bug section for your OS, provide the APhoto file, the bad PDF and the font. It will be more assured of being picked up as a bug. Mike