StevieB

Hi All,
Well, it’s been a pretty crazy week since the launch of V2!
This has been a real labour of love for us over the last year or so, and I can’t even begin to describe how hard the development team have worked on it. Not only getting the V2 apps launched, but also of course finally bringing Publisher to iPad. 
With this being our first paid-for upgrade there has understandably been a lot of feedback / questions around future updates and our pricing policies. I thought it was worth addressing / clarifying our position on some of these personally...
Updates to V2 moving forward
Buying V2 not only gets you all the new features you have seen, but we have various updates planned – including many more new features and improvements – which you will get for free. This will continue until such a time that V3 is released. We’re not sure exactly when V3 will be, but I can confirm we are not going to move to anything as regular as an annual upgrade cycle as has been speculated.
It’s worth saying too that V2 does include many under-the-hood changes to our underlying technology, and we have also been investing in several new areas of research recently. Some of these haven’t manifested themselves into new features yet, but overall V2 does give us a better platform to develop on moving forward and I’m sure you will be pleased with the updates V2 will receive.
Updates to V1 moving forward
While we did say on the FAQ that V1 would no longer receive any updates, I want to clarify that was about new feature updates. We will be updating V1 to fix any critical problems caused by operating system updates in the future. So if the next version of macOS breaks V1 we will endeavour to fix it. There will be a point in time when continuing to maintain V1 in this way will not be tenable, but certainly for the foreseeable future we will continue to patch. In fact, we have an update to V1 queued up for release very shortly with some fixes for Ventura and issues caused by a recent Windows security / quality update. 
We will update our FAQ shortly to make that clearer for everyone.
Offer period
In case you didn’t see, I’m pleased to confirm we have decided to run this initial launch offer until 14th December to give everyone the best chance possible to get it if they wish / have a decent amount of time to trial it. 
Upgrade pricing
It’s been really hard to see some of the comments about us not looking after our existing customers – we’re pretty devasted that anyone feels like that to be honest. But the fact is we felt our hands were tied somewhat with being able to offer upgrade pricing in a fair way. The main reason for this was App Store customers (which make up around 35% of our userbase). The problems with that are two-fold: firstly, we didn’t have a way from within V1 to validate an App Store purchase receipt to reliably ensure customers who were entitled to an upgrade could get one; and secondly, we could not find a good way for people to get that discount via the App Store. Us pushing upgrade customers to go exclusively via our own site (including customers who were previously acquired via the app stores) may also have put us in violation of App Store Ts & Cs which we were obviously concerned about.
I’m not saying that these issues were completely insurmountable, but any solutions we came up with would be messy, and most importantly could have resulted in some bona fide V1 customers struggling to get validated and claim their discount. We certainly don’t have the support resource here if we ended up needing to manually validate tens of thousands of receipts for example.
The only option we felt was safe to move forward with was a general launch offer, which would guarantee that every V1 customer could get the discount, whether they purchased directly through us or the App Stores. We knew a side effect of that would mean some new customers would end up receiving that same discount – but we felt that was a better option than V1 customers missing out. It’s also worth saying that while there has been some good press about V2, all our main marketing has been via email and through social media to our followers. In other words, we felt ok about it because we knew the vast majority of people who would find out about it or take advantage of the offer would be existing customers. I would be surprised if over the offer period customers upgrading from V1 didn’t make up more than 90% of our sales.
Overall I do believe us giving a 40% discount, along with the addition of the new Universal Licence of course, is offering fantastic value for money for those who want to upgrade. 
However, taking on board some of the feedback there is something extra we can do – we will offer a new free bundle of content exclusively for V1 customers upgrading to V2 as an extra thank you for your support. I’ve seen this suggested by a number of customers and it’s a great idea as it does remove the App Store conflict entirely. 
We’ll need a little time to put something together, but all customers who previously registered or purchased V1 and have since upgraded to V2 will receive a voucher code for this via email as soon as we can.
A comment on no subscription
I do want to say that some of the points above are exactly the reason why software companies move to subscription. Whatever you do with upgrade pricing, you still have the issue of customers who bought the previous version 3 months ago vs. those who have had it 2+ years. Offering perpetual licences also gives the additional overhead of needing to maintain the previous version longer than you would if everyone was on subscription / generally always on the latest version.
We are a small team so some of these complications are not ideal — all we really want to do is focus on developing our latest codebase, push out regular updates and continue with our mission to make great creative software accessible to everyone. 
But it does need to be funded somehow. We know you love our no-subscription model, but there also needs to be a level of appreciation that the alternative is having paid-for upgrades from time to time. That unfortunately comes with its own problems.
All of that said, I have to say we have been blown away with the response to V2 - around 3 times as many people have upgraded in the last week than we expected - and we really can't thank you enough for the support you have shown. More than anything the success of this upgrade puts us in a great place to continue investing heavily in development which is ultimately what it's all about, and we’re super excited to crack on with some great updates coming next year!
All the best,
Ash
This is a duplicate post of a thread that is now locked and moved to the questions forum

