Mark Oehlschlager
-
Posts
634 -
Joined
-
Last visited
Posts posted by Mark Oehlschlager
-
-
I'm setting up a Publisher document for a book that is structured in Parts and Chapters. The interior design is such that the part titles appear as running heads on the verso pages, and the chapter titles appear as running heads on the recto pages.
The question is this: what is the best way to set this up with master pages in Publisher?
One solution I have considered is to create separate master page spreads for each book Part, where the part title is set manually on the master verso page, and the chapter title is set as a dynamic section field on the master recto page. In that case, I would use the Section Manager to create sections for each chapter in the book, supplying the chapter title to the Section Name field in the Section Manager.
The above solution can be made to work, but is there a way to create a user defined field for the Part title? If so, I wouldn't have to create separate master page spreads for each book Part. I could just insert my custom Part Title field on the verso page of a single master page spread.
-
I would like to bump this topic up.
Presently laying out a document in Publisher, where the color of the page ground is very close in color and value to the default cyan color of the guidelines. As a result, it's nearly impossible to see the guides.
It would be good if one could change the color of guides to contrast with the content of any document.
-
Running Publisher 1.8.6 on Mac OS High Sierra 10.13.6, and have discovered a UI problem with the "Insert Index Mark" dialogue box.
The "Move to Parent" button on the right is clipped. (See attachment.)
-
I've got Publisher 1.8.6 installed on my iMac running High Sierra 10.13.6, and I've found that there is a UI glitch in the TOC panel.
The column heading over the checkboxes for page number occurrences of specific paragraph styles is severely cropped/truncated and cannot be read. (See attached image.)
-
I've read through the Help File page on creating and styling a TOC in Publisher. I've also watched the video tutorial. Still, I find the information to be incomplete.
Please revisit the Help Files and the video tutorials to clarify how one is to make use of and manage the special TOC paragraph and character styles (e.g., how one goes about applying one style to a chapter title, and another to the corresponding page number), and to demonstrate how one can build TOC's for publications that do have more than one TOC.
It's very frustrating to receive just half of the information required to understand the feature completely.
-
Thank you for that link. That's definitely a start.
Even this video doesn't explain everything, and the presenter seems a bit unsure about what everything does.
- Through trial and error, I believe I've discovered that the "Tabstop" field in the B&N sub-panel controls any tab inserted between a bullet or number and the following text. This is unrelated to the settings in the Tab Spaces and the Spacing sub panels.
- I still have no idea what the left-, center-, and right-alignment buttons control.
- Proper use of the "Level" field needs to be demonstrated. It's not clear.
- A fuller explanation for the "Restart numbering" needs to be presented. It's not clear.
- The "Restart numbering now" check box needs an explanation.
- The "Name" field and the "Global" check box need an explanation. It's not clear what these are for, nor how to use them.
- Through trial and error, I discovered that the "Style" popup menu is meant to apply Character Styles to the numbers itemizing a numbered list.
- I still don't understand how one would go about setting up coordinated/linked paragraph styles for multi-level lists.
A fuller explanation of all of this in either the Help files or subsequent tutorial videos is needed.
-
I have read through both help file pages on Bullets and Numbering very carefully, and I must say that the information is incomplete and unclear.
Please review these Help file pages from the perspective of a new user and rewrite the instructions with illustrations for absolute clarity.
It would also be worthwhile to add a tutorial video demonstrating how to use and configure custom Bullets and Numbering styles and settings.
-
-
FYI, the zoom behaviors of the Zoom and View tools remain broken in 1.8.6 across the suite of apps.
- Double clicking Zoom tool does zoom documents to 100%, but ...
- Double clicking the View tool does not zoom documents to "Fit".
- Zoom levels are not synchronized between the Zoom tool, View tool, and the Zoom pop-up menu and slider in the context toolbar.
Giving this thread a "bump" as you had requested before.
-
Maybe, but for reasons beyond the control of Serif. A lot of users feel trapped and fearful of moving on. It's a psychological trap.
-
The network effect advantages that Adobe enjoys is a powerful enemy to challengers. In spite of all the resentment felt toward Adobe, for the subscription model and other reasons, fear of dropping out of the professional network as a result of dropping Adobe has end users behaving like a bunch of heroin addicts.
-
I would like to request an update to the "New Master Page" and "Spread Properties" dialogue box to include a "Based on ..." attribute so that the parent-child relationship of child master pages can be more explicitly defined and redefined in these dialogue boxes.
Presently, one right-clicks on a child master to select "Apply Master ..." to configure a parent-child relationship. And the only indication of this linkage occurs if one hovers the cursor over the child master to reveal a tool-tip message.
It would be better to add a "Based on ..." attribute field to the "New Master Page" and "Spread Properties" dialogue box, just as one can set up parent-child paragraph styles.
Thank you for your consideration.
-
Two items:
- Drawing items at borders and corners should wrap to opposite side.
- Would be nice if we could build pattern tiles with vector elements.
- Patrick Connor and IPv6
-
2
-
Whenever I attempt to use the Liquify Live Filter, Photo crashes.
Photo 1.9.0.203
iMac 27" Late 2012; 2.9 GHz Core i5; 16 GB memory
Mac OS 10.13.6 High Sierra
-
Interesting to see the "Save as Package" function appear in Designer. I would normally associate such a feature with Publisher, but I suppose it also makes some sense for it to be included with Designer, as the entire suite of Affinity apps are virtually unified.
Should we expect this function to roll out in updates to Publisher and Photo?
- wtrmlnjuc and Takudzwa Nyoni
-
2
-
The download here is for a Windows .exe file.
Did you mistakenly post an update to the Mac update page, or did you mistakenly link to an .exe file instead of a .dmg file?
-
You mentioned your interest in Adobe Muse before they terminated it. You might be interested in a website building tool for the Mac called Sparkle. It's a code free, visual, website building tool. Produces responsive, fixed-width sites. Here are relevant links:
-
2 hours ago, dannyg9 said:
I also keep an old version of Adobe CS 5.5 around for one main reason: Everything I did using InDesign is part of my archive. I can convert those files to IDML and open them in Publisher.
This reminds me of yet another issue that has driven interest in the Affinity Suite.
On the Mac, after High Sierra 10.13.6, Apple's Mac OS, has gone entirely to a 64 bit architecture. Older 32 bit applications are no longer compatible with the latest OS. This has forced Mac users who've been clinging on to their perpetual license versions of Adobe CS6 to desperately seek out 64 bit alternatives to the subscription only Adobe CC. I gather that you are on Windows, but I assume the same issues are threatening to make older versions of Adobe CS obsolete.
I'm still running Mac OS High Sierra 10.13.6 precisely because I don't want to break my licensed copies of Adobe CS6. In the meantime, I've acquired the Affinity Suite and have become familiar with the tools as part of a larger strategy for surviving the transition to the 64 bit only OS environment.
Ultimately, sooner rather than later, I will be forced to replace my workstations and accept the forced migration to all 64 bit app architecture. At that point I will probably be forced to subscribe to Adobe CC simply because of the demands and pressures of the network effect that enforce the exchange of native Adobe files among clients and colleagues. But I'm happy to have the Affinity Suite and its fixed perpetual license fee as an alternative.
-
7 hours ago, AlejandroJ said:
Nevertheless, as somebody said, a Ferrari might be a nice car, but I have a Nissan, and I am very happy with it, and if in some future I decide to change it for a different car, it won’t be for a Ferrari
The problem for Serif and their customers, however, is that they are confronting the unique problem of the network effect, a problem that mostly tyrannizes the computer software industry.
The fact that your neighbor chooses to buy a Ferrari puts no real pressure on you to also buy a Ferrari, or to prevent you from selling your Ferrari and switching to another model of car. BUT, consider the problem of Facebook, or Twitter, for example. One could elect to avoid or drop Facebook, or Twitter, but 90% of the rest of the world including one's friends and family members are using those channels to communicate and share. The large network of captured users reinforces the dominance and monopoly-like position of Facebook and Twitter.
Adobe benefits from a similar network effect insofar as other professional creatives and corporate clients expect and demand the exchange of native Adobe files, not just for final deliverables, but also for collaborative work in development.
That's a bloody tough nut to crack.
-
It's very tough to knock off an incumbent in a space where network effects create virtual monopolies. Adobe is the 800 pound gorilla in that regard. Regarded as the industry standard, where it's assumed that everyone will be exchanging files in native Adobe file formats, and dependent upon proprietary effects and features.
I think it's pretty clear that Serif are targeting small professional graphic design firms, who are unhappy with and uncomfortable with Adobe's subscription model. Large agencies and corporate in-house teams are not really troubled by the subscription based licenses.
For small creative firms, the three biggest worries about Adobe's subscription model are a) the never ending expense of renting one's tools; b) the risk of seeing the rental cost of the tools arbitrarily and dramatically increased; and c) the idea that if one were to stop paying the rental price for the tools, that one would lose access to one's own work product.
The single most powerful aspect of the Affinity Suite value proposition is the availability of professional alternatives to AI, PSD, and INDD for a fixed, perpetual license fee. That's augmented by the availability of those tools on the iPad as well.
The biggest worries for Affinity users is whether they can build a closed workflow independent of having to exchange native Adobe files with clients and collaborators. Helping Serif customers overcome or mitigate the problem of workflows that demand the exchange of Adobe file formats is a major strategic challenge.
-
The Affinity Suite is astonishingly good for a 1.8 version, and does most of what the Adobe trio (Illustrator, Photoshop, InDesign) does for graphic designers.
Thus far, the opportunity that Serif have been able to exploit is the distasteful subscription policy imposed by Adobe, and the fact that Adobe is rather late in coming to iPad (though Adobe now has versions of Photoshop and Illustrator for iPad).
If it weren't for the subscription only business model from Adobe, Serif wouldn't be in business. The Adobe Suite is more polished and mature, and is more extensive. It also has the advantage of being an "industry standard" and benefiting from a kind of network effect.
Serif need to maintain feature parity with AI, PSD, and INDD, or (even better) exceed the features of AI, PSD, and INDD, and maintain an attractive one-time perpetual license fee.
If either Adobe were to offer their suite for a fixed fee, or Serif were to convert to a subscription model, Adobe would win hands down.
Still rooting for Serif and the Affinity Suite, but they are really facing an uphill battle.
- firstdefence, AITCH and Krustysimplex
-
3
-
For some reason, you have applied a 12pt baseline shift to several paragraphs on pages 30 and 31. That's what is causing your problem.
-
What you're doing in Photoshop is clipping the orange square to the Patreon symbol.
In Affinity Photo, you would place your PNG Patreon logo with transparent background, then draw your orange square shape on a layer above, then drag that orange shape layer under the layer label for the Patreon logo to make the orange layer a "child layer" of the logo layer.
-
You may want to select a font with Small Capitals that you can raise with a baseline offset. Small Capitals are designed to match the optical weight of the complementary capitals and lowercase letters from the same font set at the same point size.
The problem with scaling the "M" up or "EDITATIONS" down is that you get obvious mismatched stroke weights.
The example below is set in Adobe Caslon Pro, using small capitals.
- Fixx and sfriedberg
-
2
UI Error in "Insert Index Mark" Dialogue Box (Publisher 1.8.6)
in V1 Bugs found on macOS
Posted
@Gabe
Okay. Let's just say that it appears clipped, as most buttons are minimally square if not rectangular like the "OK" button.
Thanks.