XaviCG1

Look for this. This is for Publisher 2.

+1 for GREP in styles. Thanks

+1 for GREP in styles. Thanks

I'm interested in this feature too. 
I'm using Publisher since the initial public betas were published... and since then i'm moving from other apps to affinity apps including Publisher.
My 'ecosystem' is changing to affinity apps, but a reduced amount of collaborators/providers/partners, etc. don't. A real solution is they use affinity apps too, obviously... but the usual kind of collaboration, usually resides in collaborate with texts. Write/correct/change those texts... 
I think, linking external text files, like images, would be a really nice option to fast and intuitive workflow and to finally convince more people to adopt affinity apps as their usual design apps
Best regards

We are pleased to announce an update for the macOS release of Affinity Publisher, version 1.8.2
Changes in this build
The changes in Affinity Publisher for macOS 1.8.2 (made since the last release Affinity Publisher on macOS 1.8.1) are as follows:
Fixes & Improvements:
General
Fixed possible source of instability when enumerating fonts at startup Fix for bleed not available in Photo Persona New document panel - terminology and UI tweaks New document panel - saves settings between uses Stability and performance improvements for geometry operations Fix for collecting multiple instances of the same resource image Fixed issue with placed Artboard documents losing selected Artboard ID Application (bought through MAS) will now run on Lion and Mountain Lion (again) (Mac) Changing preflight profile with no document open causes crash (Mac) Fixed possible crash on File > New in Designer Persona (Mac) Fixes for blurry icons on non-retina screens Help and Localisation improvements Document Management
Fixes for slow page operations - adding / deleting /moving etc Stability and performance improvements adding and deleting pages Fixed issue with sections being incorrectly deleted when pages deleted Hyperlinks
Hyperlink Panel wasn't displaying hyperlinks on Master pages Renaming hyperlinks in Hyperlink Panel can detach objects Text
Spelling not honouring the language set for the text frames when opening document Fix for ligatures being disabled in justified text Fixes for Catalan Hyphenation (Mac) Fixed crash typing into Font name selection UI IDML
IDML Import could create corrupt images IDML Import crash fixes with specific documents IDML Import - crash fixes for specific documents IDML import of hyphenation Other Import / Export
Fixed issue exporting caused by hyperlinks PDF Export - Images with a 1 bit mask could be output incorrectly (or not at all) XLSX - File import improvements Earlier changes and fixes in 1.8 since 1.7 (including the new 1.8 features) are listed in some detail in this 1.8.1 update announcement.
 
UPDATING TO THIS VERSION (Free for existing customers)
The software version can be seen on the splash screen and the About dialog (in application menu, Affinity Publisher > About).
If you’ve purchased from the Mac App Store— updates are done automatically next time you run your software after it is available in the Mac App Store. If this does not happen for you, open the Mac App Store app and go to the Updates page and then Store > Reload page or press CMD+R. This should hopefully force the update to show. Apple sometimes phase roll outs around the world which can mean it may take up to 72 hours for your update to be available.
If you’ve purchased from the Affinity Store— each time you start the software it will check for updates and offer to download and install any available update, or in the application main menu there is an option Check for Updates. You can download the latest installer by logging into the affinity store here and find the order in your account and use the "download" button in there. Alternatively, this new release (and previous versions of Affinity Publisher for macOS) can be downloaded from this link (that installer is NOT for Mac App Store purchases and needs a product key).

That would be nice.
In the meantime, there is a workaround.
Designer works the same way as Publisher in this area: The Text Style named Base inherits your User Interface language as its default Spelling Language. And all the other paragraph styles inherit from Base.
However, you can change that. Just look in the Text Styles studio panel, double-click on Base, and change the Spelling Language to Catalan if you have its dictionary installed:

Then:
Click OK to saved the modified Base style. Click on the hamburger menu for the Text styles studio panel, and choose Save Styles as Default:  
After that, all your paragraph styles should default to Catalan. You will need to specify a paragraph style for your text (e.g., Body), as any text without a style will be assumed to be Spanish. But all of the styles will inherit from Base, so they'll all start out as Catalan instead of starting out as Spanish; you won't need to keep changing them.

Affinity Publisher uses the Hunspell Engine for spell checking and it also allows for additional Hunspell dictionaries to be added. You can download additional dictionaries from LibreOffice's GitHub page here but you can find direct links in the below post. 

