walt.farrell

Yes, there's a reason that the Project Gutenberg .txt files have paragraph breaks after every line. And yes, you should be able to clean that up to reflow the paragraphs using Publisher. However, it can be tricky, and for that particular copy of A Christmas Carol it's made harder by the Table of Contents not being formatted quite correctly. In addition to each line of the TOC ending with a paragraph break, each should also start with a space. That is, rather than the first line of the TOC reading it should read where "x" is a single space. The space at the beginning of the line indicates that the line should not be rewrapped (reflowed) with the prior line. The approximate general approach, then, using Find/Replace in Publisher would be this: Handle the title page separately. For the rest, perform all of the following Search for all ¶ followed by a space, and turn them into something unique, such as %%nowrap%% Search for all ¶¶¶¶Text, delete the ¶¶¶¶, and assign a Heading 2 paragraph style. (I am having a problem with this step, so it needs some kind of modification. When I try to assign a paragraph style only [No Style] is available.) Search for all ¶¶ and turn them into something unique, such as %%break%% Search for all ¶ and replace with a single space Search for all %%break%% and turn them into a ¶ Search for all %%nowrap%% and turn them into a ¶ (Note that one doesn't need to distinguish the cases in step 2 and 4, but if something goes wrong it helps in diagnosing and fixing the issue, so I do them separately that way.)

Please remember that this is only release 1 of the product. If Serif had waited until all the "required" functions (that is, functions mentioned as required by someone) were present, we would not have Publisher at all yet. As it is, we have something that works for books that do not need cross-references and do not need footnotes. And there are real books that don't need them. Even if your books need those functions, someone else's might not. But yes, if it works for you, use it. If not, don't. No one is forcing you to use Publisher if your project is too complex for it in its current state of development.

I know of two possible scenarios. Both start with right-clicking on the Master Page layer on the page and choosing Edit Detached. Then, before clicking Finish or navigating away from the page: Drag another document layer into the Master Page layer. or With a layer in the Master Page layer selected, add a new object on the document page. The new object will be created in the Master Page layer.

There was at least one macro enhancement in 1.7.1, though. At the bottom of the Library anel we now have scaling and alignment options: They are explained in the Help for the Library panel.

Even something like D:\Affinity\Designer D:\Affinity\Photo would probably work. Or possibly D:\Designer D:\Photo But not simply D:\

I don't think an option like that exists at this time. However, if it helps, you can quadruple-click to select a paragraph. Double-click will select a word, triple-click will select the line, and quadruple-click will select the paragraph.

Did you install Designer into the default location suggested by the installer, or did you change the location? For example, Designer, by default, should be in C:\Program Files\Affinity\Designer Photo by default, should be in C:\Program Files\Affinity\Photo If you installed Designer into the same directory you installed Photo into, you would break Photo.

If you press and hold the Windows key, then type R, you'll get a Run box. In that box, type %temp%\AffinitySetup and press OK. You'll get a FIle Explorer window opened to the directory that contains the logs of your setup attempts. Find the directory with the most recent date/time, and in it you'll find two files, Setup.log and SetupUI.log with additional information. You can browse them with Notepad or another text editor, and usually searching for the word Error will get you to the location with more detailed information.

If the problem is with filler text, you can also change a specific chunk of filler to real text; just right-click on it and choose Expand Field from the context menu.

Thanks for the files. I do not see any sign of raster data in your TC.svg file (the one with text converted to paths); it all looks vector to me. But I don't have much SVG experience yet, so I'm going to hope that someone who knows more than I can help further.

If only the Context Toolbar is missing, then View > Show Context Toolbar.

When you export a .svg file it should all be vector unless you've done something (applied an effect, for example) that requires rasterization. So, it might be helpful for you to provide a sample .afdesign file and the exported .svg file that don't work, so we can look at them and see what you're doing. You might check the export dialog, though, and see if you get this message:

You're welcome.

Those old 1.6 styles were deleted by Serif in 1.7 for some reason (along with some old 1.6 brushes). One of the Serif staff made them available, here: 1.6 afstyles

Just so you know, in case it's important for something else someday:

Interesting. I wouldn't have thought about that. Probably Publisher should ignore overflow when the text frame is outside the pages, but it doesn't:

If it asks to "uninstall or repair" that usually means you're running the installer for the same version you already have installed. I don't think you've said what application you're trying to install, nor where you purchased it, so I'm not sure what to suggest that you try next.

If you search the forum for Linux or for the words linux wine and then choose the option linux AND wine near the top of the search results, you will find various forum topics that discuss that. I think the answer is no, but I don't follow them closely.

Not, but only because the same sequence of actions as you took in Designer, when done in Publisher, keeps the path fill and stroke. It is the inconsistency in identical actions that suggests to me there's a bug in one of them. Thanks for the explanation of what you did. There's still an oddity to be explained. If I use the Artistic Text tool in Design er and make the letter A, then convert it to Curvers, then convert that to a Text Path, and then type a phrase, I get this: In the Layers panel this shows up as: In your file, the Layers panel shows: So (a) why does it appear to be normal artistic text rather than text on a path, and (b) why is the phrase "Neither Affinity Designer nor Affinity Publisher is Broken" incomplete on the Layer panel?

If the image is only a single layer, perhaps Rasterize & Trim... would work? (Or Document > Flatten.)

That certainly duplicates R C-R's result visually, but what do you really have there, and what steps did you take to get it? (The most puzzling aspect of R C-R's file, to me, is that in the Layers panel it seems to have just an Artistic text layer, with only part of the text on the path. And the large A isn't present in the Layers panel in any way that I can see.)

I didn't even think of that possibility, or I'd have tried it and (probably) spotted the problem

I get identical results in both applications, matching the 3rd image you provided. Perhaps there's something else in the Publisher document that's causing a problem. Can you share a .afpub file that shows it?

That's a strange file, and you'll need to explain how you did that before you will convince me. (Especially given that my prior screenshots demonstrate that an identical sequence of actions in Publisher and Designer give different results.)

Yes, either SVG or PDF will maintain editable text, at least when you export from Photo and import back into Photo. Probably they will for importing into Photoshop, too. But this is not really a good option for you to use, as you may find other things that will not transfer across 100% the same. You should both use the same application, and given that the Affinity applications are inexpensive, it would be better to have your boss buy a copy of the Affinity application you're using, in my opinion.