Angalanse

Prophet, I agree. I would gladly have provided that, which was also the reason why I uploaded a more detailed clip. But given the official responses I was given, why would I continue pushing the issue? If they are clearly not interested in looking into the odd behavior, why should I? I mean according to them the issue is already resolved: there is no problem, and if it is, it was my fault.

Appreciate the answers, put to add on the last comment -- what is so frustrating for me is that this has ever since the start been phrased as *my* problem. It is not, in my opinion. It is *Serif's* problem, which I (at least initially) wanted to assist them with. The issue has been handled as if I had posted in a support forum where I ask Serif (and others) to solve my problems. But this is a bug forum, where I had assumed that the roles are reversed (I.e. Serif asking users for assistance in ironing out inconsistencies). Instead, I am either offered (incorrect) descriptions of what I did, or suggestions that I need to "prove" that there is an error. Therefore, I ask again, what kind of issues *do* Serif want me/us to raise here?

Walt, I do appreciate the reply and the hypothesizing, but please read the official communication again.

Prophet, sorry, I didn't scale the frame. I was being sarcastic about the fact that the official reply assumed that I did and closed the case. Alfred, why on earth would I want to do that? Why would *anyone* want to raise issues in this forum? It's a genuine question, given the official replies to the enthusiasts?

Right. But the issue is already resolved according to the official reply: "Nope, it's not a bug. You scaled the text frame, so the text will come in scaled."

What I don't get is the reversed positions here. If I point out a problem, the responses suggest that I should be able to prove that it is indeed a problem. Why would I do that? Isn't Serif interested in getting feedback from real users? Also, why do you assume that I'm an inexperienced user? I'm not. I have used the Affinity suite from the very beginning, and have even been part of the beta tests. I have been working with publishing for over 20 years, specifically in academia, where I have been enthusiastic about being able to suggest alternatives to the Adobe suite. Affinity is (or rather, I assume, could have been) perfect for PhD students, post-docs or for that matter other research groups that do not want to bind themselves to expensive services. This is an issue that has reached the leadership at the universities in Sweden that I have worked at, and I have shared my experiences. Yet I know, because I have helped out with very many theses and books, that the issue that I am describing would be a huge issue. If the text size changes by resizing the frames, that would mean that the researcher or doctoral student would have to check the entire book every time he or she makes such changes. Now, I really, really don't get why you assume that this is a user error. Once again, I'm not an inexperienced user, I never moved the scaling handles. You just assumed that I did and labeled the problem as being my fault. But what if it's not? Aren't you interested in getting this kind of feedback from the users? Isn't this what a bug forum is for? And I do not share your view @Hilltop regarding the professional tone in the responses. A professional response, in my opinion, would have been to reply with a short thanks and ask for the file, to see whether it was indeed a bug.

I really don't get the antagonistic tone in the official and semi-official replies here. I post these issues as I am (was?) enthusiastic about the Affinity suite and wanted to help improve what I considered as problems that hampered my work-flow. Yet I'm met with a form of gaslighting -- it's not a problem, and if it is, it is your fault. Let me ask you: what kind of issues *do* you want raised in this forum?

Gabe, I'm not really following you. I mean it's great that you can replicate it, and great that Walt was able to point out the source of the problem, but it still is a problem, right?

Hey Walt, let me help you a bit: "Dear Angalanse, thank you for notifying us of this odd behavior. We are thankful, as always, for the active community members and bug-hunters, who are integral to the development of the Affinity suite. Would you mind walking through the steps that resulted in this odd behavior, knowing fully well that it will take some of your precious time that you surely rather would devote to work or taking care of the kids. Even if the deviating behavior is unique, it will give us important information for ironing out bugs and developing Publisher further." 2020-08-19 07-37-24.mp4 Why thank you Walt, I will try: I am working on a document with text that I pasted from Word. Changing the font size to 12 ->13.7 is not the only odd behavior. Given your nice reply, I have opened up the document on another computer, and I can now show you similar behavior in another part of the document.

Thanks again for the reply. I agree that copying and pasting the text is a workaround, but it is still a bug that could become a major hassle when working on longer documents, and which should be addressed. For instance, if I were to work on a book, I would not want to deal with unexpected font size changes when changing the size of text frames.

Thanks for the reply, but is it difficult to see? The upper frame is linked to the lower frame. When I change the size of the upper frame (using the correct handle), the text flows into the lower frame, and for some reason changes size from 12 pts to 13.7. If I had used the incorrect handle on the upper frame, I assume that would have resulted in the change of font size in that frame, not the lower one.

Hi, when I'm changing the text frame, the font size also changes which makes it difficult to get any work done. See attached snippet. 2020-08-18 11-06-36.mp4

Thanks for the thorough answer Tegwyn, I really appreciate it! I'm not scared off. For this particular project, I nevertheless chose to go back to InDesign, but mostly as I still have overlapping licences. I'm a proponent for Publisher, and often endorse it at work, where me and my colleagues mostly use it for scientific posters, pamphlets and questionnaires. I will give it another try next time I work with relatively short books such as theses. My current project is a clear deviation by being over 800 pages long. If I run into troubles at a late stage, much work will have been in vain.

Thanks for the advice LFGabel and Tegwyn! I'm still a bit concerned whether this slowdown, at such an early stage of the work-process, is indicative of additional problems further on (such as when adding large images). Have you experienced such problems, if I may ask?

I have the same problem. It is amended by turning off baseline grids, but baseline grids are necessary for longer texts. Is this something that will be fixed or optimized? I feel a bit apprehensive to start up a more extensive project in Publisher at this moment, which means that I need to revert to InDesign for now.