vonBusing

I have to agree with you. Alot of people think Affinity needs to compete with or replace Adobe. Serif doesn't need to do this. Affinity apps are 50 bones with no subscription. It would be considered a success to take 5% of Adobe's marketshare with 70% of its features. If you don't like it, keep using Adobe products.
@wonderings
PS. If you think I'm bluffing about that 5%, consider Designer has 1 million users and Serif considers it a success. Now find out how many people use Adobe products. Somewhere north of 250 million.

Matching feature for feature is simply adding features without purpose.  That leads to bloat and is not a good approach to software design.
 

This is very true and both cases are needed. 
Though, many of us think that handling a PDF is a simple thing – after all it is selfcontained file that display and prints anywhere. Surely there must be some PDF toolkit library that allows handling it as an object?
I looked into this and this is not the case. Codewise passthrough PDF is just as hard a case as opening and editing it. That is why passthrough PDF is late coming. 

+1 for data merge functionality to create catalogues and guides based on content from databases.

I agree, these are two separate use-cases:
OPENING a PDF to convert it into publisher-source document, and PLACING an already fine PDF into a publication leaving it absolutely UNTOUCHED, aka passthru. (with the exact embedded fonts, no substitution)  Sometimes you make a publication where most is your own artwork, but on a few pages are "Ads, or Sponsors-Pages" coming from another design-bureau (made with another system and fonts), and you absolutely have no right to change anything in these files.

To illustrate the point, even a placed PDF is technically being edited in APub (and the others).
In the screen shot below, I am displaying a Q document. In it, I have a font that substitutes non-breaking spaces around certain punctuation. The instances are highlighted. (PDF from Qis identical.)

In the next screen shot, I have placed the Q PDF into APub. Because a PDF has zero idea about OpenType features, it is displaying colons on each side of the non-breaking spaces. As well, the end of story marker is being displayed, showing that even placed PDFs are being "touched."

And when I export this APub file with that placed PDF, those colons on each side of the non-breaking spaces are exported to the APub PDF.
This will only be cured with pdf pass though. (And done better than it is/was in PPX9.)

Being able to edit a PDF in Publisher is very useful for many of us. If someone doesn't want to edit it... well just don't edit it, but don't ask to remove this function.
If you just "place" the PDF (using the Place Image tool) it just put it where you want it, the size you want it to be and fonts are not replaced. So we have the best of both worlds.

Editing PDFs and placing/importing PDFs are two completely different things. If a customer provides a PDF which needs to be included as part of a new design then the ability to place and crop a page from a PDF file is pretty important. But this must be done as a pass through and NOT as a converted graphic. It needs to be 100% reliable and I hope Serif take this onboard.
Having said that, the ability to convert a relatively simple PDF into a page layout program can be really useful at times. People sometimes bring me MS Publisher files to be tweaked and I'd much rather make a PDF and then edit it in AD or APub than use MS Publisher for that. Its horses for courses.

But there are a whole BIG BUNCH of us who very much want to be able to edit a pdf.   We are extremely grateful for this wonderful feature in Publisher.   Why don’t you just print your pdf’s straight from Preview (if you are on a Mac) and then close the documents?   But please don’t ask the Affinities to take away this wonderful option from the rest of us!

This thread is locked, there is now a more recent beta available from the thread pinned to the top of this forum.
Click here to download the latest beta for macOS
Status: Public Beta
Purpose: General Testing
Requirements: None
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 latest build, and as always, if you've got any problems installing or running up, please don't hesitate to post here.
Any problems actually using this version please post to post in this forum and we'll get back to you as soon as we can. Many thanks for your continued feedback.
Please post any bug reports here. Please feel free to leave general suggestions and comments in the Discussion Forum.
Fix List
Document / Page Management
- Fixed crash opening some documents containing images on a Master Page
- Pages Panel updated to improve layout and performance
- Add Page buttons now enabled correctly after converting Artboard based document to Spread on Windows
- Removed bleed setup from Add Master Page dialog, it is a document setting
- Select Anchor to page should be selected by default for scaling in spread properties
- Fixed Page redraw after deleting artboards