That's because I forgot to press the upload button...sorry!

It is a must for .eps files with Spot colours to import those colours to the document, and not change them to CMYK breakdown.
If you work with clients that have all their assets (logos etc) in Illustrator eps format, then it is a must that the colours that are defined in those files, be they spot or global, get transferred to the Publisher document. Then if you need to output the file with the spot colours they should then separate to their own plate for printing.
Sadly Affinity Designer also doesn't honour imported eps files with spot colours, so it seems an Application wide problem.
I'm keeping my fingers crossed that this will be implemented soon.

It's the new "Infinity Publisher."
(And now I better go hide.)

I remember the first betas had this problem. It’s not a deal breaker but not ideal!
The IDML import is great, I’ll soon be able to ditch adobe!
Regards, Steve 

Hi Jon,
Here it is...
It was created with the latest version of InDesign.
Hope it helps.
Steve.
BRC Legacy PREMIUM 2020 calendar.idml

Yes please!
I use the slug area all the time in InDesign to add notes on which version a lasered letter it is, especially as some clients insist on one file with all the letter versions in them.
A note in the slug area is easy to see which version is which.
See these slug area screenshots from a recent job...
 

Well I got my maths wrong, it's a week until my birthday so I got confused... the launch is two weeks and a bit...
Sorry, Patrick, for the confusion. (I'm easily confused!)

The Site's back up now.
Publisher pre-ordered!  
Only two weeks and a bit to go...

Well I got my maths wrong, it's a week until my birthday so I got confused... the launch is two weeks and a bit...
Sorry, Patrick, for the confusion. (I'm easily confused!)

In InDesign the swatches palette has the 4 process colours, Cyan, Magenta, Yellow and Black predefined as well as White (paper), Registration and None. The Black, Registration and None cannot be redefined. There are a couple of other colours there as well, Red Green and Blue, but they're also defined as cmyk.
It would be good if the colours dropdown has these colours defined in cmyk and not HLS. 

You can set up the document to have the process colours, but it would be nice to have this as a default.

It just seems odd to have a print document with HLS colours defined as you would only use cmyk or the pantone equivalents.
Hope that helps...

I think you misunderstand what Serif are doing, namely making a professional publishing program designed from the ground up.
It is totally unrealistic to expect the new program to be a clone of the old Page Plus software as it has been developed as a suite of 3 programs that all have a common core code.
The old 'legacy' software has a code base that was written (probably) in a 32bit environment, which has its limitations, namely that Apple are dropping the ability to run older 32bit software in its next release of Mac OS. See this link: https://support.apple.com/en-gb/HT208436 (I know that the Page Plus is Windows only)
To expect a new program to have all the features of the older version, which has had many years of development, is unrealistic, especially as Publisher is aimed at the professional designer who doesn't want to be tied to the Adobe Subscription model.
It is admirable that Serif has taken on this challenge and Publisher is the last piece of the jigsaw.
Just cut Serif some slack! They're doing an admirable job and have achieved a suite of design, illustration and image apps that can be used to produce professional results.
Publisher is still in the testing phase and should not really be used for mission critical work.
 
 

I think you misunderstand what Serif are doing, namely making a professional publishing program designed from the ground up.
It is totally unrealistic to expect the new program to be a clone of the old Page Plus software as it has been developed as a suite of 3 programs that all have a common core code.
The old 'legacy' software has a code base that was written (probably) in a 32bit environment, which has its limitations, namely that Apple are dropping the ability to run older 32bit software in its next release of Mac OS. See this link: https://support.apple.com/en-gb/HT208436 (I know that the Page Plus is Windows only)
To expect a new program to have all the features of the older version, which has had many years of development, is unrealistic, especially as Publisher is aimed at the professional designer who doesn't want to be tied to the Adobe Subscription model.
It is admirable that Serif has taken on this challenge and Publisher is the last piece of the jigsaw.
Just cut Serif some slack! They're doing an admirable job and have achieved a suite of design, illustration and image apps that can be used to produce professional results.
Publisher is still in the testing phase and should not really be used for mission critical work.
 
 

I think you misunderstand what Serif are doing, namely making a professional publishing program designed from the ground up.
It is totally unrealistic to expect the new program to be a clone of the old Page Plus software as it has been developed as a suite of 3 programs that all have a common core code.
The old 'legacy' software has a code base that was written (probably) in a 32bit environment, which has its limitations, namely that Apple are dropping the ability to run older 32bit software in its next release of Mac OS. See this link: https://support.apple.com/en-gb/HT208436 (I know that the Page Plus is Windows only)
To expect a new program to have all the features of the older version, which has had many years of development, is unrealistic, especially as Publisher is aimed at the professional designer who doesn't want to be tied to the Adobe Subscription model.
It is admirable that Serif has taken on this challenge and Publisher is the last piece of the jigsaw.
Just cut Serif some slack! They're doing an admirable job and have achieved a suite of design, illustration and image apps that can be used to produce professional results.
Publisher is still in the testing phase and should not really be used for mission critical work.
 
 

Here's what you need to do...
Draw your equilateral triangle.
On top of it draw rectangle that covers the area from the top of the triangle to beyond the right hand point.
Select both objects and go to the menu Layer > Geometry > Intersect.
The shape that is left is half of the equilateral triangle.
Make sure that you have snapping on, this will help you line up the shapes.
See the attached screen shots...
Hope that helps!

Thanks for clearing that up!
Could be useful when you want to extend the document size, at least you know the extended bit will have a transparent background.
Just did this test to extend the document area by 500px to the left: see screenshots.
1- Added a vertical guide at -500px
2- Crop to that guide
3- Guide now at 0px, document 6500px wide.
Works well, but you have to add the guides by using the Guide Manager.
The crop too does snap to the document bounds so you shouldn't lose where the document bounds are, but you have to have snapping enabled!

I thing some people are missing the point of the bleed area, namely this is the area that gets trimmed off when the page is guillotined.
It allows for movement of the stack of paper in the guillotine. The bleed area is where items on the page, like a background colour that goes all the way to the edge of the page is allowed to bleed off the page area into the bleed. The crop/trim marks are placed at the edge of the page and the bleed is the part that extends past the crop marks and gets trimmed off. This prevents any white space appearing if the trimming of the paper is slightly off.
Simple really!

Hi Chris26,
Here is an AfPub document set to 190mm x 277mm plus bleed, 10mm gap all the way round.
If you print that out you might find that the printer margins are such that it won't print right to the edge.
Have a try...
Page 190mm x 277mm to print on A4.pdf
Page 190mm x 277mm to print on A4.afpub

Here is an AfPub document with a page size of 180mm x 270mm. This will print on a A4 sheet with crop marks.
There are 3 rectangles:
Bleed 3mm: Outermost with red border
Page size 180mm x 270mm: Middle with green border
Margin 4.6mm all round: centre one with cyan border
Just as an example of how it looks and how to set it up.
Also enclosed is a pdf of the output.
Hope this helps to clear things up.
 
 
Page to print on A4.afpub
Page to print on A4.pdf

Will the ability to change an existing colour from spot to global/cmyk and vice versa be added in a future update?
This does seem a restriction, as it stands at the moment.
Coming from InDesign it is easy to change the colours between Spot/cmyk, very useful if someone has added lots of spot colours to a job whilst they are designing it, and you need to change those to cmyk to stop them from outputting to separate plates.
Will the ability to show the overprint in Publisher be added at some stage?

Will the ability to change an existing colour from spot to global/cmyk and vice versa be added in a future update?
This does seem a restriction, as it stands at the moment.
Coming from InDesign it is easy to change the colours between Spot/cmyk, very useful if someone has added lots of spot colours to a job whilst they are designing it, and you need to change those to cmyk to stop them from outputting to separate plates.
Will the ability to show the overprint in Publisher be added at some stage?

Aha! 
Yes that would be it...
Thanks, couldn't see that option for looking!
There's so many options in the preferences that it's easy to miss the one you want to change.

If it's not possible for the user to select the Bleed colour now could you please change it to something that contrasts with the grey background as it is difficult to see if you have a light mid-grey background!
See attached screenshot.
 

I know the frame tool is not working as it should, here are some observations.
Say, for instance, you have an eps logo that's on the large size for what you want and you resize it in the picture frame to get it to the size you want, if you then resize the picture frame, the logo immediately changes size, even if you lock the child logo layer. 
In the Properties tab it would be nice to have the option not to have the image anchored to a corner or side, sometimes you want to have the image floating in the frame while you resize it, especially as the image may be rather too large, this can happen when you're designing a layout, as sometimes the assets you have have not been cropped or you're working with low-res photolibrary images before they've been approved and purchased!