Dave Harris

Arial defines the code points for fi and ff ligatures, which Publisher will use if ligatures are enabled. Publisher exports the ligatures correctly, but some browsers don't understand them if fonts are not embedded. This is a bug in the browsers, not in Publisher. The "for web" preset currently does not embed common fonts, and Arial is one of these, so that is why you get the issue with Arial and not with Roboto. The only way I can see to workaround the browser bugs is to always embed fonts. We'll change the "for web" preset to do that in the next beta (which is a shame as it does make the PDFs bigger). So far as I know, subsetting the font does not cause a problem with these browsers. I'm not able to reproduce a problem with Font Manager > Locate stopping at ligatures. Can you attach a small sample document that illustrates it?

After moving the word to the next column, Publisher ought to re-justify the line, but currently it doesn't. This is a bug that will be fixed in the next beta/release.

Use View > Studio > Text Frame, and change the path using the controls at the top of the panel.

This is by design. You can increase indent by pressing Tab.

The bullet is generated from the paragraph formatting, so doesn't really exist to be selected. That's why it has no formatting of its own; only formatting it gets from the first character of the paragraph, or specified by a character style in the paragraph formatting itself. I believe the main difference with InDesign is that when InDesign takes the formatting from the first character, it ignore any formatting that comes from its character style. So if you change the first character to be red directly, you get a red bullet, but if you apply a character style that makes the first character red, then the bullet does not become red. This isn't possible with our implementation.

It's by design. There are two issues here. The first is that the bullet has to get its formatting from somewhere, and it gets it from the first character in the paragraph. You can then override this by specifying a character style with the bullet format. Other apps work in a similar way. In InDesign, for example, if you change the first character of a bullet paragraph to red, the bullet will become red too. Usually it's what you want. The second issue is whether when first character is selected, the bullet should be selected too. Currently in Affinity it is. That's partly to reflect the above formatting logic, and partly because when it wasn't highlighted, we found some users kept selecting until it was, which included the characters from the previous paragraph. However, this highlighting is different to other apps and seems to confuse some people, so we'll change it in a future release.

And Publisher!

Thanks for reporting this. It's supposed to split ligatures with justification the same way it does if you apply tracking manually, but currently it's broken. I don't think Times New Roman has the ffi ligature.

If I understand what you mean by "nested", the object nested inside the text should be clipped to the text. If the object disappeared, it was most likely clipped out.

Sometimes this is due to a bug rendering a specific style for the Show Samples option. If you have that enabled, a workaround may be to turn it off. (Might need to use Text > Text Styles > Detach and Delete All Styles first to get to where you can do that without crashing, then undo.) If that fixes it, could you upload an empty document with the text styles that shows the problem, so we can see what's causing it? I'm aware of it happening with Align to Spine, and also large right indents. The former should be fixed in the current beta, so it may be worth trying that, too.

However, we do support PDF/X-1a:2003. You may find your printer will accept that too.

Thanks.

I've not been able to reproduce this. For me it won't break at all after a non-breaking space. Can you attach a small document which shows the problem?

The spine alignment issue should be fixed in the current beta. This is a new bug that appears to be triggered by the huge right indent and Show Samples.

Link the text frames on the master pages. Otherwise Publisher doesn't know it's supposed to use both for the same story.

Yes, paragraph leading is in the Spacing section, near the top of the Paragraph panel. It's also in the text context toolbar. You can set it to a multiple of the font's recommended leading, or a fraction of the text point size, or an absolute number.

Your Heading 2 style has the list Text set to "\#.\#.". If you change it to "\1.\2.", it should do what you expect. \1 means the number of the list level 1, and \2 means the number of list level 2. The \# expands to the number of the current list level, so using that twice you get the same number twice each time. \# is useful for nested lists like: aa bb cc dd where the number of the current level is all you want, and it lets you increase the level (eg, by pressing <TAB> at the start of the line) without having to edit the list Text, so that's why it is the default.

Are you wrapping text around groups or embedded documents? That is known to be slow, and can be improved by given them a manual wrap outline.

Use Bullets and Numbering, and give the list a Name, and set Restart numbering to Manual Only.

The released Designer never had hyphenation. I don't think Designer beta did either, but if it did, it was an accident. Designer has gained some new text features from Publisher (eg, lists), and hasn't lost any.

In addition to the red eye that is used to hide or show overflow, if you have View > Show Text Flow ticked, stories with overflow will have two extra round red markers on every frame, when unselected. These markers disappear if there's no overflow, and turn into the triangular flow handles (which will also be red for overflow) when the frame is selected. We appreciate that a proper pre-flight check and UI is needed, but in the mean time it's easier to look for these red markers than it is for the red eye. (I forget when the overflow markers were added, but it was likely after this thread started so the early replies don't know about them.)

If I understand what you want, you can select the top two lines you want to change and use Leading override on the Character panel.

Do two things. First, change the Restart numbering rule from Any Non List to Below Current Level. The default first option restarts the numbering after any paragraph that isn't a list, which is convenient if you have blocks of consecutive numbered lists but isn't what you want for numbered headings. Then give the list a name like Heading. All lists with the same name use the same counters. Given the headings their own list name will give them their own counters separate to any other lists in the same story. All levels of a multi-level list should use the same name, so you shouldn't use the name of the style. So both H1 and H2 styles should set the list name to Heading, with H1 using Level: 1 and H2 using Level: 2, and the H2 Text set to include both \1 and \2. If the headings aren't all in the same linked story, then tick the Global box next to the Name too. This is useful for things like auto-numbered figure captions. I hope this helps.

There aren't buttons for indenting, but you can use Text > List > Increase Level. It has a default short-cut, and you can use <TAB> and <SHIFT>-<TAB> at the start of the line too.

The selection box is actually set to the larger of the cap height and the height of a lower case letter ell. Your example doesn't align because you are using a font with a tall ell. That explains what is happening. It's behaving as designed, although in this case the design isn't great.