Jump to content


  • Content count

  • Joined

  • Last visited

Everything posted by Jim_A

  1. 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
  2. @Jamso You can also select an object behind another object in the layer stack by option-clicking with the Move tool.
  3. PDFs created by InDesign which contain bulleted lists display incorrectly when imported into Publisher. The InDesign CS5 bullet list was set as a paragraph style and used a specific glyph which had a character style applied. I tried exporting as PDFX-1(2001), PDFX-4(2008) and High Quality Print with the same results. In the screenshots below, the top one shows the original Indesign Document and the one below shows the exported PDF placed in Publisher.
  4. Jim_A

    Imported PDF bug .283

    On further investigation, this problem only seems to appear with certain fonts. So far, I have identified: Kozuka Gothic Pro Kozuka Gothic Pr6N Adobe Heiti Std Heiti TC Kozuka Mincho Pro I think many of these were installed with Adobe Creative Suite CS5. There may be others, but I haven't had time to check. ------ In addition, if the InDesign-exported PDF is opened in Preview and re-exported as a PDF, it appears fine in Publisher. (I see from other threads that PDF passthrough is not a simple task.) https://forum.affinity.serif.com/index.php?/topic/67957-why-cant-a-pdf-just-be-placed-without-option-to-edit/&
  5. Jim_A

    Imported PDF bug .283

    I'm having trouble reproducing it myself. It could be a font problem with the original InDesign document which used Kozuka Gothic Pro. If I change the font, the problem disappears. My system is showing Kozuka Gothic Pr6N in addition to Kozuka Gothic Pro, so this could be a problem with the fonts on this machine. Could someone try importing the attached PDF into a Publisher document to see if it displays double bullets (as it does on my system). If I open the PDF in a PDF viewer, it appears fine. list-export-kozuka-pro.pdf
  6. Jim_A

    Imported PDF bug .283

    On further testing, it seems to depend on the Text After character used in the InDesign style. A space doesn't seem to cause problems, but tabs, em space, en space all cause formatting issues.
  7. 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.
  8. See video. A number of studio panels which aren't shown by default (for instance Table, Table Formats, Hyperlinks, Constraints) appear as duplicated tabs when selected from the Studio menu. Dragging into separate panels results in blank or unresponsive panels. [AfPub] table-panel-bug.mov
  9. Those symbols are rather cryptic but they are the correct symbols for Page Up and Page Down (see here for other macOS symbols). The symbol on my keyboard is just a plain arrow which doesn't help, but that's an Apple decision. Compact keyboards use fn-Up Arrow. The only glitch in Publisher is the missing glyph symbol in the Keyboard Shortcuts preferences. If I type Command-Page Up into the preferences, the symbol appears as expected. Not sure why it's not showing by default.
  10. Since the internal discussion on styles is ongoing, can I cheekily point you to this thread where there is a discussion about changes to the way that style information is displayed. https://forum.affinity.serif.com/index.php?/topic/70947-initial-words-sticking-with-first-font-applied/
  11. 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.
  12. Page Up and Page Down keys work here as well, although there's a different symbol on my extended keyboard which just shows a plain arrow. Looking at the Keyboard Shortcuts preferences, there seems to be some trouble displaying that glyph, although it appears ok in the Document menu.
  13. Jim_A

    APublisher: Close All ???

    Apple replaced Command-D with Command-delete for some applications, which is not as convenient to type.
  14. Jim_A

    APublisher: Close All ???

    On macOS there is also the keyboard shortcut of Command-D for Don't Save, which enables you to quickly review and close without saving (if desired) a stack of open documents (but only if you quit the program, as walt.farrell said above).
  15. That's useful, thanks. And it does work for the hyperlink styling. The option for new text frames to automatically have default styling would still be useful (or even desirable as the default option). There is a glitch with the Revert defaults button: After clicking the button, the style selected in the Text Styles list doesn't change to No Style until you start typing.
  16. Isn't this a result of the default behaviour of 'sticky' styles? If you apply styles to text and then draw a new text box, the style remains selected. I can see some situations where sticky styles would be a convenient time saver, but I find it more of a hindrance than a help as I need to manually check that no unwanted styles are selected when making new text frames. This is especially inconvenient when the document has many styles, as you have to scroll down to the bottom of the list to check that no unwanted character styles are being applied. Perhaps a preference option for 'New text frames have default styling' would solve this.
  17. Jim_A

    Text Frame inset togglers V238

    Confirmed. Also In the Text Frame panel, it's difficult to highlight the inset value. Sometimes clicking or dragging the cursor selects the value, sometimes not. (I have Font UI Size set to large in preferences, but the same occurs with small font size.)
  18. 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.
  19. 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.
  20. Shapes with a transparent background don't show their bounding box in preview mode when not selected. The only way to detect them is to click exactly on the edge of the bounding box (by guesswork) or to drag a marquee over the entire shape (partial selection doesn't work). I know they are shown in the Layers panel, but finding the right shape in a complex page would be laborious. A workaround I've found for the moment is to Select All to show all the bounding boxes, but some kind of visible boundary (as with empty picture frames) would be useful.
  21. An example might be a catalogue template which had a number of repeating graphical elements which might not always be needed. To remove selected ones (but not remove them from the template), simply make them invisible. You could hide them in the Layers panel (right-click, Find in Layers Panel, uncheck the box), but it would be laborious to find the right ones in a long list of identical elements when you're trying to show them again. Also, finding stray objects, accidentally clicking the no-fill no stroke icon, creating shapes for text-wraps. If it's on the page, it's useful to know it's there.
  22. Yes, sorry, I meant the opposite of Preview mode, whatever that's called. Edit mode? And, yes, if the bounding boxes are eventually implemented, they need to disappear in Preview mode.
  23. Thanks. That setting helps. It's in Miscellaneous, if anyone's looking for it.
  24. I've also noticed inconsistent behaviour when clicking in the page-range field: Most of the time the displayed range will disappear to be replaced with a blank field and a flashing cursor (as expected). But occasionally the numbers themselves become selected and highlighted. However, I can't reproduce this reliably. It may be related to the scrollwheel problem mentioned above. Edit: Clicking in the blank field and then scrolling will scroll the document and highlight the page range. Further edit: I also had a crash when entering a number on the keyboard number pad when the page-range was highlighted, but I can't reproduce this.
  25. I've noticed if you hover the cursor over the page-range field of the Pages panel, the scroll wheel on the mouse will quickly scroll through the pages of the document. I'm using a Magic Mouse and sometimes the act of clicking in the page-range field causes a quick page scroll before I've clicked the mouse, leading to an unexpected scroll to a different part of the document. I wonder if something similar is happening to cause the crashes: too many conflicting inputs being processed at once. Is anyone else using a Magic Mouse? [This was tested on a blank 50 page document. AfPub]