walt.farrell

Just a comment: From the text that you're replacing, it appears that you have imported some text into Publisher that was not encoded as UTF-8. That would give you those strange character combinations. I'm curious where the text came from, and how you got it into Publisher. It may be a good idea to look at your workflow and convert the text before importing it, so it goes into Publisher properly. But without knowing what you did originally we can't really say for sure. (I have commented in another topic that I believe Publisher has some flaws in how it determines character encoding when importing text.)

You may be looking there. But I believe you'll find that Serif intends Publisher for books (and eventually ebooks). And they have been pretty clear that they're not interested (at least at this point) in apps that will do web design, video editing, and several other kinds of design that are common requests of them here in the forums. So it seems reasonable to assume that they're also not looking at applications that will help design mobile apps. (I cannot, of course, speak for Serif, but I have read a number of responses they've made which have informed my beliefs about what they're looking at.)

Publisher is not for designing apps. It is for books and other printed materials. Loosely, I suppose that it is possible that one one might want to embed an audio file within an epub, when Publisher supports them, but that is about the only potential connection for audio that I see with any of the Affinity applications.

I'm curious to learn how audio files are important in the Affinity Photo or Designer workflows.

It may be relevant that the PNG image format does not support CMYK. But I'm not precisely sure how that should affect your file.

I can't really answer that for a PSD file, Tom. But I have noticed that Publisher (and I suspect the other two applications) have some fundamental differences in the way they treat placed/embedded files, handling pure image files differently from the way they handle non-image files.

Thanks, Imre. Your problem seems to be that Publisher is expecting a file encoded as UTF-8 but your file is encoded as ANSI. Here's a version of your file converted to a UTF-8 encoding, and it imports correctly into Publisher for me, at least for all the characters I checked. This is probably a bug in Publisher's detection of file encoding. I've had some experience with that, and it can be tricky to figure out a good algorithm until you've seen this kind of problem once Hungarian_test-utf8.txt

I suspect that yours isn't an image (JPEG, TIFF, PNG) but a document (PDF, PSD, EPS, SVG).

What happens when you try, and what OS are you using?

Backing up through the History panel you should be able to get to a point before you converted it to curves, I think. Of course, you'll lose anything done after that.

The best guess is that it will be comparable to the price for Affinity Designer and Photo.

You get automatic page numbering by putting a page number field on a Master Page and applying that Master to your pages (or specifying the Master when creating new pages).

Do you have something there for Horizontal Scale? I don't see that. (In fact, I don't think I see anything labeled "Horizontal Scale" anywhere. Where is it in general?)

Thanks. So that probably explains what's happening. When you let Publisher create the new frame and flow the text it uses the same settings as the current text frame (which includes the increased font size). However, when you manually draw a new text frame Publisher uses the default (i.e., last) font size value set for the tool, which is the original text size before the last frame was adjusted. Then when you link them and flow the overflow text into the new box it has that original text size.

Interesting. I see the same thing in the Designer preferences on Windows. Delete is missing. Perhaps a bug? Or something that hasn't made it into Windows yet for Photo or Designer? (It's present in Publisher, so I suppose it might be present in the other applications on Windows when they reach 1.7)

Might it be relevant where duncang bought it from? If from the Microsoft Store, for example, I think it will still have the old installer (the .123 version, not .135).

But how did you create that second frame, and how did you flow the text? If I just shift-click on the link icon, letting Publisher create the new frame and flow the text, then the text size is correct.

That's provided in the Navigator panel which, by default, I think, is available in the lower right studio.

I think we need to know the exact actions, and sequence of actions, that you took. You did something to resize the first frame (and the text), and then you did something to create the second frame, and you did something to get some of the text from the first frame into the second. But what order did you do things, and what did you do to accomplish each? I have tried to duplicate it, and my text ended up the same size in both frames. Also, are you on Windows or Mac?

Perhaps you meant Layer menu? At least that's where I find the 3 Convert to ... entries.

Someone who knows/uses the iPad version will have to tell you how to find the information; sorry.

There's a topic over in the Publisher Discussions & Suggestions topic that mentioned that if one clicks on a document page that Publisher doesn't automatically scroll the Pages panel to show that page. That might well be a feature request/improvement, but while investigating it I may have found something that's a bug. My post is here, including some screen shots. Basically, the Pages panel seems to show as selected whichever document page has 50% or more showing on the screen. The problem that I show is that when zoomed out so that two pages are partially showing on the screen, one of them may be shown as "selected" (highlighted, active, whatever that grey rectangle in the Pages panel means) while I'm actually working on the other page that's visible on the display. That's confusing enough that it feels like a bug to me, so I thought I'd raise that issue here in the Bugs forum to make it more visible to the QA team.

RGB/8 is shorthand for RGB (8 bits per pixel), which is one of the standard color formats for images. Edit: Note that I do not use an iPad, so I can only provide screenshots from Windows. Sorry. If you have your image open in Affinity Photo, and have the View Tool (Hand) selected, you'll see your document's color format in the context bar. For example, this screenshot is from a document in the RGBA/16 format (RGB with 16 bits per pixel): You can also see your color format via Document > Color Format. Here's one where the document is RGB/8: Question: what color format is your document?

Thanks, but I was particularly interested in the original of the .txt file you imported, as you said the error is with the import.

I agree. It would be better if the page you clicked on (or the page you were working on) were the one highlighted in the Pages panel. In fact, this seems a bit buggy. In the attached screenshot, I selected page 4 and put text into a Text Frame there. You can see Page 4 selected in the Pages panel. Then I scrolled up in the main part of the window, so that part of Page 3 was visible and available to work on. Note that I scrolled up so less than ~ 50% of Page 3 was visible. If I scrolled further it would become the selected page in the Pages panel. You can see that Page 4 is still selected. Then I chose the Artistic Text tool and created a word on Page 3, while Page 4 is the "selected" page. I would have thought that that the page whose content I'm changing should have been the active/selected page.