General Tools and Menus
- Added Layer > Arrange, Alignment, Geometry, Transform, Insertion
- Added Layer > New Layer, Layer > New Adjustment
- Preferences options missing from dialog drop down menu
- Fixed marquee zoom when using the <Space>+<Ctrl>
- Fixed Find and Replace text field drop menus on Mac
- Fixed toolbar customisation - Distribute, Operations on Mac
- Fixed Guides editing default for Select Tool on Mac
- Updated minimum Zoom Out for view
- Fixed crash when assigning keyboard shortcut to File > Place on Windows

Text Tool
- Symbols indicating overflowing text added to text frames
- Fixed bug redrawing text flow after unlinking text frames
- Text wrap options dialog fixed for light UI on Windows

Text Panels / Text Style Editor
- Tidied Paragraph style dropdown drawing on Mac
- Fixed application of Kerning by dragging icon on Mac
- Text Styles Panel fixed to display description fully
- Fixed deselection of Stylistic Sets from Character Panel
- Fixed Initial Words not applying in Text Styles
- Fixed hyphenation Minimum Score not applying in Text Styles
- Fixed bullet character style for bullet not applying if tab stop value is 0 in Text Styles
- Fixed 'Ignore space if same style' not applying in Text Styles on Windows

Tables
- Icons added to table row / column extenders to advertise their purpose
- Table tool headers now reflect insets
- Frame settings now applied correctly to new tables
- Double-click on default format now edits that format rather than creating a duplicate

Resources / Resource Manager
- On File > Open, if linked resources are missing, request to locate

Assets
- Fixed Asset thumbnails when asset include image in CMYK document

Picture Frames
- Fixed Convert placed image to Picture Frame
- Custom zoom and placement maintained when Picture Frame is resized

Print / Export
- All formats now export with optional bleed
- Fixed export of Artboards in embedded afdesign files
- Print model not saved with pre-set on Windows
- Double sided prints flips on longest (wrong) side (on Windows)
 

Thanks @Seneca for the suggestions. Using styles properly is, of course, the most elegant way. But Text>Find was a powerful tool I had not tried before, and it did the job pretty well.

Yes, sorry, you are right.
Then try to find and replace feature.
Text > Find ...
You can search for any formatting, including font, paragraph styles, character styles and see whether that works for you, but it should.

Of course the best way to deal with this sort of thing is to have styles.
You define styles for your document and then simply update your styles with the fonts you need.

I wondered about the purpose of the baseline grid buttons on the main toolbar. In my opinion, this is a strange and overly complicated implementation, and so for the following reasons.
When you click the middle button (Show Baseline Grid Manager) the baseline grid manager will open. But what is the purpose of discerning an enabled and disabled (pressed and released) state for this button beyond the trigger action (see my video)? This button is a trigger button, not a switch. So the fact that it currently looks like a switch must be a bug.
But even more important, what is the purpose of having a switch (left button, Enable Baseline Grid) for the baseline grid to be activated or deactivated globally? When I create a grid-fitted document, why would I ever want to disable my baseline grid globally? Just to see my text scramble? No, a baseline grid is not a snapping option, it is a grid option. And fitting a piece of text to the grid is the duty of a paragraph setting. Associating the baseline grid with snapping is a conceptual mistake, in my opinion.
Hope you can see my point.
Alex 
 

Baseline-Grid-Manager.mov

You and I are used to the font substitutions mechanism in the ‘Plus’ applications, where we would use F&R if we wanted permanent replacements, but my point is that the fact of ‘Replace’ being permanent isn’t explicitly stated anywhere in the Affinity apps.

If bleed guides are enabled, clip to canvas should show the bleed content. If bleed guides are disabled, then bleed area can be hidden when clip to canvas is enabled. I would not want to have to disable clip to canvas to be able to se objects that extend into the bleed, because then, I would also se items that are placed beyond the bleed. That would be messy.

