Skip to content

Matěj Kříž

My feedback

2 results found

  1. 33 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Matěj Kříž supported this idea  · 
  2. 30 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Under Review  ·  amaarora responded

    Thanks for reporting the issue. We are reviewing it

    -InDesign Team

    An error occurred while saving the comment
    Matěj Kříž supported this idea  · 
    An error occurred while saving the comment
    Matěj Kříž commented  · 

    How it looks in InDesign

    An error occurred while saving the comment
    Matěj Kříž commented  · 

    ### Adobe InDesign version:

    InDesign 14.0.2 x64

    ### Steps to reproduce the issues:

    1. Create Character Style with Underline Options (or Strikethrough Options)
    2. Set this Character Style as Numbering Style for Paragraph

    ### Expected result:

    All styles from my Character Style are respected and used in Numbering Style. Underline Options (or Strikethrough Options) set in Character Style are used in Paragraph Numbering, so I can see underlined number, or I can create fake background color for number with underline offset etc

    ### Actual result

    SOME styles from my Character Style are ignored in Numbering style. Underline Options (or Strikethrough Options) are ignored in Numbering style.
    When you set same Character Style directly to some characters in Paragraph it works fine. You use it as Numbering style SOME (Underline Options and Strikethrough Options) styles are ignored.

    Here is a discussion on this topic on Adobe Forums with suggested workaround: https://forums.adobe.com/message/11159786

Feedback and Knowledge Base