Once you've downloaded the correct file(s), you can use them in Affinity Publisher by following the below instructions:
Please note: There are some differences between how you install Hunspell dictionaries for macOS/Windows, since we use the default spelling dictionaries available within macOS but it's also possible to add custom Hunspell dictionaries too.
macOS
You may already have Spelling dictionaries available but not active within macOS. To check, go to:
System Preferences >  Keyboard > Text and select Set up... from the Spelling drop down menu. Please check the required language if available. If it is, check the required language and restart Affinity Publisher for the dictionary to appear within the app.
If the required language is not available within macOS, you can install standard Hunspell dictionaries for use with Affinity Publisher. Hunspell dictionaries consist of two files, xx_XX.dic and xx_XX.aff. Copy both the .dic and .aff files to: ~/Library/Spelling
Once you have done this the language should become available to select from the Spelling drop down menu in System Preferences >  Keyboard > Text. Once you've checked the required language, restart Affinity Publisher for the dictionary to appear within the app.
Hyphenation dictionaries can also be installed in a similar way but they must be installed into a subfolder. Navigate to ~/Library/Spelling/ as above and create a subfolder with a name in the format of xx-XX ( substituting xx-XX for the locale id ). The dictionary comes as a single file with a name in the format hyph_xx_XX.dic - this file should be copied to the subfolder. Now restart Affinity Publisher for the dictionary to appear within the app.
Windows
You can add additional dictionaries and hyphenation dictionaries by going to Edit > Preferences > Tools. The default Additional dictionary folder used by the app is C:\ProgramData\Affinity\Common\1.0\Dictionaries but you can change this location by clicking Browse... - Please make sure that you specify a folder that holds all subfolders for each locale and not one specific locale folder as this will not work!

To copy any downloaded dictionaries and hyphenation dictionaries to the Additional dictionary folder click Open... but before copying your files to this folder you will need to create a subfolder with its name in the format of xx_XX ( substituting xx_XX for the locale id ). Once you’ve done this you can copy your xx_XX.dic, xx_XX.aff and hyph_xx_XX.dic files to the subfolder. Now restart Affinity Publisher for the dictionaries to appear within the app.

Please note: Any changes to dictionaries require that you restart Affinity Publisher

Hi @reminous,
in one of the recent beta versions Serif introduced the 'My Account' feature. Currently it only alows to sync content that was bought or delivered as a free give away in the Affinity store. But there also have been indications that this will be developed further and could eventually become some kind of Affinity cloud to share all kinds of content (assets, colour palettes, etc.).
Cheers,
d.

I'm having a similar issue, but with Export. The option to export to google drive is grayed out. I contacted google drive support and they told me
So this is an affinity problem. Other apps work fine. Any chance of an update? This complicates my workflow significantly.

I'm interested in this feature too. 
I'm using Publisher since the initial public betas were published... and since then i'm moving from other apps to affinity apps including Publisher.
My 'ecosystem' is changing to affinity apps, but a reduced amount of collaborators/providers/partners, etc. don't. A real solution is they use affinity apps too, obviously... but the usual kind of collaboration, usually resides in collaborate with texts. Write/correct/change those texts... 
I think, linking external text files, like images, would be a really nice option to fast and intuitive workflow and to finally convince more people to adopt affinity apps as their usual design apps
Best regards

+1. Thanks

That document is already "fixed". Is this what you were seeing?  Screen Recording 2020-06-08 at 09.27.36.mp4

+1 for GREP in styles. Thanks

Yes
I think the same as you...
Who never used Grep Styles, don't understand How magical it is... (and how different as a F/R it is..., including, how different as plain Grep F/R it is too.).
I suppose it's difficult to understand that 'magic', probably for someone who never used Grep Styles.
When you use linked text styles and include grep styles... wow!! the workflow is incredible. 
Definitively: +1 for GREP styles please 😀
I hope it would be take in consideration by the dev team.
My best wishes for all of you
Best Regards!

Hey there, video tutorial in real time, showing my workflow that I use to build my characters
I hope this helps you!
 

