Fantomas.CZ

While it would be good to bundle more spelling and hyphenation dictionaries for Mac and Windows to avoid users having to figure this out on their own and then ask for tech support, I think this is a real issue for Publisher on iPad. Not only can you not hyphenate many languages on iPad, the lack of hyphenation means hyphenated documents would flow differently on desktop vs. iPad for many common languages such as Dutch, Danish, Czech, Polish, Norwegian, Finnish, Swedish, and Greek.

We've reported this issue previously, please see the thread below. Affinity doesn't work the way other apps do and the way we are all expecting.
If you drag select or Shift + left/right arrow select a word, Affinity shows the word as selected and Cut/Copy will copy only the word which is as you would expect. If you double-click a word to select it, Affinity shows the word as selected, same to the above, but Cut/Copy will copy the word and the following space. This is inconsistent and a usability issue because it's not showing the selected text any differently than above. When you Paste, it pastes whatever is on the pasteboard without respect to the surrounding text. Serif has to bridge the gap between Apple and Microsoft. Here's how Apple apps work:
Regardless of how you select a word, Cut/Copy copies only the word without the trailing space When you Paste text copied in one Apple app into the same or another Apple app, it adds spaces around the word as required. Pasting into the middle of a word adds spaces on both sides while pasting at the start of end of a word separates the pasted word from its neighbour. It doesn't add spaces if you Paste text copied from a non-Apple app. (And Apple has a bug with pasting from Microsoft apps, it doesn't always work properly.) Microsoft apps work this way:
If you double-click or Shift + right arrow select a word, Microsoft shows the word and the trailing space as selected and Cut/Copy will copy the word and space together. I find this odd. If you drag select or Shift + left arrow select a word, Microsoft shows only the word as selected and Cut/Copy will copy only the word. When you Paste text copied from any app, it separates the pasted text by one space on either side regardless of whether or not the pasteboard contains leading or trailing spaces. You never wind up without a space or double spaces. This is   

If you double-click a word, rather than drag-selecting the letters, and then drag the word to the start of another word – the insertion cursor being immediately before the first letter – you should get some of the functionality you want, if I have understood your requirements correctly, since the space after the word is also moved (even though it’s not selected on the screen).
Granted, it doesn't do everything you want but it might help with some of it.

Hi again, 
sorry to start a new thread, but I read one should not ask multiple questions in one thread, so I'll try my luck and repeat the second question burried in my last post.
I started using APu for iPad, it looks great, I love what you did for the user fonts, and my question is: could you do it for hyphenation/spell check dictionaries too? Could you introduce installable spelling check and hyphenation dictionaries? 
I'm using two main languages: Latin and Czech. For Czech, the iPadOS has its own (I guess) spelling dictionary, but not hyphenation, and neither is available for Latin, at least not in the system. So the result is that the Latin text gets hyphenated and rather successfully, but the Czech text is not. Which is not usable in the current state. 
Is there going to be a fix for that? 
Thanks for the answer!

Hi Affinity Team, 
after repeating the same crash like three times, I recon it's time to share it with you. I'm working on M1 Mac mini with Sonoma 14.2.1 on it, Affinity Publisher 2.3.1.
Steps to reproduce the crash:
Open the file. Go to page 374. Select the Latin text (left column) from AD LAUDES to ... well, it varies. I wanted to copy the entire feast of Nativity, i.e. from AD LAUDES to a third Antiphon (Aña.) on page 378, but sometimes it crashes even before that.  It crashes just by selecting the text, nothing else needs to be done. Once I was able to select the text and even copy & paste it, only to have the program crash on me doing the same with the Czech text in the right column.
Thanks for taking care for this, I think I don't need to tell you, how bloody annoying is to have the program repeatedly crash, reopen all the documents I need for my work, because - and this might be a good idea to fix too - it doesn't reopen all the bloody documents, so I need to bloody do it manually, although my settings say otherwise!
Psalterium diurnale S.O.Cist.afpub

Hi @Fantomas.CZ,
Not anything new to share sadly, I'm now watching the improvement internally so if there's any change I'll post back on this thread.

The issue "Paragraph break point regression over V1 allows commas at the start of line" (REF: AF-38) has been fixed by the developers in internal build &quot2.3.0.2083&quot.
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.

Back in the day it was "If it compiles; Ship it!"

Hi All,
We have just made 2.2 live across all App Stores and our website. As always, the feedback we have received from you all during this beta has been an incredible help in both shaping the new features as well as squashing many bugs!
The build we have released is the same as RC3 (build 2005), meaning for the time being whether you use the latest beta version or switch to using the release version they are the same. If you anticipate taking part in the next beta you may wish to keep your current beta version installed, as this will be updated on auto update when a new beta is available. This will either be a 2.2 patch if we feel one is needed, or moving straight onto a 2.3 beta.
It would be impossible for us to do what we do without your support, and I just wanted to say a huge thanks for everything you have contributed to this release.
All the best,
Ash

Thank you, Mike, that was it! I reset and recreated my shortcuts, and it was fine. So that's hopefully solved 😊

Hello everyone, 
there is one thing that I have to do every time I open a document: go over to the upper right corner and switch the Swatches from "Colors" to "Document". As I mostly do typesetting of simple-coloured documents with two or three colours, I don't really need a huge swatch of every colour that I won't use, but I always need to use those two or three concrete colours that I have already defined. 

My suggestion: could this setting be saved in the document and reopen in its last state, same as the newly opened document always opens on the page where I left off? 
EDIT: One more thing came to mind. Could you also do this for the other toolboxes? Like it opens in Paragraph, as I left it while saving (so far so good), but Bullets and Numbering open again, although I have never used this feature in my books and brochures. I mean, it is definitely important and it has to be there, but does it need to open every time and take up space for other toolboxes that I actually use? 
Also, in the Mac version, there is obviously a hard limit on the Swatch panel size, so it cannot be resized to occupy only one line of colours, it always takes up space for like five lines. On Windows version, it's ok. And I'm talking about all the production as well as beta versions in V2.
Thanks for the consideration, have a nice day!

