Raphie reacted to Steve Rawson in Fillable Forms
My feature request is for Affinity Publisher to have the ability to create form fields to be filled in ... in order to create fillable form PDF to be filled and edited in other software programs if needed. I would love to do this in order to make my patients process of filling our paper forms easier, for example to be done on an iPad.
Raphie reacted to rui_mac in [ADe] Select same color / fill / stroke / appearance
This was asked before.
I include a screen capture of all the options available in the Find & Replace and Select dialog from FreeHand.
It was great to have something like this :-)
Raphie reacted to Matthias in [ADe] Select same color / fill / stroke / appearance
Can be a great timesaver when you open documents from someone else or from CAD applications. Change any attribute a thousand times at once with only a few clicks.
Raphie got a reaction from wmcl in Is it possible to package a project in Publisher?
This is really a bad solution, a proper packager should be in place, especially if Affinity Publisher still need to maintain the images embedded to preview, even if it says they are linked. And as you point out this works with a fairly large file, almost a Gigabyte. But I wonder how this going to behave with even larger files. Photoshop itself won't handle properly over 5 Gb, I always test to see how far I can go with a software since the computer is more than capable that kind of file size in memory. The funny thing is that even Microsoft Publisher, the most basic publication application has this feature.
Not to have a proper packager is a huge mistake, the reason you create publications is mostly to send to print, most digital printers are OK with a PDF file but most reputable printers prefer to have the original file. They are dealing with thousands of prints per day and their schedule is tight as Air Control on an Airport, a small delay because of an error on a PDF can cost millions of dollars in delays, with the original file they can make adjustments on the fly.
And I don't know if any young freelance know this, fonts are software and many printers do not have the time to update their font catalog, because they probably have the font in the system doesn't mean is the same font, and what they look in the screen is nothing close to what you see in your screen. And the PDF will used the font installed in the system is currently open, fonts are not saved with the document. Try to print a PDF file from the web that uses licensed fonts and you will see what I mean by this. Of course, this is only one variable from the many could go wrong when moving a design to another computer on an alien network.
And this is very true, if you have been in the business for as long idyguy, I'm almost getting there, not any reputable firm will take seriously Affinity Publisher without this feature. This should be your higher priority. Right now I have to have a meeting and back up everything I suggested to my agency of considering Affinity Publisher as a replacement for InDesign, it is that serious.
Raphie reacted to yinYangMountain in Is it possible to package a project in Publisher?
Future? Not bad? That’s outrageous and absolutely unacceptable! Here’s why:
I’ve been working with QuarkXPress since the 90s and InDesign since the 2000s. I was completely surprised when I noticed a Package / Collect for Output feature was missing. So I made a call to a project manager working with various commercial publishers and with contracts at CocaCola, HP, Cannon, Honda, Hallmark, etc.
The basic response was:, “What! There is no way that output process will work or be taken seriously by anyone in ‘The Industry.’”
So Chris, I’d respectfully suggest that instead of moving this to a feature request and thinking about it as something for a future update, Serif get on this immediately and have it working prior to the first release.
And while I understand there is little chance Serif will take my advice, I’ll predict this is one of the biggest blunders ever. Whoever vetoed the Package / Collect for Output feature has little understanding of the final output process of professionals and commercial print houses.
- - - - - - - - - -
AFFINITY PUBLISHER (BETA) 188.8.131.52
- macOS: 10.13.6
- MacBook Pro (Retina, 13-inch, Early 2015)
- Processor 3.1 GHz Intel Core i7
- Memory 16 GB 1867 MHz DDR3
- Graphics Intel Iris Graphics 6100 1536 MB
Raphie reacted to Tom Schülke in Is it possible to package a project in Publisher?
The Big advantage of Packaging is, that you
can find all used Content, wherever it is on your Network, and the Packagingprocess sorts out all unessesair Content that you have put to your Contentfolder but didn´t use in your final layout.. When you Package a Dokument and send it to a partner ore collegue using also afinnity publisher, either way, you need to send many data to him.. from filesize there wouldn´t be a big differenze if you put the used content to a folder or if you embed the content to your afpublisher Document.
So i would suggest to embedd all the used contend to your document and send it this way.. But i would suggest a further Feature here !!!
using the embedded objects in the Ressource Manager.. give us the option to Export the embedded Content to a Folder we point to !
This of course wouldnt work when exporting to idml format which also is essential for many companys that work together with external partners.. My Architecural Company does this all the time .. sharing indesign documents or idml formats with for example the greenplaners.. So i assure you we need this workflow..
I dont know how afpubisher would handle the export of idml files and the packaging of content when it will support idml.. i hope they find a good solution for this..
Raphie reacted to Helen Anderson in 3 Page spread
Hi the multi page spread would be such an asset!!! I am designing a book cover and just gone back to Indesign due to not being able to layout a multi page spread with all relevant crop marks - spine included....
What a shame really like Affinity!! Hope you add this feature down the line - would make designers very happy!!!
Raphie reacted to walt.farrell in too easely broken path to linked resources
If you can make sure that the path name to the images out in your network is the same for everyone using a .afpub file, I think you'll be OK. But that will mean that you all need to use the server name, or all use the server IP address. You can't have some users referring to the server by IP address and some referring to it by name. Logically, it would be better to use the server name, as that is less likely to change (in my experience).
Raphie reacted to garrettm30 in Text Variables
Sure, no problem. For a simple example, consider a basic book with named chapters. You probably would assign the title with a particular paragraph style, which perhaps you have named "ch_title." Next, you can assign a variable that is linked to ch_title. In InDesign, there are a couple of choices, such as "First use on a page," which will grab the text from the first time that paragraph style is used in a page. Next, you can then create your header on a master page, and in the header, you place your variable. Now you have running headers, so that on the top of every page, you have the name of the current chapter. The value of the variable will stay the same until the next time it comes across the same paragraph style. If you have to edit the text of the chapter title, the running header will pick it up.
You can also think of it in terms of a similar but more limited functionality within Publisher as it is now. To use the same scenario above, you could instead divided your pages into sections in the Pages Studio and name each section to match the corresponding chapter title. Then you can use the <section_name> field in the header, and it will work basically the same. There are two disadvantages with that for a simple book: 1) You must make the section name match the chapter title, and make sure if you edit the chapter title, you also edit the section name, and 2) If the page count or order gets changed, you must make sure the sections still line up with the chapter. However, with a little vigilance, it is not a bad solution for Publisher's first version.
To give you an example that is too complex for Publisher, here are three pages from a layout of the French Bible that I have been working on lately in InDesign.
If you look at the top left of page 322 and the top right at 323, you will see running headers that show the first and last full verses on the spread. That is a combination of a couple of variables: first, it is defined from a character style on the book heading "2 Samuel," and secondly, each verse has a hidden verse reference (for example 1.22) that is tagged with the character style chap-verse-hidden. Then on the left page there is a variable defined to the first use of chap-verse-hidden on the page, and on the right we have another variable that is defined as the last use of chap-verse-hidden on the page. In that way, we have a faithful set of running headers throughout the text.
Similar would be a dictionary, where in the headers you have the first and last entry. If each entry is styled with a character style, then variables makes it simple to make running headers such that no matter the text flow, the first and last entry in a spread is automatically put in the headers.
Raphie reacted to Martien in Text Variables
Wish: support for Text Variables. Very handy e.g. to define revision numbers and other stuff and inject document metadata (date printed, modified, created, etc.) at appropriate places. Makes the document more evolvable (maintainable).
Wish++: share Tet Variables across documents (Designer, Publisher, Photo).
Raphie got a reaction from Alfred in Price for Publisher
I didn't knew that, thanks for the clarification. I was just repeating what the warning that prompt when opening one of those files, currently is still true... in semantics... because I can open them and save them as Publisher files and I still be able to reopen the original file on the original App.