Thanks Walt.
I understand as obvious the requirement we must have all the fonts installed to open a document Or to edit a document (in this case a pdf)... but sincerely not on embed pdfs (it's a contradiction).
But don't worry for this. Now I understand how work aPub and i'll do my better efforts to adapt to this kind of features (although i think this in particular it's a big error in concept -sorry -)
Thanks a lot 

It may help if you check your Export settings for the PDF. In the More... dialog make sure you're embedding all fonts, not just a subset.
Alternatively, if that doesn't fix it, you could change that setting to export text as curves.

That italic "ti' sure looks to be a ligature, which could be causing the problem.

I'm interested in this feature too. 
I'm using Publisher since the initial public betas were published... and since then i'm moving from other apps to affinity apps including Publisher.
My 'ecosystem' is changing to affinity apps, but a reduced amount of collaborators/providers/partners, etc. don't. A real solution is they use affinity apps too, obviously... but the usual kind of collaboration, usually resides in collaborate with texts. Write/correct/change those texts... 
I think, linking external text files, like images, would be a really nice option to fast and intuitive workflow and to finally convince more people to adopt affinity apps as their usual design apps
Best regards

You and I must be related. I agree 100%.
 
 

Thank's for your answer 
Yes, you're in the correct way 
i'll dream with this feature.
I understand that create new 'app' or use tied affinity app would be 'the very best' to integrate into the affinity ecosystem (provably with StudioLink)... but I understand, create that app, will occur in a long time... I suppose.
The initial step... in my mind... is to use something like (tagged) rtf, or txt,... Something... basic in functions, standar to be used for everyone.
It probably produce 'noise' (coded text -affinity labels- only seen in the txt editor). Philosophy of xml.
imagine a file (.doc or docx, or otf...). Opened by you... resaved as .txt. to force Publisher compatibility. Then...Linked to Aff. publisher.
In Publisher you applied styles, organize boxes, etc... (the linked file include those tags to the .txt file -with styles or text attributes information-)... I think everybody can understand an indication like: 'you can change what you want between tag <affinity> text editable </affinity> DON'T TOUCH ALL OTHER TEXT' 
Share file by something like dropbox, mail or what you want...
There are corrections? no problem... the editor change the text. 
Finally you update link in Publisher... and voilâ . The Magic acts. 
I'm sure there will be -as you've said- a lot of 'but..' and 'What if...', including the obvious situation... the editor break the code
There's where in the near future (i hope) affinity develop that light but powered, 'affinity text editor' with StudioLink compatibility   
Have a nice day!!!

I'm interested in this feature too. 
I'm using Publisher since the initial public betas were published... and since then i'm moving from other apps to affinity apps including Publisher.
My 'ecosystem' is changing to affinity apps, but a reduced amount of collaborators/providers/partners, etc. don't. A real solution is they use affinity apps too, obviously... but the usual kind of collaboration, usually resides in collaborate with texts. Write/correct/change those texts... 
I think, linking external text files, like images, would be a really nice option to fast and intuitive workflow and to finally convince more people to adopt affinity apps as their usual design apps
Best regards

You are right about that. I made a simple test file (attached) with a header that says "Left Page" on the left and "Right Page" on the right. Delete, for example, Page 2 from the Pages Studio, and then the rest of the pages after that are now backwards.
I am not sure this is a bug, but I do think this should be reconsidered.
I had some headache with something that I think is related just yesterday, and I spent nearly 30 minutes trying to figure it out. With editing and formatting changes, the end of my chapter was now on the previous page from where it was previously, which was a page on the right. Because of the change, I wanted to the page (which was now the last page in the chapter) from using the "Inner Pages" master to the "End of Chapter" master. There was no simple way to just swap masters because a page can have more than one master. No option I tried would allow the text to flow onto that page. I also had reassign the text frame flow to include the page where I had changed the master. Only, when I did that, the text thread flow showed it was included, but no text was visible. After a lot of messing around, I discovered that even though I had deleted masters from the right page, the layers panel showed it was still still there because of the left page. I had to also remove the master from the left page and then reassign the original master to just the left page, fix the thread flow, and then it finally did what I wanted it to.
That is really hard to describe. I may need to try to make a video if anyone doesn't understand what I am saying and wants to see it.
Thankfully it was the end of the day, because I went home frustrated and discouraged. I don't think the master page functionality is ready to cope with repagination issues.
 
master_page_test.afpub

I completely agree about paste FX being in right-click menu.
You could also create a 'Style' to do this:
right click one of your photos with the shadow and outline and choose 'create style' Make sure 'Styles' is showing in View > Studio Scroll to the bottom of the styles palette and your new style will be the last item - you can right-click that to rename it. Any new photo frames just select them, then click your style to apply it. Personally I think styles is unfinished - when you click 'create style' a dialog should pop up straight away to name it - that would give instant feedback that something has happened and take the guesswork out of finding the style you just made. And you should be able to 'update style from selection' the way you can with a text style.

A bit old thread, but for convenience of other users:
Inserting Zero-Width Space in text where you would like initial words to end and then using it as End character can be useful. You can enter '<ZWSP>' (without quotation marks) in 'end characters' input box. Not ideal, but mostly workable solution.