Thanks a lot to all of you!
Yes, this is a bit confusing. I had no idea there is a setting like this in MacOS itself (nor do I get, why anyone thought it useful). Maybe a small warning directly in APu's settings would be handy (there is one just a few lines lower), so that more people wouldn't blame Affinity, when it's system's fault 🙂 

Hello everyone, 
there is one thing that I have to do every time I open a document: go over to the upper right corner and switch the Swatches from "Colors" to "Document". As I mostly do typesetting of simple-coloured documents with two or three colours, I don't really need a huge swatch of every colour that I won't use, but I always need to use those two or three concrete colours that I have already defined. 

My suggestion: could this setting be saved in the document and reopen in its last state, same as the newly opened document always opens on the page where I left off? 
EDIT: One more thing came to mind. Could you also do this for the other toolboxes? Like it opens in Paragraph, as I left it while saving (so far so good), but Bullets and Numbering open again, although I have never used this feature in my books and brochures. I mean, it is definitely important and it has to be there, but does it need to open every time and take up space for other toolboxes that I actually use? 
Also, in the Mac version, there is obviously a hard limit on the Swatch panel size, so it cannot be resized to occupy only one line of colours, it always takes up space for like five lines. On Windows version, it's ok. And I'm talking about all the production as well as beta versions in V2.
Thanks for the consideration, have a nice day!

Hello everyone, 
there is one thing that I have to do every time I open a document: go over to the upper right corner and switch the Swatches from "Colors" to "Document". As I mostly do typesetting of simple-coloured documents with two or three colours, I don't really need a huge swatch of every colour that I won't use, but I always need to use those two or three concrete colours that I have already defined. 

My suggestion: could this setting be saved in the document and reopen in its last state, same as the newly opened document always opens on the page where I left off? 
EDIT: One more thing came to mind. Could you also do this for the other toolboxes? Like it opens in Paragraph, as I left it while saving (so far so good), but Bullets and Numbering open again, although I have never used this feature in my books and brochures. I mean, it is definitely important and it has to be there, but does it need to open every time and take up space for other toolboxes that I actually use? 
Also, in the Mac version, there is obviously a hard limit on the Swatch panel size, so it cannot be resized to occupy only one line of colours, it always takes up space for like five lines. On Windows version, it's ok. And I'm talking about all the production as well as beta versions in V2.
Thanks for the consideration, have a nice day!

No problem 🙂 
My bad, you are right. It works for me, because I increased the left indent to 1 mm for the entire paragraph, which fixed the situation. When I tried setting it back to 0 mm, the issue was there again.
So do I 🙂 

Strangely enough, I have tried the same file in the new 2.2.1954 beta, and it didn't put the comma to the beginning of the line, so it works for me now 🙂 

Really? I didn't know, but thanks! Then the question is, whether this character is so important, that it should be possible to insert it via the menu, or not. I'd say it is 🙂 
Nice, thanks! I have saved it as reference for later 🙂 

Hello everyone,
this thread has been recommended to me as a correct place to suggest new functions, so here it is 🙂 It would be a great help. if you were to rework the paragraph composer for Czech, and possible also other languages, to consider tying orphan prepositions like "v, k, u, s, z, o" (UPPER as well as lower case) to the next word, so that they don't end up hanging at the end of line. The same goes for "A (upper case only) and i, I" (just they are not prepositions).
Thank you, have a nice day!

Of course. I just took out the text, that's concerned, so it's on page 4, right column, near bottom of the page. 
BTW, if you are going to rework the paragraph composer for Czech, please consider also tying orphan prepositions like "v, k, u, s, z, o" (UPPER as well as lower case) to the next word, so that they don't end up hanging at the end of line. The same goes for "A (upper case only) and i, I" (just they are not prepositions).
EDIT. One more thought comes to mind: you have a zero-width non-joiner character. What about introducing a zero-width "joiner"? It would be very handy in cases like this, or if the hyphenation doesn't work as it's supposed to and you're not feeling like troubleshooting the hyphenation dictionary...
Thank you!
Sample.afpub

It does the same on Mac as well as on Windows (I work on both and I have checked).
Of course, below, you can see the special characters on. As you see, there is only one NBSP.

 

Hi everyone, 
I have seen this bug in the last version 2.1.1. and 2.1.0 probably too. It's quite simple: when I try to insert a narrow non-breaking space using keyboard shortcut, it results in a normal non-breaking space being inserted. When I use the menu entry, everything works as supposed, even though I use the same keyboard shortcut, that is written right next to the menu entry. 
The keyboard shortcut for a standard non-breaking space works as intended. I have seen this only on Mac, the Windows version seems to be normal. 
Is there something I can do to fix it, or do you?
Thanks, have a nice weekend? 

Thank you guys! Yes, that was it. I tried Cmd+Shift+Space, and it works as it's supposed to. So I might need to relearn this. Which is still much better than having to use the menu... 🙂 So we can consider this closed. Thanks again!

Hi @Fantomas.CZ @MikeTO,
Many thanks for providing detail on this issue, I've been able to replicate the problem using Mike's file and have now reported it to the developers for further investigation/resolution.

I have one final update, before this gets (hopefully) fixed.
You don't have to create a new single sided Master Page. It's enough to delete the unused elements, so if you name them correctly, you can just edit detached, and delete them. It's not enough to hide it though, because it's already hidden.

Thanks a lot, that could actually be a solution. I'd prefer not to have to do 4 other Master Pages, but it seems I have no other choice...