This happens a lot with the Mac. Fix it by going to the finder and select a file, either sag or ai, and use the get info command. In the Info window change the "open with" menu to whatever you want then apply it to all. 



hit continue and all is well.

This is how Affinity Publisher handles the matter when exporting to PDF. Suppose you create an element in your document that spans across an entire spread, including the bleed area. Then you can export either spreads or pages to PDF.
When you export single pages (Export > Area > All Pages or Export > Area > Current Page), you will see that Affinity Publisher will effectively create a bleed area along the binding edge and duplicate the respective page contents into this area. In other words, it will take the first closest millimetres of the opposite page’s content and add that to the bleed area. In my screenshot, you will see that the letters that fall into the (virtual) bleed area along the binding edge appear on both of the exported pages, as is to be expected. On the other hand, when you export to spreads (Export > Area > All Pages or Export > Area > Current Page), there won’t be an additional bleed area at the binding edge, of course. Indesign does it a little differently. There you can specify bleed for the inner and the outer edge of a page, rather than for the left and the right edge. This will give you more flexibility, for you can export to single pages without having a bleed area along the binding edge. I haven’t found a way to do this in Publisher so far.
In any case, you will have to ask your printshop how they want to have your PDF documents. They will usually advise you how to setup your document and make the necessary adjustments during imposition, depending on the binding method. 

 

If you use layer effects in Affinity apps, the actual area is rasterized on pdf export. This is a known issue since layer effects were introduced. Big improvements have been made with previous versions of Affinity apps to reduce object rasterization during pdf export, but this has not been addressed, what I know of. My best advice is to avoid them when vector-sharp output are expected. Many times there are other means to achieve the same effect that will not rasterize. Alternatively, you can also export at higher resolution for rasterized objects.

Great start to the app, a few rough edges obviously.

1. While it's easy enough to use any Pantone colour in the Swatches panel, it's hard to add one to the document swatch. The #1 way people will try is to go to the Swatches panel, then choose "Add Global Colour…", but if you choose Pantone in that modal dialog box, you can't show the list of swatches by name, and you can't search. You can hover and wait for a tooltip, but that's a nightmare.

2. Going a different way, choosing Pantone from the Swatches panel, then 485C, then applying that to an object, then right-clicking the object and choosing Add to Swatches > From Fill works, but it's not obvious.

3. Converting the Pantone 485C swatch back into CMYK doesn't give the values I'd expect. In InDesign, this is 5.84/97.64/100/0.57, but in Affinity Publisher I see 0/81/87/15? Another: Pantone 130C in InDesign is 2.43/37.87/100/0, but in Publisher it's 0/30/100/5. What's going on? Is there some kind of double conversion happening? Is it just that the new "V2" of Pantone+ Coated is completely different *again* from the last version? (Pantone+ Coated is not the same as Pantone Coated, all the CMYK breakdowns changed in CS5 but few noticed. 485C used to be 0/98/100/0.) Worth noting that the Pantone+ CMYK Coated values *do* seem to be the same between InDesign and Publisher. Still, if Pantone numbers in Publisher are so wildly different from Pantone numbers in InDesign, clients will be pretty unhappy. Most people only use the "C" numbers but then print in CMYK anyway — the breakdowns are really, really important. This may be Pantone's fault, but Affinity will get the blame if colours don't match.

I don't believe this is a realistic goal. Affinity Publisher is not aiming at getting EVERYONE to switch from Indesign. They are quite many low hanging fruits to focus on with people doing much simpler things, that could do with a simpler tool that get them all the way they need and in a more enjoyable way.
Nevertheless, data merge specifically, would be really useful. 

