Petar Petrenko

If you don't like it, please use Quark instead.
Also, you may login to Adobe's forum and say to them: "I'm not going to use your apps because they don't have Affinity suite export/import files".

If you don't like it, please use Quark instead.
Also, you may login to Adobe's forum and say to them: "I'm not going to use your apps because they don't have Affinity suite export/import files".

If you don't like it, please use Quark instead.
Also, you may login to Adobe's forum and say to them: "I'm not going to use your apps because they don't have Affinity suite export/import files".

Second case:
he maybe owns both programs, but doesn't know how to use them because he is a newbie.

Because I don't have Affinity Photo ... 

If he had his applications listed on the profile, it would be clear, and we did not ask :-)

Second case:
he maybe owns both programs, but doesn't know how to use them because he is a newbie.

Yes, we all know that.
But it does not answer the question, why it does not do it in APhoto, which is more suitable for raster image processing.

Just use the "Crop" tool in Designer.

Hi all
This has been the week of figuring out how to get my colours sorted in Affinity Photo. There is no direct support for the ColorChecker Passport from X-Rite in Affinity Photo unfortunately but I did figure out how to do it with some help. If you use X-Right ColorChecker Passport these are the steps on how to do it. This might be painfully obvious to some people but for me it was all entirely new and took a while to get my head around so I hope that this is some use to people.
1. When you are shooting your photos in a location take a photo of the ColorChecker Passports colour cards and the white card. Make sure they are in the same place as your subject matter and are properly exposed.
2. Import all the photos from your session along with your pictures of the ColorChecker.
3. Open your photos of the ColorChecker in Affinity Photo crop them down if you like and export them as 16 bit Tiff files. 8 bit might work but I have been going with 16
4. Open ColorChecker Tiff photos with the new beta version of ColorChecker Passport  Camera Calibration software in the ICC tab.
5. Export your ICC profiles naming them something so you know what photo shoot they go along with. 
6. Close down Affinity Photo and then re-open it to refresh the ICC database
7. Open your photos from the associated photo shoot and go to the Document tab and select Assign ICC Profile and select the ICC file you just created. And if all goes well your colour is mostly corrected.
8. Now to set the white balances correctly. Go to White Balance in the Adjustment section. Click the Picker button and then click on the photo that you took during the photo shoot of your white card. This will then automatically make the adjustment.
 
I hope that helps some folks. I did not understand any of this stuff three days ago and it was no fun trying to get my head around it for the first time. If anyone has tips on how to improve upon this workflow please share. I am by no means an expert on this subject. 
All the best!
 

If you want to create your own ‘faux’ bold, select the text and apply a thin stroke to it. This tends to yield a particularly poor result with serif fonts because the serifs become disproportionately thick, and whatever the font you will probably have to increase the tracking.

Just use the "Crop" tool in Designer.

