
Jim_A
Members-
Content Count
58 -
Joined
-
Last visited
About Jim_A
-
Rank
Member
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
-
Jim_A started following Initial Words, [Fixed] docx import bug .305 and 'Overprint black' rewording suggestion
-
There are some bugs with the new Publisher .docx import feature: From a new blank document in macos Pages (version 7.1 (5683)) I used the default styles to make a simple document containing the Title, Subtitle and Body styles, then exported to .docx. On import into a Publisher textframe, the paragraphs are have 'Start: On Next Page' applied in the Flow Options, even though this wasn't part of the style in the original Pages document. (So on import, only the first paragraph appears, with the text overflow icon showing red. By option-shift clicking on the overflow icon, a number of new pages are created for each of the paragraphs in the document.) Also, the original font Helvetica Neue Bold has small caps and italics applied on import. Original Pages file and .docx export file attached. (Full specs of my system in sig.) docx-export-test.pages docx-export-test.docx
-
-
-
Not really a bug, but rewording might prevent some prepress headaches. When exporting a CMYK document using PDF/X, the option to 'overprint black' could be reworded to 'overprint black at 100%'. Black set to anything other than 100K knocks out, unless a global swatch with overprinting set is selected.
-
-
-
The only way I could find to do it was to type a tab character in a text frame, copy it, edit the style then paste it into the End characters field. Nothing shows in the field as it pastes as an invisible character. However, if you save the style changes, close, then Edit Style again and go back to the Initial Words section, the tab shows up as <TAB>. However, manually typing in <TAB> doesn't work, you have to paste in a tab character. Maybe there's an easier way.
- 1 reply
-
- end character
- tab
-
(and 1 more)
Tagged with:
-
Side by Side Views?
Jim_A replied to rpmichael's topic in Feedback for Affinity Publisher on Desktop
Looking forward to seeing that in the Mac version. It would be intuitive to drag a tab and have it float as a new window. The only way I can get an image to open in a separate window is to double click it in the Layers panel. Maybe there's another way? Once the image is open then View > New View gets a second window. The weird thing is that somehow I got two tabs (main page view and image view) to open by double clicking, but I can't reproduce it. -
Side by Side Views?
Jim_A replied to rpmichael's topic in Feedback for Affinity Publisher on Desktop
When you have multiple tabs open, go to Window > Separated Mode. In Separated Mode you can also use View > New View to see multiple windows at the same time. -
-
color swatch auto-names
Jim_A replied to thomaso's topic in Feedback for Affinity Publisher on Desktop
+1 for swatch names automatically updating when the colour values are changed. This is a useful feature for print production, especially when global colours are used. -
-
I need a clean preview
Jim_A replied to SigsCreations's topic in Feedback for Affinity Publisher on Desktop
No, they don't show on export. (Thankfully!) -
I need a clean preview
Jim_A replied to SigsCreations's topic in Feedback for Affinity Publisher on Desktop
The Preview mode still shows empty picture frames with a cross. Ideally, those would disappear. In contrast, white or transparent shapes created by the various shape tools are invisible when in either view mode, which makes them hard to find and select. (Finding them using the Layers palette is going to be difficult on a complex page.) -
+1 for Aloof. 'No change' is useful for character styles, where text attributes are shared with the paragraph style. However, with a paragraph style based on another paragraph style it's helpful to see the values. Otherwise you're working in the dark. For instance, set up a Body style for the main text, then create a Body First Para style (based on Body style) which has Drop Caps and Initial Words enabled. When you edit the Body First Para style, the values for the Drop Caps and Initial Words show as 'No change', even though they weren't enabled in the original Body style. You can get some information from the Style settings box at the bottom of the editor window, but some values (such as Initial Words Max word count) don't show. Best to keep 'No change' for character styles, as there it helps to identify which attributes have been overridden.
-
Bleed and margin border colors
Jim_A replied to Bo Lovenhjelm's topic in Feedback for Affinity Publisher on Desktop
+1 for different colours for guides, bleeds, margins, layers, text boxes, etc. -
- Find / Replace is broken at the moment (can't paste some invisible characters; can't replace with nothing; magnifying glass under Find is missing in Mac version, etc). I'm going to wait for a later beta release before I use it. - I think I had to manually add the soft return shortcut as shift-return by going to Preferences > Keyboard Shortcuts > Text (popup) > Insert > Line Break. (see screenshot) - Bulleted lists are best set up as a style. Create a new style, then select the Bullets and Numbering tab. The distance between the bullet and text can be altered using the Tabstop value. (see screenshot)
-
Story editor - mandatory
Jim_A replied to Jowday's topic in Feedback for Affinity Publisher on Desktop
+1 for Story Editor. It’s an extremely useful tool, especially, as Hank said, for working with overset text, identifying styles and invisible characters. The alternative is to link overset text to a temporary box on the pasteboard. This is cumbersome and impractical with longer documents. And it doesn’t provide a way to identify which styles have been applied. The story editor has also saved me much time and frustration in trying to track down rogue column break or page break characters in the middle of some imported text.