Click here to download the latest beta for macOS
Status: Public Beta
Purpose: General Testing
Requirements: None
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 latest build, and as always, if you've got any problems installing or running up, please don't hesitate to post here.
Any problems actually using this version please post to post in this forum and we'll get back to you as soon as we can. Many thanks for your continued feedback.
Please post any bug reports here. Please feel free to leave general suggestions and comments in the Discussion Forum.
Fix List
Installer
- Fixed failure to start on some systems due to font issues
Start up
- Reset Table Formats and Title Exceptions missing from Ctrl+Run on Mac
Document / Page Management
- Offer option to convert Artboard documents to Spread documents on open
- Bleed guides / visible bleed now available in the main view
- Fixed document bleed not being automatically applied to new spreads and master spreads
- Fixed bleed from masters not drawing on applied spreads
- Snapping grid now draws on current spread rather than always the first spread
- Transparent background is a document setting, not a per-spread setting
- Adding a pages to a facing page document generates the wrong page labels
General Tools and Menus
- Fixed Pop up Sliders not closing on Mac
- Fixed priority issue with Select Tool / Placement Tool
- Fixed Zoom Out causing unwanted Pan
- Fixed Gradient Tool to add stops correctly
- Added Paste FX to Layout Persona Edit Menu
- Added Geometry operations to the Customise Toolbar dialog on Mac
- Fixed applying style from Styles Panel when in list mode
- Rearranged View menu to separate guides and rulers
Text Tool
- Fixed diacritic entry via dead keys on Mac
- Drop Caps now have a 'Scale for Descenders' attribute
- Fixed Leading entry glitches on Windows
- Fixed Kerning entry glitches
- Fixed Tracking entry issue
- Fixed intermittent crash when adjusting the Fill and / or Transparency for Decorations
- Fixed spelling error highlights not updating whilst editing Text Wrap settings
- Fixed crash setting Text Wrap option on EPS images
- Text flow handles now hide when view is zoomed a lot, out to prevent view clutter
Text Style Editor
- Layout improvements
- Fixed Style description truncation in Text Style Editor on Windows
Tables
- Setting Table cell size from Table Panel not working correctly
- Fixed Keep with next lines breaking Table layout
- Table Save as Default could cause app to crash 
- Right click on table header not deleting multiple columns / rows
- Table Formats should include Frame fill, stroke and insets
Resources / Resource Manager
- Document policy for Embedding / Linking images available from File > New / Document Setup
- Better prompting when missing Linked Images encountered on Document Open
- Resource Manager now always shows resource thumbnails
- Placement sort in Resource Manager fixed
- Resource Manager columns are now resizable
- Fixed Resource Manager grid scroll issues
- Fixed Properties read out for pasted Affinity Documents
TOC
- Fixed glitch when TOC was deleted leading to incomplete removal
Print / Export
- Double sided prints always flip on longest side (partial fix)
- Fixed converting colour for PDF/X-3 export rasterising elements
 

Ne t'inquiètes pas et utilise Google traduction (rien ne t'empêche de laisser la version française dans ton message, les traductions automatiques étant ce qu'elles sont…), ça permettra aux francophones de te comprendre et de te répondre.
Serif fait un gros effort aussi pour répondre dans la langue utilisée.
Second point, beaucoup écrivent en anglais ici même si ce n'est pas leur langue, et au final ça fonctionne et personne ne s'offusque des erreurs de grammaire ou d'orthographe

Hi all,
Welcome to Affinity Forums
Bleed preview (on canvas) will come in a future update still during the Public Beta.

In the case of Publisher 1.7, this beta isn't quite feature complete because a few smallish things weren't ready in time. We couldn't delay going public, because someone announced the date during the Designer iPad launch. The bleed preview is an example of that; it should be in the next beta later this week. We may also pick up some extra features from Designer 1.7 and Photo 1.7, which are both still under development and which should be released at about the same time as Publisher 1.7. (We need to keep them in sync because they can open each other's files.)
The bigger issue is that 1.7 isn't the end of the line, even when it is released as a paid-for product. For comparison, we first released Affinity Designer in 2014, as 1.0, and it has had new features added to it every year since. Hence its version is now 1.6. And all those updates were free, for people who had bought a previous version. In the same way, features which will be missing from Publisher 1.7 even when it comes out of beta, will be added in free version updates over time. So in that sense the product isn't "complete" and won't be until we start version 2.0.