They, Serif, likely will never open INDD files directly. It would be a moving target as Adobe changes the file specs often.
Serif might be able to create a routine that can go a long way around the INDD issue. But I doubt it would be worth the hassle. Best to plan on a script or plug-in that can open ID files and create a package with them which can also create the IDML automatically. There are free scripts (I've posted one such link) that can simply walk through a folder structure. Set it to work over a weekend or two.
Mike

HI Petar
Thanks for raising this it is a known issue so hopefully the team will be able to look at sorting this
Thanks

I see but it is more comfortable to have it always up. thank you for the tip!

I want a single app with all Personas (based on the license), too. 

I really hope that this is extended across the range so that all combinations are supported, rather than only supporting Designer and Photo inside Publisher.

Yes, it would be nice to have all personas on in this one app according to purchased licenses.
Even now, both applications can do everything - AP can draw vectors from AD, AD can apply AP filters. Only can not edit it and enter, pity.
 

If you could just integrate these two programs into one seamless app then you would have a perfect replacement for Adobe Fireworks. I'm not a fan of switching from one to the other

Who said so?

Found it.
Right-click on the master layer in the Layers studio and there is now a set of four options in the context menu, one of which can be active at a time:
Edit Detached - this does what you are asking for.  It allows you to select items from the Master and move them around, keeping the changes independent for that page. Edit Linked - this allows you to select items from the Master and move them around, but changes are propagaed back to the Master and other pages that were not modified by editing detached Edit Frame Content - this is the new default behavior, in which you can enter text and the like but the positions of Master page items are locked down Lock - this one prevents you from even editing text in Master page items.   
So it looks like they already did this - you just need to tell it what mode you want to be in.

Hi,
my workflow for magazines is to keep all text on one page into one text box (if possible), but it does not allow me to use Layer effects within paragraph and character styles (like outer shadow on Headings). So, I am asking you to include Layer effects into text styles and make Publisher even more flexible than Quark and ID.

Petar is talking about the new functionality in 1.7.0.221, I believe, which is intended to replace that old workaround.

Status: Public Beta
Purpose: Stability and General Testing
Requirements: 64 Bit Win 7 SP1 / Win 8 / Win 10 
Hi,
We are pleased to announce Affinity Publisher build 221 is now available as a manual download from the link above. We hope to put it on auto-update early next week.
As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity where you may be adversely affected by the application failing, including the total loss of any documents. 
We hope you enjoy the product, and as always, if you've got any problems installing or running up, please don't hesitate to post in this thread.
Any problems actually using this version please make a new topic in this forum and we'll get back to you as soon as we can. Please feel free to leave general suggestions and comments in the Discussion Forum. 
Many thanks for your continued feedback.
---
Updates and Fixes
Master Pages
Due to the changes in Master Page functionality in this build we strongly suggest you backup any documents that are valuable to you before testing.
It is now possible to edit the content of Master Page Text Frames and Picture Frames directly from a spread the master is applied to. By default, on editing, the content attribute for the item in question is automatically unlinked, but the other attributes and geometry remain locked. It is also possible to entirely lock the Master Page instance if desired, to prevent unintended content edits. Finally options are available to edit all attributes of Master Page items linked - the Master Page and any other pages it is applied to will be updated - or to edit all attributes unlinked - only the copy on the current spread will be updated. In both of these cases an information bar is displayed while the editing ‘mode’ is active.
Text flow between frames on masters is honoured when the master is applied and it is possible to create text flow between frames that have come from masters. When auto-flowing text from a frame that comes from a master the text auto-flow will use the matching frame on subsequent pages that have the same master applied or insert new pages with the same master.
Note that the previous default behaviour was to edit all attributes for all master items linked, but also to lock the Master Page instance in the layers panel. If dealing with an old document and the new functionality is desired the instance will need to be unlocked or the Master reapplied.
Link to master page tutorial / video here
Amalgamated Text > Insert Text from File and File > Place
Text > Insert Text from File has been removed and File > Place should be used instead. The types of files available via File > Place depends on context, for example if a Text Frame is selected then text files will be made available.
Performance
(Win) Fix for system mis-reporting RAM on some systems leading to poor performance.
- If 'RAM Usage Limit' in Preferences > Performance is set to 1024MB you may be experiencing this issue. If so please set the limit manually to a higher value (typically the amount of Physical RAM installed) or Ctrl-Run Up to reset settings.
Menus and Studio
(Mac) Fixed the spurious black tiles issue when switching between multiple documents
(Win) Fix for redraw issues when dragging document windows between monitors on some monitor setups
(Win) Fixed Show Bleed failing to work under some circumstances
Fixed min / max size issue for some panels
Added Tooltips to Page Navigation controls
(Mac) Fixed Colour Panel tabbing issues
(Mac) Fix for Pasting control characters into Find and Replace fields.
(Win) Fix for Find and Replace fields not being cleared when starting a new document
(Mac) Paragraph / Character Panels now always show scrollbars if necessary
(Win) Fix for Min / Max / Defaults in Paragraph Panel Justification settings
(Win) Fix for crash trying to insert a Text Field without a text frame selected
(Mac) Fixed Text Wrapping Dialog tab order
Section Page Count is actually Section 'Last Page'
Added 'Run Last Page' to Fields Panel
Added Next and Previous Frame page numbers to Fields Panel
(Win) Tools toolbar leaves monitor viewport when undocking on some monitor set ups
(Win) Document Zoom Level is changed to 'Fit' when a Symbol / Asset etc is dragged out
(Win) Fixed drag drop from Explorer to floating Document windows
Fix for Paste Inside being disabled with multiple objects selected
Section Manager selection fixes
Tools and View
Fix for Text Frame Baseline Grids drawing incorrectly
(Win) Fixed issue setting CMYK colours for Guides
(Mac) Fix for incorrect Ruler Origin on spreads other than first
Text and Tables
Tables and Text frames can now individually be set to ignore baseline grid
Added support for language dependent smart quotes
Allow for space above at tops of columns in more places. Fixes issues with Art Text
No longer apply initial words formatting automatically to text generated by lists
Fix for effect of next paragraph style on character formatting not being undone correctly
Fix crash justifying narrow text
Page Number glyphs are now shown as placeholders on master pages
When creating a TOC reuse an unused style if there is one
Fixed Hyphenation to exclude nulls from hyphenation strings because they confuse length rules
(Mac) Fixed failure to ever set Restart Numbering 'Now' in Text Style Editor
(Win) Fixed issue with Arial Black being incorrectly reported as missing
Fix for Edit Text Style controls not updating when Font Family changed
Fixed issue changing Table insets after scaling
Fixed issue scrolling through the Font List if fonts with long names present
Resizing text frame no longer causes issues with cursor position on the text ruler
Fix for punctuation stopping 'Capitalise first word of sentence' from working
Import / Export and Printing
Fix for some EPS imports being incorrectly translated
Document fields such as 'Author' and 'Subject' are now exported to PDF
(Win) Fix for some stroke widths being printed incorrectly on rotated objects
(Win) Fix for flipped text printing
---
Earlier Release Notes Beta 206

I've asked/mentioned the ability for importing QXP-style tagged text files. They don't need the full verbosity that Q will export (which is far less verbose than ID's clunky tagged text). The fuller Q tagged text can support images, the creation and placement of objects, etc. But I would be happy for just handing text.
To directly answer your question? Of course it would be good!