Jump to content

Jim_A

Members
  • Content count

    58
  • Joined

  • Last visited


Reputation Activity

  1. Like
    Jim_A got a reaction from Jeremy Bohn in 'Overprint black' rewording suggestion   
    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.
     



     
  2. Like
    Jim_A got a reaction from Jeremy Bohn in 'Overprint black' rewording suggestion   
    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.
     



     
  3. Thanks
    Jim_A reacted to JFisher in Studio panels redraw bugs   
    Hi Jim_A,

    Thanks for your report, this has been fixed in the latest build. (1.7.0.257)
  4. Thanks
    Jim_A reacted to Old Bruce in Studio panels redraw bugs   
    I believe they are aware of this problem, but more reports are better than none.
  5. Like
    Jim_A reacted to A_B_C in Separating Paragraph and Character Styles   
    I have to concur with what was said in this thread. With lots of character and paragraph styles present in a document, the panel simply becomes confusing, and the suggestions made by Dave are only kind of patches on a more fundamental issue. There are already many good ideas articulated in this thread, if splitting the panels is not an alternative (which I would prefer). Please consider improving workflow and ergonomics here. I know that Publisher is currently not aimed at creating complex documents, but I don’t believe the current implementation has the scalability that will be required later in the development process. 
  6. Like
    Jim_A reacted to evtonic3 in Separating Paragraph and Character Styles   
    I was hoping I could separate them like this.
     

  7. Like
    Jim_A got a reaction from Wosven in Usability concern with new hyperlink feature and text frame default style   
    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.
  8. Like
    Jim_A got a reaction from Wosven in Usability concern with new hyperlink feature and text frame default style   
    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.
  9. Like
    Jim_A reacted to carl123 in APublisher: Close All ???   
    Close all should close all files that have not been changed
    Close all should prompt to save (or not) any file that has been changed
    Close all should prompt to save any unnamed file that has been created within that session
    The application should remain open after close all has completed
  10. Like
    Jim_A got a reaction from Alfred in Shape bounding box not visible   
    Thanks. That setting helps.
    It's in Miscellaneous, if anyone's looking for it.
  11. Thanks
    Jim_A got a reaction from thomaso in color swatch auto-names   
    +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. 
  12. Like
    Jim_A got a reaction from walt.farrell in I need a clean preview   
    No, they don't show on export. (Thankfully!)
  13. Like
    Jim_A got a reaction from Old Bruce in Crash when merging windows in Separated Mode   
    In Separated Mode, dragging one open document on to another to merge them into one window causes crash.
    Also reported in another thread:
     
    As a side note, when in the default view (not separated) with multiple documents open, the Window Menu only displays the front document at the bottom of the list. Shouldn't it display all open documents?
    [macos AfP beta 1.7.0.145]
  14. Like
    Jim_A got a reaction from ffca in Initial Words Sticking with first Font applied   
    If text is selected which has paragraph style overrides, I agree. 
    If no text is selected, it should default to no styling. And ideally, all the character style formatting fields should be blank, not 'No change'. (No change from what? The default styling? The applied paragraph style?)
  15. Like
    Jim_A got a reaction from A_B_C in Apply Styles – Options behave strangely   
    I agree with Wosven: being able to apply paragraph styles to individual characters is confusing.
    Paragraph styles for paragraphs. (Whole paragraphs.)
    Character styles for characters. 
    It is confusing to be able to apply more than one paragraph style to a paragraph, especially as the order in which they are applied determines which elements of the style appear. 
    For instance, try setting a paragraph to Body style, select all, then 'Apply "Line Below" to Characters'. Now try it in reverse.
    If Body style is applied first, there is no line below.
    If Line Below style is applied first, the line below appears.
    And with multiple paragraph styles applied, there is no quick way to clear overrides (or even find where they are). Selecting the whole paragraph then clicking on another style sometimes leaves one of the original paragraph styles selected.
    Also, there is a bug (?) where if a new text box is drawn with a style already selected, changing the style adds the style to the original one instead of replacing it. The only way out of this is to select 'Detach Characters from "Stylename"' from the flyout menu. (But, these bugs are inconsistent and depend on which styles have been applied before.)
    I realise there are still bugs to remove, so it's hard to work out for sure how styles will eventually work, but I think being able to apply multiple paragraph styles is a mistake. The whole idea of one style being 'based on' another is surely a better way (and already implemented), and then keep character and paragraph styles separate.
  16. Like
    Jim_A got a reaction from A_B_C in Apply Styles – Options behave strangely   
    I agree with Wosven: being able to apply paragraph styles to individual characters is confusing.
    Paragraph styles for paragraphs. (Whole paragraphs.)
    Character styles for characters. 
    It is confusing to be able to apply more than one paragraph style to a paragraph, especially as the order in which they are applied determines which elements of the style appear. 
    For instance, try setting a paragraph to Body style, select all, then 'Apply "Line Below" to Characters'. Now try it in reverse.
    If Body style is applied first, there is no line below.
    If Line Below style is applied first, the line below appears.
    And with multiple paragraph styles applied, there is no quick way to clear overrides (or even find where they are). Selecting the whole paragraph then clicking on another style sometimes leaves one of the original paragraph styles selected.
    Also, there is a bug (?) where if a new text box is drawn with a style already selected, changing the style adds the style to the original one instead of replacing it. The only way out of this is to select 'Detach Characters from "Stylename"' from the flyout menu. (But, these bugs are inconsistent and depend on which styles have been applied before.)
    I realise there are still bugs to remove, so it's hard to work out for sure how styles will eventually work, but I think being able to apply multiple paragraph styles is a mistake. The whole idea of one style being 'based on' another is surely a better way (and already implemented), and then keep character and paragraph styles separate.
  17. Like
    Jim_A got a reaction from Husbandman in Find & Replace with nothing / Soft return / Bullets   
    - 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)
     


  18. Thanks
    Jim_A got a reaction from Jowday in Story editor - mandatory   
    +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.
×