Chris Christner

The workaround on a Mac is to select the template files that have custom extensions and do a get info, then click the "Stationary Pad" button. Opening the docs will create a new file with all the content of the template but the template can't be overwritten. Don't know if Windows has a similar setting.

And that works really well! Thanks for the help.

I understand that each Affinity app can save a template file with a .aftemplate extension, and that the templates can be opened in any of the suite applications. But to avoid confusion, why not give each app a unique template extension so it'll open in the correct application? Then if you want to open a Publisher template in Designer, you can simply open it from inside Designer.

It ain't pretty, but it'll work. Thanks again!

I'm betting you'll have a workaround as usual. Appreciate the help!

The problems I have with that are: there's no way to set the B&N tabstop by eye (which is how I like to work) and I don't see why B&N can't just work with the text ruler tabstop. Where's the advantage to it being a specific setting? As a workaround, the tabstop could be set by eye or clicking on it could bring up a field for entering the precise position. Anyway, I thought it was a bug, but it turns out they like it that way. So I'll adapt.

Because both settings control where the text is indented. Hence they should be the same.

As shown in the attached image, I created a bullet style and adjusted the tab stop to where I was satisfied. But the first line of text kept indenting to what I later learned was the tabstop setting in the Bullets and Numbering panel of Paragraph. Am I missing something subtle or is it a bug? Because it seems like the B&N tabstop should be the same as what I set with the ruler tabstop.

Update: Following advice from this topic (Thanks all!), I requested a refund from Apple, and received it today.

As I recall, webp exporting was tentatively scheduled for 1.9. I didn't see it in the beta, so is it going to be in 1.10?

Actually, I haven't contacted the App store because SFurniss gave me the affinityreturns@serif.com address. I emailed it and got an auto-response. Are you saying they're not likely to refund the purchase and that I have to contact the App store?

I didn't know that's how it works. Thanks for the explanation. Part of the problem is that the App store is so flaky. You download software and pay for the pro version. Next time you download it you get the basic version, so you have to click on the buy button, at which point it tells you that you've paid for the pro version and downloads that. That's what threw me, because I expected the store to download the version I'd already bought, not realizing I must have bought it at Serif's store. Anyway, they're giving me a refund, so all's well that ends better.

I'll do that, thanks!

Hmmm. Why would that be a separate purchase? I mean, if I buy it from the Serif Store or the App Store, it's all registered to me, so it shouldn't matter. I hope they'll refund the money.

I already have a license for Publisher, but after doing a clean install of MacOS High Sierra, I was charged for Publisher (not Designer or Photo). Please fix this. Thanks, Chris

I need to get glasses, because when you suggested this earlier, I missed the S in the P and T panel and tried clicking on the S in Typography instead, which didn't work. Now that I've found the S it does exactly what I need.

Thanks, that's the workaround I'm using too. I created a character style with the font, size, and baseline I needed for superscripting. Of course it's only good for that font and size, but it works.

I understand their reasoning, but it's flawed, otherwise the top apps in the industry wouldn't be using faux characters to annoy their users' customers. For purists with lots of time on their hands, I'm sure they admire Affinity's stance on this. Those of us with deadlines to meet...not so much.

Well, thanks again. That does seem like an incredible blindspot in Publisher, especially since the other major apps (InDesign, Quark, Word, etc.) handle this sort of formatting without making users break out manuals and trusting to luck that the font they've been using can do subscripting. I trust Affinity has addressing this feature on a roadmap so eventually it'll work as expected.

Thanks again for the assist! Question, though: How can you tell whether an OpenType font includes the sub/superscript characters? Hopefully not by trial and error.

...to the mouse right-click pop-up menu. Thanks!

Superscripting doesn't work for capital letters or cap-height letters such as "l" and "h" (see video). Screen Recording 2021-01-07 at 4.02.40 PM.mov

I figured out a workaround: Delete a few characters near where the L SEP or P SEP characters appear; save the change; then retype the deleted text. It works! Apparently deleting those characters also gets the unicode characters too. Incredibly time consuming, but at least I can check Microsoft Edge to verify that the text is clean. Please fix this problem ASAP!

I'm extracting text from a datasheet created in Publisher for use as an online datasheet created in CS6 Dreamweaver. I've been going crazy trying to figure out how to avoid having text copied from Publisher randomly bringing along P SEP and L SEP unicode characters with it (see attached). The problem occurs in the previous and beta versions of Publisher. I've tried pasting the copied text as text only into Dreamweaver, where the characters don't appear (even in code view!), BUT when I look at it in Microsoft Edge, they pop up. Oh, and that's another problem: not all browsers display

Chiming in on this. Publisher is including unicode L SEP and P SEP characters in copied text that remain in the text (invisibly of course!) when pasted into an HTML editor using the Paste and Match Style command. And then they pop up randomly when viewed in browsers. Right now it's Microsoft Edge where they show up.